summaryrefslogtreecommitdiffstats
path: root/bpmn/MSOInfrastructureBPMN
AgeCommit message (Collapse)AuthorFilesLines
2017-09-21Add preprocess for NS Createc001491071-47/+19
Pre deal the parameters for NS create Change-Id: I43afdbceb262d881e6a501c41ee2cf6e50173ad6 Issue-ID:SO-57 Signed-off-by: c00149107 <chenchuanyu@huawei.com>
2017-09-21Add NS Create Taskc001491072-152/+121
Add the details task of NS create workflow Change-Id: Ic3ee8c2659ae2cdc9b91b5eaf318dd655d87f711 Issue-ID:SO-57 Signed-off-by: c00149107 <chenchuanyu@huawei.com>
2017-09-21Merge "SO Failed Robot Health Check"Seshu Kumar M1-0/+7
2017-09-21SO Failed Robot Health CheckRob Daugherty1-0/+7
There were several issues. The wrong jackson provider was being selected, which caused the exception, so we fixed that. Then we discovered that a a URN mapping was missing, so we added that. Then we found that the healthcheck wouldn't work because it's trying to check the default process engine, which does not exist. We commented out that part of the healthcheck to be able to resolve this high priority issue. A new low priority issue will need to be created to follow up. Change-Id: I327612a147333eeecd44915942cecd13959c4717 Issue-id: SO-139 Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-09-20Fix duplicate service instance idsSeshu-Kumar-M3-215/+171
IssueId: SO-146 Change-Id: I483f96eea7be409546ebc5c84e2332b2992672e7 Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
2017-09-20Add subprocess for NS createc001491071-0/+258
Add VFC NS create sub work flow Change-Id: I503419f89633a0f74a887bc3b95fbaa3acdbfd02 Issue-ID:SO-57 Signed-off-by: c00149107 <chenchuanyu@huawei.com>
2017-09-20Added Groovy for E2E svcSeshu-Kumar-M3-131/+45
IssueId: SO-146 Change-Id: Id247132c451e16c49dde8b8547d50924cdfa00c4 Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
2017-09-20Add E2E service BPMNs resolve conflictsSeshu-Kumar-M3-145/+409
IssueId:SO-56 Change-Id: Icb04ea102b1fe497d8827eac582b28a472bbb836 Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
2017-09-19BPMN applications not deployed properlyRob Daugherty7-16/+133
Since the 1710 MSO merge the following problems exist: The workflow applications are not deployed properly. I've also fixed a few small issues with the CreateCustomE2EServiceInstance flows that prevented them from being deployed. Change-Id: Ia4f7a6de87abbc99e80c0e9083e2175cdf9b4fe5 Issue-id: SO-148 Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-09-18Merge "VoLTE groovy draft files"Seshu Kumar M3-0/+1218
2017-09-18Merge "VoLTE BPMN draft file"Seshu Kumar M3-0/+1145
2017-09-18VoLTE groovy draft filesSeshu-Kumar-M3-0/+1218
Issue-Id: SO-142 Change-Id: I2adbf796f46cb400d32ada1d7f0ae671e58b00ad Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
2017-09-18VoLTE BPMN draft fileSeshu-Kumar-M3-0/+1145
Issue-ID: SO-46 Change-Id: I01b80c4eb5ee6c779dd95b840fa99a9bff0ad78e Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
2017-09-18Add sync response taskc001491071-1/+40
Add sync response task for e2e service flow Change-Id: I3b17e0103fb3e7cb4ba41d076bc6014acc1d295c Issue-ID:SO-57 Signed-off-by: c00149107 <chenchuanyu@huawei.com>
2017-09-18Add Create E2E Service Groovyc001491071-0/+121
Add groovy logic for E2E service Change-Id: I3d3f1023c14d2621380933396fbc650516145da2 Issue-ID:SO-57 Signed-off-by: c00149107 <chenchuanyu@huawei.com>
2017-09-13Merge "Fix hardcoded orchestration-status"Seshu Kumar M2-4/+7
2017-09-11Fix hardcoded orchestration-statusAbhishek Shekhar2-4/+7
While creating a service-instance orchestration-status is hardcoded to be Active. The user should be allowed to set the initial status. Issue-id: SO-108 Change-Id: Ica6febae1f7733125126b49f4f7e0e23bba2a0f2 Signed-off-by: Abhishek Shekhar <abhishek.shekhar1@amdocs.com>
2017-09-11Groovy scripts header correctionSeshu-Kumar-M42-42/+42
IssueId: SO-120 Change-Id: I58aaff6213fcc91388f1cabf3ca37838a25c1c73 Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
2017-09-11Change the header to SOSeshu-Kumar-M19-19/+19
IssueId: SO-120 Change-Id: I4282112764bc7697dd98e780bb02b13319cabb5d Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
2017-09-081710 Rebase - Second AttemptArthur Martella160-7762/+28967
This commit rebases changes from openecomp-mso/internal-staging-1710 up to and including this codecloud commit: 54483fc6606ddb1591a2e9da61bff8712325f924 Wed Sep 6 18:12:56 2017 -0400 Rebasing was done on a branch on top of this commit in so/master in ONAP: 93fbdfbe46104f8859d4754040f979cb7997c157 Thu Sep 7 16:42:59 2017 +0000 Change-Id: I4ad9abf40da32bf5bdca43e868b8fa2dbcd9dc59 Issue-id: SO-107 Signed-off-by: Arthur Martella <amartell@research.att.com>
2017-08-04Failed to deploy so artifacts in nexus (again)Rob Daugherty1-7/+7
There are Linux Foundation rules (enforced by nexus) that I still don't really understand. I'm convinced this is absolutely true: The groupId of every artifact in a project MUST begin with: org.openecomp.<project> --or-- org.onap.<project> The top-level artifact is no exception. So for example, this is NOT allowed: <groupId>org.openecomp</groupId> <artifactId>so</groupId> Here's what I'm trying now. The top level pom will contain: <groupId>org.openecomp.so</groupId> <artifactId>so-parent</artifactId> Child modules will contain: <parent> <groupId>org.openecomp.so</groupId> <artifactId>so-parent</artifactId> <version>1.1.0-SNAPSHOT</version> </parent> <groupId>org.openecomp.so</groupId> <artifactId>some-child-artifact</artifactId> Note that the groupId for the direct child module will be the same as the groupId for its parent. Issue: SO-21 Change-Id: I0d3cd2eb7a1883e23e3c0878ee7fa3dd4a7d55b2 Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-08-01Failed to deploy so artifacts in nexusRob Daugherty1-7/+7
More problems encountered since mso repos were renamed. We now have found that this declaration in the top-level so pom causes the deploy to fail with a 403 Forbidden error: <groupId>org.openecomp</groupId> <artifactId>so</artifactId> We are changing this to: <groupId>org.openecomp.so</groupId> <artifactId>framework</artifactId> Issue: SO-21 Change-Id: I4e21d689c73c5071bde725127bb81482ce3d91f9 Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-07-19Fix artifact group IDs (org.openecomp.so)Rob Daugherty1-7/+7
Since the repositories were renamed from "mso" to "so" the artifact group IDs in the poms must be updated to match. Issue: SO-39 Change-Id: I617fe738a77d0f6c1d1cc0ac9474fb753f4e234c Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-05-09Refactor WorkflowAsyncResourceGary Wu1-7/+3
Change-Id: I794b606687343851f71d63ac055ed1898320216a Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
2017-05-09[MSO-8] Additional fixes for the second rebaseDeterme, Sebastien (sd378r)62-15598/+11005
DB fixes + BPMN flows and groovy fixes + Fix issue with CloudConfig file not reloaded properly when it's wrong (JSON error or model hierarchy mistake) at MSO startup Change-Id: I2853030b78499e2a761706b643ea210955e72de3 Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com> [MSO-8] Restore files removed in patch set 2 Those groovy files must be there Change-Id: I9a47ac3d9c8fc06774a1b8f518491b1b0b00af04 Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
2017-05-02[MSO-8] Second step of the rebase for MSODeterme, Sebastien (sd378r)115-20426/+25776
Second rebase containing additional features for MSO + total reworking of the BPMN structure + Notification flow can now be added at the end of some BPMN flows Change-Id: I7e937c7a0ba1593ca85e164a093f79c7e38b6ce0 Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
2017-04-11[MSO-8] Update the maven dependencyxg353y188-0/+47240
Update the maven depenency for sdc-distribution-client to cooperate with the sdc changes. Change-Id: I2da936e5c40cb68c7181bb78307192dd5655b5dc Signed-off-by: xg353y <xg353y@intl.att.com>