Age | Commit message (Collapse) | Author | Files | Lines |
|
IssueId: SO-120
Change-Id: I6d54eeeb34d8d46c588fd09c417aba3e1f5173b0
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
IssueId: SO-120
Change-Id: I58aaff6213fcc91388f1cabf3ca37838a25c1c73
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
IssueId: SO-120
Change-Id: I01c886124436ec4e29ff7c38f6a3ee397e62b00c
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
IssueId: SO-120
Change-Id: I429381791a209b421349baa9a4adaa32c6e27958
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
IssueId: SO-120
Change-Id: Ic7be2d1eba06cb1b3bb15b7ccec5856d1528e23b
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
IssueId : SO-120
Change-Id: I1a94ec1846caaa8968054eb0124fa7cf7885a432
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>
|
|
IssueId: SO-120
Change-Id: I59982b12d5b538b3f9765410ac26cbdde1844957
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>
|
|
|
|
Change-Id: Ie0948e048a52a8743b919319cca78376e0dfea13
Issue-id: SO-104
Signed-off-by: DeWayne Filppi <dewayne@cloudify.co>
|
|
Change-Id: Iab761e263f1e2380471dd38c2b7ce9b77f0aab0e
Signed-off-by: DeWayne Filppi <dewayne@cloudify.co>
Issue-id: SO-106
|
|
Issue ID: SO-98
Change-Id: Ida8eba238c3c0ca867cc40a58d00ddcd74417921
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
Change-Id: I92221d72fa554aa4246c501e30d523732c4d7f47
Issue-id: SO-105
Signed-off-by: DeWayne Filppi <dewayne@cloudify.co>
|
|
Fix the review comments for vf-c adapter
Change-Id: I1b2a7de490b7d46c07d522f5720ef005bfffe67d
Issue-ID:SO-109
Signed-off-by: c00149107 <chenchuanyu@huawei.com>
|
|
Issue-Id : SO-98
Change-Id: I229819e850c36fce9f8715d1534f8e5c5d812a0a
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
|
|
Add VF-C Adapter to support VF-C APIs
Change-Id: I4eb27755c8c5420343f457e0f9be37aa438361eb
Issue-ID:SO-41
Signed-off-by: c00149107 <chenchuanyu@huawei.com>
|
|
|
|
|
|
|
|
|
|
|
|
Change-Id: I13e4895730da6aa265cc14a15621283b89b1d083
Signed-off-by: DeWayne Filppi <dewayne@cloudify.co>
Issue-id: SO-104
|
|
As per EELF logging guidelines, component can put a calling application
identifier or user name in MDC against key PartnerName. SO is setting
user name against key PartnerName in LogFilter. By having an identity of
calling application can assist in debugging. To achieve this SO will
check request header key X-FromAppId and set its value against MDC -
FromAppId.
Change-Id: Ib67c5e76fdf5567282200e17210ddb49cf9a57fb
Issue-ID: SO-99
Signed-off-by: anupmarathe <anup.marathe@amdocs.com>
|
|
Add Operation Status DB And Interfaces for create/delete progress rest
Change-Id: I1b93f219470b79b0b7e0bdcbb27a0a31408bbf5f
Issue-ID:SO-41
Signed-off-by: c00149107 <chenchuanyu@huawei.com>
|
|
Add VF-C Message Type Enum for log
Change-Id: Ia22d5c4a1652b977020c40085a17e19100232115
Issue-ID:SO-41
Signed-off-by: c00149107 <chenchuanyu@huawei.com>
|
|
Change-Id: I4f218e333db1016f481fd210a1aa97c96a1e3bd7
Signed-off-by: DeWayne Filppi <dewayne@cloudify.co>
Issue-id: SO-102
|
|
|
|
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>
|
|
Desc: Sonar issue fix
Change-Id: I48e45fb9fd51bac3e79feaa47d3078b6614025cf
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
|
|
|
|
define default recipe mapping for any 'source' at level of 'service' and 'network' resources."
|
|
|
|
|
|
Modify MSOLogger to route info messages to debugmso.log instead of errormso.log
Change-Id: Id985e83c336e85083764f0d52e7f7e9bb5a20595
Issue-ID: SO-36
Signed-off-by: pranavdi <Pranav.Dixit@amdocs.com>
|
|
Change-Id: I3a24ab6fc5ba54466bfecaf596a13b8907248ae8
Issue-id: SO-77
Signed-off-by: DeWayne Filppi <dewayne@gigaspaces.com>
|
|
Change-Id: I806c879f7eddadec396adbb72f3fc2117dccbeb5
Issue-id: SO-77
Signed-off-by: DeWayne Filppi <dewayne@gigaspaces.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>
|
|
Change-Id: Ibb34f3d2f7c1fd63e79e6a12394a70ca09cb8034
Issue-id: SO-25
Signed-off-by: DeWayne Filppi <dewayne@gigaspaces.com>
|
|
Change-Id: I5ff93b3d7b2c71c30a618b3224226b37bc18c05e
Signed-off-by: DeWayne Filppi <dewayne@gigaspaces.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>
|