summaryrefslogtreecommitdiffstats
path: root/bpmn
AgeCommit message (Collapse)AuthorFilesLines
2018-05-24Fix problem with singleton impact on TC executionBogumil Zebek2-1/+9
Change-Id: I154c150d8c6c6620344f3f584d3ec7e7201a46ff Issue-ID: SO-643 Signed-off-by: Bogumil Zebek <bogumil.zebek@nokia.com>
2018-05-24Fix problem with singleton and parallel unit testsBogumil Zebek2-0/+6
Change-Id: If4236506978795933564fc6507e780212edbfd5d Issue-ID: SO-641 Signed-off-by: Bogumil Zebek <bogumil.zebek@nokia.com>
2018-05-24Merge "Removing license from OOF Homing Demand"Seshu Kumar M2-12/+4
2018-05-23Removing license from OOF Homing DemandMarcus G K Williams2-12/+4
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>
2018-05-23APPC client changes topic for controllerTypeArthur Martella1-2/+7
... 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>
2018-05-23Change LCM property for SDNC topicArthur Martella1-0/+2
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>
2018-05-23Fix cloudOwner, cloudRegionId in HomingMarcus G K Williams2-0/+15
Issue-ID: SO-637 Change-Id: I0c95e5d5c7a9ea60525d103823bd22495f6ac6a6 Signed-off-by: Marcus G K Williams <marcus.williams@intel.com>
2018-05-23Merge "Fix resource looping if AAI response empty"Chuanyu Chen1-10/+14
2018-05-23Merge "fix endless loop"Chuanyu Chen1-1/+1
2018-05-23Merge "Fix customerLocation var in VcpeCusRes Flow"Seshu Kumar M1-1/+2
2018-05-22Fix customerLocation var in VcpeCusRes FlowMarcus G K Williams1-1/+2
Issue-ID: SO-636 Change-Id: Ieb6c3da2c0485585d009bfca1d689f4c485a2879 Signed-off-by: Marcus G K Williams <marcus.williams@intel.com>
2018-05-22APPC client changes topic for controllerTypeArthur Martella1-2/+7
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>
2018-05-22Fix resource looping if AAI response emptysubhash kumar singh1-10/+14
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>
2018-05-22fix endless loopguochong1-1/+1
Issue-ID: SO-634 Change-Id: Id39f2487d111099abf09330f3f2f089605cbe945 Signed-off-by: guochong <guochong@chinamobile.com>
2018-05-22Merge "Added setting pnf name in pnf-pnp"Seshu Kumar M4-4/+54
2018-05-21Move pnfDefaultTimeout to dmaap.propertiesArthur Martella3-7/+4
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>
2018-05-21Merge "Added checking input variables in pnf-pnp"Rob Daugherty7-104/+271
2018-05-18Merge "Fallback for cloud region calls to AAI"Rob Daugherty1-3/+11
2018-05-18Fallback for cloud region calls to AAIArthur Martella1-3/+11
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>
2018-05-18Merge "Fix resource building logic"Seshu Kumar M1-1/+5
2018-05-17Fix resource building logicsubhash kumar singh1-1/+5
Fix resource building logic. Change-Id: I95064d945a6ff026a0ea10336a550d9bb8af401a Issue-ID: SO-624 Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.com>
2018-05-17Added checking input variables in pnf-pnpbiniek7-104/+271
Change-Id: I1a4f4b9704385a17995e76d4b87484c2f588b889 Issue-ID: SO-506 Signed-off-by: biniek <lukasz.biniek@nokia.com>
2018-05-17Revert placementInfo to placement in SniroHomingMarcus G K Williams4-5/+5
Issue-ID: SO-628 Change-Id: I6e9e44d453a72b4e9ec1a0abe99eb8028aa5ba1a Signed-off-by: Marcus G K Williams <marcus.williams@intel.com>
2018-05-16Revert placementInfo to placement in SNIROUtilsMarcus G K Williams2-4/+4
Issue-ID: SO-628 Change-Id: I3bd802fc966f466b12556d19e347a130e152a51d Signed-off-by: Marcus G K Williams <marcus.williams@intel.com>
2018-05-16Add homingService variable to homing bbArthur Martella2-2/+4
Change-Id: I41bf2c4d12345d46d8bf008f79d6610592e3b645 Issue-ID: SO-625 Signed-off-by: Arthur Martella <am153x@att.com>
2018-05-15WorkflowResponse json issuesRob Daugherty34-177/+191
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>
2018-05-10Close db connections in finally blockEthan Lynn1-14/+19
Fix bugs reported by sonar Change-Id: I0d3445856eb45533d904443b60d75c8aa03e5881 Issue-ID: SO-580 Signed-off-by: Ethan Lynn <ethanlynnl@vmware.com>
2018-05-09Added setting pnf name in pnf-pnpbiniek4-4/+54
Change-Id: I2f35d1a8cc01f349f791b1bc192f91f5f020f689 Issue-ID: SO-506 Signed-off-by: biniek <lukasz.biniek@nokia.com>
2018-05-08Remove wrapper from WorkflowResponseArthur Martella4-3/+17
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>
2018-05-07Merge "updated createvfmoduleinfra flow version number"Seshu Kumar M1-15/+15
2018-05-07Merge "fixed bug in createvnfinfra bpmn"Seshu Kumar M5-37/+104
2018-05-04Use tosca parser without resolving GetInputsubhash kumar singh1-1/+1
Use tosca parser without resolving GetInput. Change-Id: I964464dd76c0bdd096e67ce78ab4cc7c2e76a167 Issue-ID: SO-422 Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.com>
2018-05-04Set operation type valuesubhash kumar singh1-0/+1
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>
2018-05-04Fix warning in DoDeleteE2E bpmn filesubhash kumar singh1-7/+7
Fix warning in DoDeleteE2E bpmn file. Change-Id: I50b1ad5502fc08692775d2f5d9050c3796dd32b1 Issue-ID: SO-422 Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.com>
2018-05-04updated createvfmoduleinfra flow version numberBancala, Ben (bb3476)1-15/+15
Change-Id: I0a166b867dcacad4133c8fc679606c381cb5389a Issue-ID: SO-602 Signed-off-by: Bancala, Ben (bb3476) <bb3476@att.com>
2018-05-04fixed bug in createvnfinfra bpmnBancala, Ben (bb3476)5-37/+104
Change-Id: I3e27ec0d1487eb68e8c54d27508b58233bf49808 Issue-ID: SO-602 Signed-off-by: Bancala, Ben (bb3476) <bb3476@att.com>
2018-05-04Add enforcer.skip to pom.xmlArthur Martella1-2/+2
To prevent appc snapshot problem Also change appc version to SNAPSHOT Change-Id: Ifce05b7f44ccc70a2d654526d67da873dd325dcd Issue-ID: SO-605 Signed-off-by: Arthur Martella <am153x@att.com>
2018-05-03ecomp-model-information to onap-model-informationArthur Martella13-75/+86
Change-Id: I05f4648ff898a54e7a00d899d97129746172cdb4 Issue-ID: SO-603 Signed-off-by: Arthur Martella <am153x@att.com>
2018-04-28Merge "createvfcns serviceInstanceid is null bug fix"Seshu Kumar M3-11/+11
2018-04-28createvfcns serviceInstanceid is null bug fixYulian Han3-11/+11
deleteResource bugs fix Change-Id: Idaa55084f5ecb0dd3636c232cebc14fa5f06430a Issue-ID: SO-578 Signed-off-by: Yulian Han <elaine.hanyulian@huawei.com>
2018-04-27Change to sdncadapter for service callc001491072-50/+165
Change to sdncadapter for service call Change-Id: I9011e69fba20d4d0f83705455791b7357e2f5bb0 Issue-ID: SO-587 Signed-off-by: c00149107 <chenchuanyu@huawei.com>
2018-04-26Merge "Remove operation status set in api-handler"Rob Daugherty2-9/+8
2018-04-26Add NS relationship delete for E2E servicesubhash kumar singh2-13/+100
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>
2018-04-26Fix value for VFC sync responsesubhash kumar singh2-0/+3
Fix value for VFC sync response. Change-Id: Ie663f9080c051b9302dd4729aea5640c5289e14c Issue-ID: SO-422 Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.com>
2018-04-26Remove operation status set in api-handlerc001491072-9/+8
Remove operation status set in api-handler Change-Id: I579d25044130b0701231c0a2d42534e8c63e3ebd Issue-ID: SO-587 Signed-off-by: c00149107 <chenchuanyu@huawei.com>
2018-04-26Merge "Fix VFCNS termination invocation"Chuanyu Chen2-0/+20
2018-04-26Merge "Add service operation initialtion in request db"Chuanyu Chen2-16/+115
2018-04-25Fix VFCNS termination invocationsubhash kumar singh2-0/+20
Fix VFCNS termination invocation Change-Id: Ib30f0a3e4365e215f6da0a693f78825d5a2d32c9 Issue-ID: SO-422 Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.com>
2018-04-25Add service operation initialtion in request dbsubhash kumar singh2-16/+115
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>
2018-04-25Merge "PnfReadyEventConsumer implementation"Seshu Kumar M3-42/+45