Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
|
|
Throw exception if resource receipe is not available for the resource
in service.
Change-Id: Ic6110a1f03d9a0f22d963812eab99e571191140d
Issue-ID: SO-422
Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.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>
|
|
|
|
Issue-ID: SO-659
Change-Id: I4f7d9ce861db6d997ebc1108cdf1bd0995a7aa19
Signed-off-by: Bancala, Ben (bb3476) <bb3476@att.com>
|
|
|
|
Adding space to change TunnelXConn to Tunnel XConn
so that SO will match SDNC.
Change-Id: I2a752fd1c6b3ed115c8a2dafbd47e3ce24f49a57
Issue-ID: SO-650
Signed-off-by: Arthur Martella <am153x@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>
|
|
|
|
|
|
Change-Id: I6d0d30b10615fd7b411ab723cf27fbeea2fec21e
Issue-ID: SO-602
Signed-off-by: Elena Kuleshov <ek1439@att.com>
|
|
Change-Id: I7d83ee933361ca16d9b05639bfb84b9c1466887c
Issue-ID: SO-602
Signed-off-by: Elena Kuleshov <ek1439@att.com>
|
|
Issue-ID: SO-634
Change-Id: I79ac70be79345c966642dc5b99c25b4a39dc575d
Signed-off-by: guanwenyao <guanwenyao@chinamobile.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>
|
|
Issue-ID: SO-637
Change-Id: I0c95e5d5c7a9ea60525d103823bd22495f6ac6a6
Signed-off-by: Marcus G K Williams <marcus.williams@intel.com>
|
|
|
|
|
|
Issue-ID: SO-636
Change-Id: Ieb6c3da2c0485585d009bfca1d689f4c485a2879
Signed-off-by: Marcus G K Williams <marcus.williams@intel.com>
|
|
Fix ressource looping if AAI response is empty for resource list.
Change-Id: I244d3836beb98ec2689c71df5c61f24f40619d96
Issue-ID: SO-632
Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.com>
|
|
Issue-ID: SO-634
Change-Id: Id39f2487d111099abf09330f3f2f089605cbe945
Signed-off-by: guochong <guochong@chinamobile.com>
|
|
|
|
Re: https://gerrit.onap.org/r/#/c/48031/1
SO is failing health check because pnfCheckInputs
is not found in dmaap.properties, and
pnf.properties is not being read, since
applicationContext.xml has two
PropertyPlaceholderConfigurer attributes, but
it's only using one.
Moved defaultTimeout to dmaap.properties, where
applicationContext.xml will be able to read it,
and renamed it to pnfDefaultTimeout to make it
clearer what it is.
Change-Id: I6490de472fbf4875e53204f4248c6325787c8af5
Issue-ID: SO-506
Signed-off-by: Arthur Martella <am153x@att.com>
|
|
|
|
In the integration environment, there's no cloud region named att-aic.
Therefore, try without att-aic first (CLOUD-REGION)
and if that fails, try att-aic (DEFAULT-CLOUD-REGION)
Change-Id: Ie4a4a3924eb6fe1120519e124a7967a62c96428f
Issue-ID: INT-475
Signed-off-by: Arthur Martella <am153x@att.com>
|
|
Change-Id: I1a4f4b9704385a17995e76d4b87484c2f588b889
Issue-ID: SO-506
Signed-off-by: biniek <lukasz.biniek@nokia.com>
|
|
Change-Id: I41bf2c4d12345d46d8bf008f79d6610592e3b645
Issue-ID: SO-625
Signed-off-by: Arthur Martella <am153x@att.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>
|
|
Change-Id: I2f35d1a8cc01f349f791b1bc192f91f5f020f689
Issue-ID: SO-506
Signed-off-by: biniek <lukasz.biniek@nokia.com>
|
|
|
|
|
|
Set operation type value, to reflect in DB entries.
Change-Id: I2f56bf5f33912645d17bbed2fc759f9354a0ba7b
Issue-ID: SO-422
Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.com>
|
|
Fix warning in DoDeleteE2E bpmn file.
Change-Id: I50b1ad5502fc08692775d2f5d9050c3796dd32b1
Issue-ID: SO-422
Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.com>
|
|
Change-Id: I0a166b867dcacad4133c8fc679606c381cb5389a
Issue-ID: SO-602
Signed-off-by: Bancala, Ben (bb3476) <bb3476@att.com>
|
|
Change-Id: I3e27ec0d1487eb68e8c54d27508b58233bf49808
Issue-ID: SO-602
Signed-off-by: Bancala, Ben (bb3476) <bb3476@att.com>
|
|
Change-Id: I05f4648ff898a54e7a00d899d97129746172cdb4
Issue-ID: SO-603
Signed-off-by: Arthur Martella <am153x@att.com>
|
|
|
|
deleteResource bugs fix
Change-Id: Idaa55084f5ecb0dd3636c232cebc14fa5f06430a
Issue-ID: SO-578
Signed-off-by: Yulian Han <elaine.hanyulian@huawei.com>
|
|
Change to sdncadapter for service call
Change-Id: I9011e69fba20d4d0f83705455791b7357e2f5bb0
Issue-ID: SO-587
Signed-off-by: c00149107 <chenchuanyu@huawei.com>
|
|
|
|
Add NS relationship delete for E2E service
Change-Id: Ia58308dae0fef38b32098d1e92c0871617a86ed2
Issue-ID: SO-422
Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.com>
|
|
Fix value for VFC sync response.
Change-Id: Ie663f9080c051b9302dd4729aea5640c5289e14c
Issue-ID: SO-422
Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.com>
|
|
Remove operation status set in api-handler
Change-Id: I579d25044130b0701231c0a2d42534e8c63e3ebd
Issue-ID: SO-587
Signed-off-by: c00149107 <chenchuanyu@huawei.com>
|
|
|
|
|
|
Fix VFCNS termination invocation
Change-Id: Ib30f0a3e4365e215f6da0a693f78825d5a2d32c9
Issue-ID: SO-422
Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.com>
|
|
Add service operation initialtion in request db
Change-Id: I2aed78e5cda753b5424b8a8c39e9997a7a7dd61c
Issue-ID: SO-422
Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.com>
|
|
|
|
|