Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
|
|
|
|
|
|
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>
|
|
|
|
|
|
Change-Id: If06c2be264003ab27090adf0a29804d961d28115
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
Change-Id: I794b606687343851f71d63ac055ed1898320216a
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
The duration numbers in getDelay() are all
expressed in milliseconds; the call to
TimeUnit.convert() is fixed to specify milliseconds.
Change-Id: I6b466f7a40a05ebe4afb1c3c39fb862eef2ae40d
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
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>
|
|
The functionality of HttpHeader already exists
in org.apache.http.message.BasicHeader. This change
removes the HttpHeader class and replaces its uses with
BasicHeader.
Change-Id: I828aa7d94a1968dffd928d4ca719f0beff1a0f4b
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
Some files in commonBPMN have been removed as they prevent the war to be
successfully deployed on Jboss + Remove rest interfaces files for
catalog that should not be there anymore
Change-Id: Iaf83f8b60610624e160feac8a96b7eaed7f161d1
Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
|
|
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>
|
|
|
|
Change-Id: I0d67ad98e2e9b409774532715da3959e47e27d13
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
APIResponse is supposed to be immutable, but was exposing
its internals in the getResponseBodyAsByteArray() method.
This change adds the missing defensive copy in that method.
Change-Id: I8a424a4cb72eb703fb425ffbd30ea70d6592f85a
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
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>
|
|
Change-Id: Id054e7a04ce88450c3cfe108c8259c4d287681c8
Signed-off-by: ChrisC <cc697w@intl.att.com>
|
|
Change-Id: Icf233b27421878e3b4a65705ee202f517ef6a78c
Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
Signed-off-by: JulienBe <jb379x@att.com>
|
|
Change-Id: Ia6a7574859480717402cc2f22534d9973a78fa6d
Signed-off-by: ChrisC <cc697w@intl.att.com>
|