Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
The fallout and completion handlers are not updating
the request status in the mso_requests database.
The cause is a missing URN mapping that defines the
service endpoint for these updates.
Issue: SO-230
Change-Id: I5b4ff6e9ca2cde6605b3ed7cb7b086041111d31c
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
The code already included "BPMN" and MsoLogger.getServiceName() as
additional arguments in the call to warn() and error(). Simply added
those same arguments to the call to info(), to match the method
signature.
Issue-Id: SO-244
Change-Id: Ic6297d67329358a3b9cdb480d930dc032b7029a2
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Issue-id: SO-224
Change-Id: Ib4e15f7db253d8af8f73d2185afd950f33c1a8ac
Signed-off-by: Ramanjaneya-Huawei <ramanjaneya.palleti@huawei.com>
|
|
The exception occurs because the default process engine is
being used to handle the callback. Until we come up with a
better design, we will use the "infrastructure" process
engine.
Issue: SO-76
Change-Id: Ibe8a40ac28b2ae855f85094f57d878ee622349a0
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
Replaced the license in several groovy scripts with reference to the
Apache license, as is standard for ONAP.
Change-Id: I2be9aef096a95fe70b82579d0a2f6ee88b3caf03
Issue-Id: SO-238
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
|
|
Issue-id: SO-224
Change-Id: I98e6b2de01514f2e2c705c9f880057bb977ff075
Signed-off-by: Ramanjaneya-Huawei <ramanjaneya.palleti@huawei.com>
|
|
Change-Id: I0cbfeb8931a46ccd0b2f759c95adea49c5825af2
Issue-id: SO-224
Signed-off-by: Ramanjaneya-Huawei <ramanjaneya.palleti@huawei.com>
|
|
Added additional junit tests for VCPE and fixed bugs that were found while
testing.
Change-Id: Icb6a0c936a16b775ff553c11cb07a4348bd9ebfc
Issue-ID: SO-210
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Change-Id: Idbf4c87544c92dc6b744a859c024c773ec00e2cd
Issue-id: SO-138
Signed-off-by: Arthur Martella <amartell@research.att.com>
|
|
Flows in the MSOCommonBPMN jar, which is embedded in the
MSOInfrastructureBPMN war, are not being deployed.
MSOCommonBPMN needs a processes.xml file.
I'm also fixing a problem with CustomE2EGetService.bpmn, which claims
it is the GenericGetService flow. This creates a conflict with the
real GenericGetService flow.
Issue: SO-199
Change-Id: I1ec9d4ad079abf65b5c276b625b46a86805a15e6
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
1. Coordinated jacoco and surefire JVM arg line options
2. Changed sonar plugin version to 2.19.1
3. Removed dead code (unused classes)
Issue: SO-193
Change-Id: I21b7a77510eec71f4d4ca9afde5b7f86f0e3cbd7
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
Change-Id: I5bc9dc02ac81789dc0b113571c073e74d8cee609
Issue-Id:SO-118
Signed-off-by: ramanjaneya <ramanjaneya.palleti@huawei.com>
|
|
|
|
|
|
|
|
|
|
|
|
Fix the AAI java package names that was still openecomp,
remove the variable for LF repositories due to Oparent, Fix the
jacoco to overwrite the oparent settings (fix test coverage)
Change-Id: I40b9b326e33ff27992a1bf2cc9d3094d338f8828
Issue-ID: SO-168
Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
|
|
* changes:
Fix code complexity
Use diamond operator(<>)
|
|
|
|
Issue-Id:SO-118
Change-Id: Iaad28a363586cd8b42e86bd7e854faa9e716c59d
Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
|
|
Issue: SO-71
Change-Id: I91d503b52909cfcb62ca4b5cd93f6cfc70d6eb24
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
Issue-Id:SO-118
Change-Id: I96a1fb659bafd204221c5ff8f3d0b680a36dba9d
Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
|
|
Issue-Id:SO-118
Change-Id: I5db909a4c2bfb803c3d3647f30cfa4533c729148
Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
|
|
Issue-Id:SO-118
Change-Id: I3f749777618e506efe4b83314e45574455639f7b
Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
|
|
Major Sonar Issue
*Replace type specification with diamond operator
This is done to reduce the verbosity of generics code
Issue-Id: SO-118
Change-Id: Id1a6e6d2e03f6f92a0e36b9326df61154c0ba910
Signed-off-by: surya-huawei <a.u.surya@huawei.com>
|
|
Fix major sonar issues in so module
https://sonar.onap.org/component_issues?id=org.openecomp.so%3Aso#resolved=false|severities=MAJOR|rules=squid%3AS1161
Add the "@Override" annotation above this method signature
Issue-Id: APPC-186
Change-Id: I0a93e48f921c968ab9a43fc0599ba16d2349db40
Signed-off-by: shashikanth.vh <shashikanth.vh@huawei.com>
|
|
Fix major sonar issues in so module
https://sonar.onap.org/component_issues?id=org.openecomp.so%3Aso#resolved=false|severities=MAJOR|rules=squid%3AS1161
Add the "@Override" annotation above this method signature
Issue-Id: APPC-186
Change-Id: Ia896df35c7f81f3f149e3f7cf06656dafc0a7abf
Signed-off-by: shashikanth.vh <shashikanth.vh@huawei.com>
|
|
String contains no format specifiers.
https://sonar.onap.org/component_issues?id=org.openecomp.so%3Aso#resolved=false|severities=CRITICAL
Issue-Id:SO-118
Change-Id: Ibcb5124a98ea689a01461dddc42a4aa1db147a20
Signed-off-by: shashikanth.vh <shashikanth.vh@huawei.com>
|
|
Issue: SO-159
Change-Id: Ic3e442eaa7603b52a2e32e8395ca8ff9bc069f75
Signed-off-by: Krzysztof Kwiecien <krzysztof.kwiecien1@orange.com>
|
|
Files regarding the Homing building blocks added for use in vCPE flows.
Change-Id: Iae9eb70b81ec7d473e6c4e9c821a9282dc40baa9
Issue-id: SO-138
Signed-off-by: Arthur Martella <amartell@research.att.com>
|
|
IssueId: SO-146
Change-Id: Id247132c451e16c49dde8b8547d50924cdfa00c4
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
|
|
|
|
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>
|
|
Fix Blocker/Critical sonar issues in so module
https://sonar.onap.org/component_issues?id=org.openecomp.so%3Aso#resolved=false|severities=CRITICAL
Fixed String with no format specifiers
Issue-Id:SO-118
Change-Id: Ie5257d1a01a9c2e6cf25a453a4c602376a69a396
Signed-off-by: shashikanth.vh <shashikanth.vh@huawei.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>
|
|
Issue-Id : SO-117
Change-Id: Icdc64605b475e20af7e871135af327f7d0e38792
Signed-off-by: seshukm <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: 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>
|
|
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>
|
|
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>
|