summaryrefslogtreecommitdiffstats
path: root/common
AgeCommit message (Collapse)AuthorFilesLines
2017-09-28Merge "Removed the unused variables"Seshu Kumar M1-1/+1
2017-09-27Merge "Fixed Blocker issues. IssueId: SO-165"Rob Daugherty2-12/+27
2017-09-27Fixed Blocker issues.seshukm2-12/+27
IssueId: SO-165 Change-Id: I7c2520af9394ceb600a5a25fa9acfd095d872a1d Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
2017-09-27Removed the unused variablesrama-huawei1-1/+1
Issue-Id:SO-118 Change-Id: I979370f8d3ffa0382856353aa189610d24dcd20c Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
2017-09-27Update POM to inherit from oparentRob Daugherty21-0/+420
Issue: SO-71 Change-Id: I91d503b52909cfcb62ca4b5cd93f6cfc70d6eb24 Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-09-23Yang decoderZhuoyao Huang22-0/+1692
Change-Id: I4e264c33915969f883ebc3721e7020fb1256682c Issue-ID: SO-88 Signed-off-by: Zhuoyao Huang <10112215@zte.com.cn> description: It could help SO to use the restconf interface which is generated by yang-tools in SDN-C directly.
2017-09-12Fix for SONAR critical issuesseshukm2-0/+5
Issue-Id : SO-117 Change-Id: Icdc64605b475e20af7e871135af327f7d0e38792 Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
2017-09-11SO header changes for JsonSeshu-Kumar-M2-2/+2
IssueId: SO-120 Change-Id: I6d54eeeb34d8d46c588fd09c417aba3e1f5173b0 Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
2017-09-11Change the header to SOSeshu-Kumar-M27-27/+27
IssueId : SO-120 Change-Id: I1a94ec1846caaa8968054eb0124fa7cf7885a432 Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
2017-09-081710 Rebase - Second AttemptArthur Martella38-3192/+234
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-09-04Merge "Fix to get calling application identifier"Seshu Kumar M2-0/+8
2017-08-30Fix to get calling application identifieranupmarathe2-0/+8
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>
2017-08-30Add VF-C Message Typec001491071-0/+1
Add VF-C Message Type Enum for log Change-Id: Ia22d5c4a1652b977020c40085a17e19100232115 Issue-ID:SO-41 Signed-off-by: c00149107 <chenchuanyu@huawei.com>
2017-08-09Fix defect SO-36pranavdi1-102/+103
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>
2017-08-04Another attempt to fix deploy problemRob Daugherty1-1/+1
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>
2017-08-04Failed to deploy so artifacts in nexus (again)Rob Daugherty1-3/+3
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-4/+4
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-3/+3
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-09[MSO-8] Additional fixes for the second rebaseDeterme, Sebastien (sd378r)1-230/+231
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)2-5/+11
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 dependencyxg353y4-6/+104
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>
2017-03-13Update to version 1.1.0ChrisC1-1/+1
Change-Id: Id054e7a04ce88450c3cfe108c8259c4d287681c8 Signed-off-by: ChrisC <cc697w@intl.att.com>
2017-02-14Modification of the MsoLogger methodsDeterme, Sebastien (sd378r)1-436/+589
Method Signature changed to let new opensource based project define their own Log Enum Change-Id: I3e010695c6567fbbf8ea0efbea2c89c50938680d Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
2017-02-10Removal of powermock injection in WARDeterme, Sebastien (sd378r)1-0/+10
THere were transitive dependencies to powermock due to the import of the EELF library. This has been excluded from the MSO common lib, and therefore no War importing it will have the powermock anymore Change-Id: I1d3170d52d9e76ffc002adf4f94f55c2bb3d7828 Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
2017-01-31Initial OpenECOMP MSO commitChrisC65-0/+9305
Change-Id: Ia6a7574859480717402cc2f22534d9973a78fa6d Signed-off-by: ChrisC <cc697w@intl.att.com>