Age | Commit message (Collapse) | Author | Files | Lines |
|
Issue-ID: SO-2519
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
Change-Id: Id0993b244b0978375ff8476e4bf8ef79e1bb9e68
|
|
Added new appc adapter micro service.
Made required code changes to use the new adapter.
Issue-ID: SO-2596
Signed-off-by: Benjamin, Max (mb388a) <mb388a@att.com>
Change-Id: I880ecace64ec85ca4094a82bc1210798fd3bb85d
|
|
Development of SOL002 Adapter
Issue-ID: SO-2574
Signed-off-by: Piotr Borelowski <p.borelowski@partner.samsung.com>
Change-Id: If973a36756e7e89e51797844034673b2a2c40e4f
|
|
all pom.xml files now have two spaces
validation is on for pom.xml files
Change-Id: I424ea2e4d6a549f468792e5f90a43f3a97e6c954
Issue-ID: SO-1781
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
Create maven structure, spring boot application and docker image for the VNFM adapter. Implementation of functionality will follow in subsequent stories.
Issue-ID: SO-1620
Change-Id: I735ead3f1c34bf33e6813a3741609409b0da851c
Signed-off-by: MichaelMorris <michael.morris@est.tech>
|
|
Henceforth, the master branch will be for Dublin work.
Change-Id: I269fd8f227e37afdab9c633f45488c643e5e765e
Issue-ID: SO-1151
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
Change-Id: I95381232eeefcd247a66a5cec370a8ce1c288e18
Issue-ID: SO-670
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
This is code from AT&T's 1712 and 1802 releases.
Change-Id: Ie1e85851e94bc66c4d9514a0226c221939531a04
Issue-ID: SO-425
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
Change-Id: If1df4b792fca2a127e169e393268d63ef31d9ed1
Issue-ID: SO-437
Signed-off-by: Munir Ahmad <munir.ahmad@bell.ca>
|
|
Change-Id: Ib7aea4df7e6a31cf5e1e6513b89bed6f878537af
Issue-ID: SO-372
Signed-off-by: Arthur Martella <amartell@research.att.com>
|
|
Change-Id: I08210bc29f4f6c2f90723b57e30d48c60a81e3bb
Issue-ID: SO-360
Signed-off-by: Lukasz Muszkieta <lukasz.muszkieta@nokia.com>
|
|
Bump minor version in preparation for Amsterdam
branching.
Change-Id: Ib72ca9cab2782a4fee15fff8f0653f0c53ad9f71
Issue-ID: CIMAN-120
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
|
|
IssueId: SO-346
Change-Id: I4bd910032baa26c2aa154d3860bf4d34ecf7d9dd
Signed-off-by: seshukm <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>
|
|
Add VF-C Adapter to support VF-C APIs
Change-Id: I4eb27755c8c5420343f457e0f9be37aa438361eb
Issue-ID:SO-41
Signed-off-by: c00149107 <chenchuanyu@huawei.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>
|
|
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>
|
|
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: Ia6a7574859480717402cc2f22534d9973a78fa6d
Signed-off-by: ChrisC <cc697w@intl.att.com>
|