Age | Commit message (Collapse) | Author | Files | Lines |
|
Issue-ID: SO-777
Change-Id: I8a46f1802feb18ab4df098472fef5373ac42208b
Signed-off-by: Brittany Plummer (bp896r) <bp896r@att.com>
|
|
|
|
SO maps "instanceName" to "serviceName" field
in the Homing Request, however OOF is expecting
'subscriptionServiceType'
Issue-ID: SO-667
Change-Id: I3faa6cc600b6515d9c6e01e18cb289104f3976fc
Signed-off-by: Marcus G K Williams <marcus.williams@intel.com>
|
|
changes required for unit tests to pass again
Changes sniro homing BB license demand to be a named array per sniro
defect.
boolean checks must now account for null
fixed compilation issues in code
updated tests and removed primatives from bbobjects
upgraded to A&AI dependency with Boolean
Change-Id: I5f3e69c0ad24d2c3e4591568467bad861abd0261
Issue-ID: SO-896
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
|
|
Changed logic to determine if sniro request is initial or speed change.
Change-Id: I36eeea8860855bf5226560dcc2722a2c27723ef9
Issue-ID: SO-893
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
Added logic to get service type and customer id from uri keys for sdnc request.
Change-Id: I3b0c4b88737e2ad6fc573d335addff221d06e885
Issue-ID: SO-889
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
fixed compilation issues and all unit tests now pass
fix condition that checks for vnf in list to set homing flags
fix resource name variable being null
Skip volume group search for alacarte VF Module creation, since that group is expected to be specified on the input
Remove temporary change to JUnit for creation of volume group.
Add mapping of isBaseVfModule setting to AAIObjectMapper for vfModule.
adding a unit test for hte issue which was fixed
Explicitly return heatStackId variable from VnfAdapter subprocess
Fixing an issue with the workflow processor/asynresource which may lead to
apihandler leaving the active_Request table record in_progress while the bpmn quits the processing due to the error.
Change-Id: I7587193fcb5251f50370d72a1e4c10d112a1c72f
Issue-ID: SO-879
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
Bug fix for ccvpn uc
Change-Id: Idaa55084f5ecb0dd3636c232cebc14fa70000013
Issue-ID: SO-683
Signed-off-by: Yulian Han <elaine.hanyulian@huawei.com>
|
|
updated mock in unassignnetworkbbtest instead of base
added mock to extract pojos method in unassignnetwork
Return gBuildingBlockExecution from calls to VnfAdapter subprocess
Correct JUnit data to expect modelInfoVfModule
Enable Spring Security for logging of unauthorized/bad credentials
errors
Fix handling of a case of no VF Modules in a VNF resource.
fix populating lookupKeyMap with resource ids
removed unnecessary test resources
Issue-ID: SO-848
Change-Id: Id89f075dcac4042bf8fb1e207e66d289d079171f
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
|
|
Fixes the new GR-API flow
Various fixes in the create VF Module area
Fixes issues parsing the SDNC GR API response
Fixes new resource type in ASDC controller
Fixes AppC mismatch in JSON marshaling
Issue-ID: SO-821
Change-Id: I4ace0d348483ab1303fcfee26c5801674be51466
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
Add more logging information for Java.Lang Exceptions
Issue-ID: SO-822
Change-Id: I5eb25adc087c9fb495829af2c9d0d1be7374f4a3
Change-Id: I5eb25adc087c9fb495829af2c9d0d1be7374f4a3
Signed-off-by: Smokowski, Steve (ss835w) <ss835w@us.att.com>
|
|
|
|
Change-Id: Idaa55084f5ecb0dd3636c232cebc14fa70000005
Issue-ID: SO-683
Signed-off-by: Yulian Han <elaine.hanyulian@huawei.com>
|
|
to use AAIResourceClient
updated bpmn, removed Generic AAI flows, and removed dead useless code
Did not modify E2E Delete Service Instance flow as it has changed
significantly
Issue-ID: SO-813
Change-Id: I1a6bc5353ef89e2ce4359be2654395f7ce060aba
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
Change-Id: Idaa55084f5ecb0dd3636c232cebc14fa70000001
Issue-ID: SO-683
Signed-off-by: Yulian Han <elaine.hanyulian@huawei.com>
|
|
Change-Id: I665f35bd6385ceec2d5aeff9a1d8af359bccd97a
Issue-ID: SO-784
Signed-off-by: Lukasz Muszkieta <lukasz.muszkieta@nokia.com>
|
|
Change-Id: I95381232eeefcd247a66a5cec370a8ce1c288e18
Issue-ID: SO-670
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
|
|
|
|
Change-Id: If229caa7abfad85f10e5ee7b8f5f6eccfb6600ac
Issue-ID: SO-602
Signed-off-by: Elena Kuleshov <ek1439@att.com>
|
|
|
|
Change-Id: I6fa62b9dca0e7f69030fffab5cbc13fe57b39294
Issue-ID: SO-602
Signed-off-by: Elena Kuleshov <ek1439@att.com>
|
|
Flavor Labels are not passed to
DoCreateVnfAndModules.bpmn, in
turn it needs to be passed to
DoCreateVfModule
Issue-ID: SO-661
Change-Id: I51c4e77677a17513725d5b832e379bbb72f13185
Signed-off-by: Marcus G K Williams <marcus.williams@intel.com>
|
|
- Works around a bug in OOF
where OOF does not return a serviceResourceId
with homing solutions. SO uses serviceResourceId
to match a homing deman to a homing request.
This patch addes resourceModuleName as another
way to match a demand to a request, as currently
OOF needs this to be unique.
- Changes SO homing processing of key cloudRegionId to
key locationId as this is now the key used for cloudRegionId
in solutions sent back from OOF
Issue-ID: OPTFRA-249
Change-Id: I8e5d9244a227ea4d3d061a758f202144bac270ce
Signed-off-by: Marcus G K Williams <marcus.williams@intel.com>
|
|
changing capitalization of SDNC in LCM property
adding payload to createVfModule bpmn
Change-Id: Ib4d8e172a929a8138cf4e3fbf446170467b44a42
Issue-ID: INT-475
Signed-off-by: Arthur Martella <am153x@att.com>
|
|
Change-Id: Ia9aaf05cd2a255491b0f73351653f1b622140e62
Issue-ID: SO-602
Signed-off-by: Arthur Martella <am153x@att.com>
|
|
|
|
- Fix general topic properties.
- Fix junit for getLcmProperties
Change-Id: I424129c18a017908280c6bdc831a6a72ba1192ca
Issue-ID: SO-602
Signed-off-by: Elena Kuleshov <ek1439@att.com>
|
|
|
|
Change-Id: I71003381548d1d221854f78e0d0734994dd16d5f
Issue-ID: SO-602
Signed-off-by: Elena Kuleshov <ek1439@att.com>
|
|
- Update homing request build to send
correct request to OOF
- Use nfFunction field as resourceModuleName
requires updating nfFunction fields
during vcpeRestCust service creation in SDC
- Fix No Solution Error from OOF
- Made subscriber info and cloud info optional as OOF Homing does
not require it
- Update Homing Requests for AR to provide vgMuxInfra
modelInfo instead of vgmuxAR modelInfo as required by OOF
Issue-ID: SO-573
Change-Id: If1c41c81f387bb614be954d158d6cc4d9c48e2c8
Signed-off-by: Marcus G K Williams <marcus.williams@intel.com>
|
|
|
|
serviceInstanceName was not set
in CreateVcpeResCustService and not
made available in Homing Flow.
Issue-ID: SO-573
Change-Id: I9d3098aa252ceba139c75a24c71950bab70b14b6
Signed-off-by: Marcus G K Williams <marcus.williams@intel.com>
|
|
Change-Id: I648e5a25337beca1f8c483ba6e5359d245e237d3
Issue-ID: SO-642
Signed-off-by: mkorman <michal.korman@nokia.com>
|
|
|
|
OOF does not support License deman in Beijing
Issue-ID: SO-573
Change-Id: Ia7e013949773595b520ed4cbd0bbe8cb0f18922c
Signed-off-by: Marcus G K Williams <marcus.williams@intel.com>
|
|
... again. Back to just changing topic.read
and topic.write based on controllerType (but
still setting controllerType too, just in
case).
Change-Id: I175d20b998c6d141ca7587504535bd7bb494563c
Issue-ID: INT-475
Signed-off-by: Arthur Martella <am153x@att.com>
|
|
Followup to https://gerrit.onap.org/r/#/c/48571/
Adding property sdnc-topic.read and
sdnc-topic.write to match topic.sdnc.read and
topic.sdnc.write on advice of SDNC LCM dev.
Change-Id: I3c856f126ecb2f6b1c45df818ea7d294e0440e5c
Issue-ID: INT-475
Signed-off-by: Arthur Martella <am153x@att.com>
|
|
When controllerType is sdnc, it's still using
the appc topic names. Trying this to switch
topic based on controllerType.
Patch 2 changed to match APPCClient in ATT
code base.
Change-Id: I72e7e84720f73ac30d3d28e3387af2d537d301ad
Issue-ID: INT-475
Signed-off-by: Arthur Martella <am153x@att.com>
|
|
|
|
Fix resource building logic.
Change-Id: I95064d945a6ff026a0ea10336a550d9bb8af401a
Issue-ID: SO-624
Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.com>
|
|
Issue-ID: SO-628
Change-Id: I6e9e44d453a72b4e9ec1a0abe99eb8028aa5ba1a
Signed-off-by: Marcus G K Williams <marcus.williams@intel.com>
|
|
Issue-ID: SO-628
Change-Id: I3bd802fc966f466b12556d19e347a130e152a51d
Signed-off-by: Marcus G K Williams <marcus.williams@intel.com>
|
|
This commit adds some robustness to the interface between the
API-H and BPMN, specifically, in how the response is handled.
I don't have proof, but there appears to be some randomness to
the json provider behavior when used with the jax-rs. Sometimes,
the serializer is adding the root element, and sometimes it
is not. Maybe there's something wrong with the configuration.
Maybe we have competing json providers. I couldn't pin this
down.
I'm almost certain it is the presence of the root element in
the content that causes the API-H code to fail parsing of the
BPMN response. This doesn't kill the request, as you might
expect, but rather, the API-H passes the BPMN response through
to the client (VID, or policy, or whatever).
The original problem (SO-586) was "fixed" by "removing the
wrapper". This "wrapper" is a needed feature of the interface
between BPMN and the API-H. We shouldn't have removed it.
The fact that the "fix" appeared to work is due to the
behavior I described in the previous paragraph. The API-H
chokes on the message, and it passes it through unchanged.
Not really what we want.
So, I don't know why the jackson/json behavior is flaky and
different now, but I can (and did) modify the API-H so it can
parse a json message whether or not it has a root element.
Note that WorkflowResponse.java (in BPMN) and CamundaResponse.java
(in the API-H) are basically the same bean representing the
message format. Seems less than ideal to have two different
classes.
Also note that I changed the name of the "response" attribute
of the WorkflowResponse and CamundaResponse classes to "content".
Got tired of seeing this nonsense everywhere in the code:
response.getResponse()
Change-Id: Icaf70f8457de99e493cf882170fe778c620308c9
Issue-ID: SO-586
Issue-ID: SO-618
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
When the workflow response succeeds, the requestReferences object is being wrapped by "WorkflowResponse": {"response": {... and all the other fields from the WorkflowResponse object are being included as well. Adding a WorkflowResponseSerializer didn't seem to work since the root node was still included and there was no ObjectMapper in which to set WrapRootValue to false. So this is the next best thing.
Patch 2 fixes most of the broken unit tests.
Change-Id: Ifa5bd02e70b23f41c9042ac207848c8ade77313a
Issue-ID: SO-586
Signed-off-by: Arthur Martella <am153x@att.com>
|
|
Use tosca parser without resolving GetInput.
Change-Id: I964464dd76c0bdd096e67ce78ab4cc7c2e76a167
Issue-ID: SO-422
Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.com>
|
|
Change-Id: I05f4648ff898a54e7a00d899d97129746172cdb4
Issue-ID: SO-603
Signed-off-by: Arthur Martella <am153x@att.com>
|
|
Set Resource Recipe Time Out Val
Change-Id: I7f304465c71837ee37e5fa99a48ca14d97d8f91f
Issue-ID: SO-587
Signed-off-by: c00149107 <chenchuanyu@huawei.com>
|