Age | Commit message (Collapse) | Author | Files | Lines |
|
Add generic post function and correct the api define
Change-Id: I11c2a10f4aad00f389b68cf7b9c42dab4441027c
Issue-ID:SO-57
Signed-off-by: c00149107 <chenchuanyu@huawei.com>
|
|
|
|
Files regarding the Homing building blocks added for use in vCPE flows.
Change-Id: Iae9eb70b81ec7d473e6c4e9c821a9282dc40baa9
Issue-id: SO-138
Signed-off-by: Arthur Martella <amartell@research.att.com>
|
|
Note: vCpeResCust isn't done yet. Waiting for Homing BB integration.
Change-Id: I9c6bcbd13eb1857085cb44d9aabe96ffb600b9a1
Issue-id: SO-147
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
|
|
|
|
Generate the nsParameters from the request body
Change-Id: I31cdcb3a576d031dc6606dd4fabf7c2401786ab2
Issue-ID:SO-57
Signed-off-by: c00149107 <chenchuanyu@huawei.com>
|
|
|
|
Pre deal the parameters for NS create
Change-Id: I43afdbceb262d881e6a501c41ee2cf6e50173ad6
Issue-ID:SO-57
Signed-off-by: c00149107 <chenchuanyu@huawei.com>
|
|
Add the details task of NS create workflow
Change-Id: Ic3ee8c2659ae2cdc9b91b5eaf318dd655d87f711
Issue-ID:SO-57
Signed-off-by: c00149107 <chenchuanyu@huawei.com>
|
|
Adding network id before Underlay VPN in E2E svc creation
IssueId: SO-152
Change-Id: If6311914633c7247b62362ca9371c54c426889bc
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
|
|
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>
|
|
IssueId: SO-146
Change-Id: I483f96eea7be409546ebc5c84e2332b2992672e7
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
Add VFC NS create sub work flow
Change-Id: I503419f89633a0f74a887bc3b95fbaa3acdbfd02
Issue-ID:SO-57
Signed-off-by: c00149107 <chenchuanyu@huawei.com>
|
|
IssueId: SO-146
Change-Id: Id247132c451e16c49dde8b8547d50924cdfa00c4
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
IssueId:SO-56
Change-Id: Icb04ea102b1fe497d8827eac582b28a472bbb836
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
|
|
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>
|
|
|
|
Fix Blocker/Critical sonar issues in so module
https://sonar.onap.org/component_issues?id=org.openecomp.so%3Aso#resolved=false|severities=CRITICAL
Fixed String with no format specifiers
Issue-Id:SO-118
Change-Id: Ie5257d1a01a9c2e6cf25a453a4c602376a69a396
Signed-off-by: shashikanth.vh <shashikanth.vh@huawei.com>
|
|
Fix Blocker/Critical sonar issues in so module
https://sonar.onap.org/component_issues?id=org.openecomp.so%3Aso#resolved=false|severities=BLOCKER
Fixed condition that always evaluate to "true"
Issue-Id:SO-118
Change-Id: Iceec8653cad6c2ca5dc148644c761075fe207a66
Signed-off-by: shashikanth.vh <shashikanth.vh@huawei.com>
|
|
|
|
|
|
|
|
Issue-Id: SO-142
Change-Id: I2adbf796f46cb400d32ada1d7f0ae671e58b00ad
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
Issue-ID: SO-46
Change-Id: I01b80c4eb5ee6c779dd95b840fa99a9bff0ad78e
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
Issue-Id: SO-141
Change-Id: Ie08e5a03f1448071ce0d31ca0829b28d791c05fd
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
|
|
Add sync response task for e2e service flow
Change-Id: I3b17e0103fb3e7cb4ba41d076bc6014acc1d295c
Issue-ID:SO-57
Signed-off-by: c00149107 <chenchuanyu@huawei.com>
|
|
Add groovy logic for E2E service
Change-Id: I3d3f1023c14d2621380933396fbc650516145da2
Issue-ID:SO-57
Signed-off-by: c00149107 <chenchuanyu@huawei.com>
|
|
|
|
|
|
IssueId: SO-118
Change-Id: Ib7830bb47d41f322a14bc82b7bc99748b547d640
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
|
|
IssueId: SO-118
Change-Id: I19221e6b4c41db7f00201dbc6805e76068bf099e
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
|
|
|
|
Issue-Id : SO-117
Change-Id: Icdc64605b475e20af7e871135af327f7d0e38792
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
|
|
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>
|
|
IssueId: SO-120
Change-Id: I58aaff6213fcc91388f1cabf3ca37838a25c1c73
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
IssueId: SO-120
Change-Id: I4282112764bc7697dd98e780bb02b13319cabb5d
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
|
|
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>
|
|
Issue ID: SO-98
Change-Id: Ida8eba238c3c0ca867cc40a58d00ddcd74417921
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
Issue-Id : SO-98
Change-Id: I229819e850c36fce9f8715d1534f8e5c5d812a0a
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
When SO is calling AAI REST API in groovy code, it is always passing new
X-TransactionID. As per EELF logging guidelines, this id is used for
tracking transaction across components. This fix checks if there is
already an existing transaction id in MDC, if yes then pass same. If not
found, then create one and set in MDC for use in next API calls in same
transaction.
Change-Id: If6e33b77d9615f4887e1c1fc367de4268eecc340
Issue-ID: SO-78
Signed-off-by: anupmarathe <anup.marathe@amdocs.com>
|
|
The top level pom will contain:
<groupId>org.openecomp.so</groupId>
<artifactId>so</artifactId>
Child modules will contain:
<parent>
<groupId>org.openecomp.so</groupId>
<artifactId>so</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: I1976819df459d92937c6a4780959c32599dc3e71
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
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>
|
|
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>
|
|
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>
|
|
|
|
|