aboutsummaryrefslogtreecommitdiffstats
path: root/adapters/mso-vnf-adapter
AgeCommit message (Collapse)AuthorFilesLines
2017-10-12Iterate over "entrySet" instead of "keySet"rama-huawei1-4/+8
Issue-id: SO-214 Change-Id: Ic402b02a82bd613b0753db1530dd76ce59c3ad08 Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
2017-10-10Sonar blocker issue - NullPointerExeption - take 2Arthur Martella1-0/+3
Catch potential NullPointerException described in https://sonar.onap.org/issues/search#issues=AV7t547AlaLbmlVXT_jY Semi-duplicate of https://gerrit.onap.org/r/#/c/17703/ Trying again from newer branch which will hopefully fix build failures. Change-Id: I65c9af1ec1a90bed201042cffb45f3871222a889 Issue-ID: SO-165 Signed-off-by: Arthur Martella <amartell@research.att.com>
2017-10-04Merge "Adding UT for MSO Vnf Adapter"Seshu Kumar M3-4/+302
2017-10-03Adding UT for MSO Vnf AdapterSeshu-Kumar-M3-4/+302
IssueId: SO-176 Change-Id: I66f7a522bdd85c65abba57e2802bb5085b4535a7 Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
2017-10-03Not logging or re-throwing the exceptionsrama-huawei1-0/+1
Issue-id:SO-175 Change-Id: I1e1e9e1d6f8bafb4e3a18c6d81565f908753ebf0 Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
2017-10-02Merge "HeatBridge integration with Orchestration, part 1"Rob Daugherty1-0/+45
2017-09-28Merge "Fix some major sonar issues"Seshu Kumar M1-1/+0
2017-09-27Fixed Blocker issues.seshukm1-3/+4
IssueId: SO-165 Change-Id: I7c2520af9394ceb600a5a25fa9acfd095d872a1d Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
2017-09-27Fix some major sonar issuessurya-huawei1-1/+0
*Use collection.isEmpty() instead of collection.size *Remove unnecessary commented line This is done for increasing code readability *Pass the string object directly Instead of wrapping the returned object and creating a new object, passing the object itself will save memory Issue-Id: SO-118 Change-Id: I24c15e9270ec3422d35d3910a8aff9fcf8d632d9 Signed-off-by: surya-huawei <a.u.surya@huawei.com>
2017-09-26HeatBridge integration with Orchestration, part 1Arthur Martella1-0/+45
Adding Heatbridge python code and call into SO. Still needs configuration to be complete. Change-Id: I4869217699d857e27579decce91e9c542ce7a449 Issue-ID: SO-1 Signed-off-by: Arthur Martella <amartell@research.att.com>
2017-09-25Merge "Fix @Override major issues"Seshu Kumar M1-0/+2
2017-09-25Merge "Replaced with Diamond symbol"Seshu Kumar M1-11/+11
2017-09-25Merge "Replaced with Diamond symbol"Seshu Kumar M1-11/+11
2017-09-25Fix @Override major issuesshashikanth1-0/+2
Add the "@Override" annotation above this method signature Issue-Id:SO-118 Change-Id: I0973c1559c66b80a56a9c1ba610ae73bba54fe49 Signed-off-by: shashikanth.vh <shashikanth.vh@huawei.com>
2017-09-25Replaced with Diamond symbolrama-huawei1-11/+11
Issue-Id:SO-118 Change-Id: I6a1542d53c9021e315331a1643519c25500df20a Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
2017-09-25Replaced with Diamond symbolrama-huawei1-11/+11
Issue-Id:SO-118 Change-Id: Ib7c5963521bc2e077a3e4d888ffb30566fd76be5 Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
2017-09-25Replaced with Diamond symbolrama-huawei1-5/+6
Change-Id: I439daab53236cd35e43e3a503ddc4b3218f7d992 Issue-Id:SO-118 Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
2017-09-21SO Failed Robot Health CheckRob Daugherty1-2/+7
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>
2017-09-18Fixed issues in adapter packageseshukm1-30/+25
Issue-Id: SO-141 Change-Id: I1a6905aa7e1328e47b3d0f7580a1dca33c6a069c Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
2017-09-12Fix for SONAR critical issuesseshukm3-21/+32
Issue-Id : SO-117 Change-Id: I57e30d9a8a2b251a57466d92c49f41e2a5943b22 Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
2017-09-11Change the header to SOSeshu-Kumar-M17-17/+17
IssueId: SO-120 Change-Id: I59982b12d5b538b3f9765410ac26cbdde1844957 Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
2017-09-081710 Rebase - Second AttemptArthur Martella3-721/+350
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-08-04Failed to deploy so artifacts in nexus (again)Rob Daugherty1-8/+8
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-8/+8
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-8/+8
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-02[MSO-8] Second step of the rebase for MSODeterme, Sebastien (sd378r)2-158/+174
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 dependencyxg353y11-171/+326
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-01-31Initial OpenECOMP MSO commitChrisC27-0/+5857
Change-Id: Ia6a7574859480717402cc2f22534d9973a78fa6d Signed-off-by: ChrisC <cc697w@intl.att.com>