Age | Commit message (Collapse) | Author | Files | Lines |
|
Issue-ID: SO-3433
Signed-off-by: Lukasz Muszkieta <lukasz.muszkieta@nokia.com>
Change-Id: If00e2a209cf28a57caa52a840bc8c10164a58ff4
Signed-off-by: Lukasz Muszkieta <lukasz.muszkieta@nokia.com>
|
|
|
|
|
|
|
|
retry on ResponseProcessingException
Issue-ID: SO-3570
Signed-off-by: AT&T Open Source <g22940@att.com>
Change-Id: I62745d3833bec8fb5f33007aa613ff4626b5486d
|
|
restore not NULL verification on user params
include test file missed in commit
Issue-ID: SO-3564
Signed-off-by: AT&T Open Source <g22940@att.com>
Change-Id: I2ad7cff33081b1ccc5369cfc54dccf0eab1f6fbf
Signed-off-by: Benjamin, Max (mb388a) <mb388a@att.com>
|
|
|
|
create protected method for vf module bb logic
Issue-ID: SO-3569
Signed-off-by: AT&T Open Source <g22940@att.com>
Change-Id: I66076655781c8593a78da380f74c028e635b4d5b
|
|
Issue-ID: SO-3566
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
Change-Id: Idf64064827f7d61ef310c4623894fca4d57cb60f
|
|
|
|
Modify/re-use of an existing TN NSSI contains problems since
Guilin release. We have planned to resolve these issues in
Honolulu release. This submission contains these fixes.
Issue-ID: SO-3563
Signed-off-by: hyu2010 <hyu2010b@gmail.com>
Change-Id: If2b22260797135eab3cc74c66e0b9a9ec8d91d65
|
|
Removed unused endpoints from source code
Removed unused jackson mapper configuration
Issue-ID: SO-3557
Signed-off-by: AT&T Open Source <g22940@att.com>
Change-Id: I32df4e49f5adf8cade8d963492495975fc0f11b2
|
|
To fix the issues noticed during testing
- in activate and deactivate flow
- in allocate non-shared: update requestdb correctly when flow is
successful.
Issue-ID: SO-3527
Signed-off-by: aleemraja <ar00500721@techmahindra.com>
Change-Id: I37ce7d61eaba8ea60a95a9517509696b2cf3a357
|
|
Change-Id: Ie3cb635be40a4e1201f759bd706a9c924545a3d3
Issue-ID: SO-3486
Signed-off-by: Mukesh <mukeshsharma@est.tech>
|
|
|
|
|
|
Issue-ID: SO-3554
Signed-off-by: deepikasatheesh <deepika.s84@wipro.com>
Change-Id: I1bce6e7c48e9fcb92505304727ed1a04aed5be05
|
|
This update contains for the fixes for the following JIRAs:
SO-3512: update logical-link name and logical-link id in
TN NSSI
SO-3544: Transport Slicing problems found in RAN NSSMF and
TN NSSMF integration
Issue-ID: SO-3512
Issue-ID: SO-3544
Signed-off-by: hyu2010 <hyu2010b@gmail.com>
Change-Id: I075bf76da635365260bfc52b0fe13ac3cb69c3c7
Signed-off-by: hyu2010 <hyu2010b@gmail.com>
|
|
|
|
This commit fixes default software version source input
for pnfcustomization table. If pnfcustomization has a
value in default software version field that will be picked.
Else first entry of software versions will be picked.
Issue-ID: SO-3543
Signed-off-by: tragait <rahul.tyagi@est.tech>
Change-Id: I10261c2d4c8e816fdaa2ef54d20c7e83b9f41701
|
|
QueryJobStatus"
|
|
This change should not have any effects on functionality as integration
image is built on top of adoptopenjdk/openjdk11:jre-11.0.8_10-alpine.
Benefits from switching over:
* minimal {java11,python} images maintained by integration team
* using currently "blessed by seccom" versions (:latest tag used)
* should limit spread of legal issues across layers
* integration images will be the first to have automated compliance
documentation
* should limit spread of base layers (contributing to deployment
footprint - more base layers = more to download, more to store etc...)
Issue-ID: INT-1864
Signed-off-by: Alexander Mazuruk <a.mazuruk@samsung.com>
Change-Id: Ia7bb95a5518e77ba6eddb7e4512528c920f9e381
|
|
|
|
Change-Id: If35f94bd8459c08c11d5e178ae872f70a36fd9fa
Issue-ID: SO-3486
Signed-off-by: waqas.ikram <waqas.ikram@est.tech>
|
|
|
|
cleaned up plugin and repository management sections
Issue-ID: SO-3539
Signed-off-by: AT&T Open Source <g22940@att.com>
Change-Id: Ibc0c582ee4077c4830c5f6cd3c110f9c6038d8db
Signed-off-by: Benjamin, Max (mb388a) <mb388a@att.com>
|
|
Change-Id: I5ab5d409bad26abd83b2d8338c4c5ab5fa6be97c
Issue-ID: SO-3485
Signed-off-by: waqas.ikram <waqas.ikram@est.tech>
|
|
|
|
|
|
Change-Id: I2b6ef2fd61d08925696cde63c53f16dd87700d52
Issue-ID: SO-3487
Signed-off-by: waqas.ikram <waqas.ikram@est.tech>
|
|
Change-Id: I87ce8344f2f2329066639e6aa2d415eac06ef622
Issue-ID: SO-3538
Signed-off-by: pwielebs <piotr.wielebski@nokia.com>
|
|
Issue-ID: SO-3537
Signed-off-by: mukesh.paliwal <mukesh.paliwal1@huawei.com>
Change-Id: I79b1c1f6f355fb584e30253bedf7ca5ede02e336
|
|
Issue-ID: SO-3536
Signed-off-by: mukesh.paliwal <mukesh.paliwal1@huawei.com>
Change-Id: Id0836f5e7900fdb69fb6f2c04b8657746b801805
|
|
Issue-ID: SO-3432
Change-Id: I0dc26542301bd39398326ba28823453f3183a8a6
Signed-off-by: Kalkere Ramesh, Sharan <sk720x@att.com>
|
|
|
|
|
|
|
|
|
|
Issue-ID: SO-3535
Signed-off-by: mukesh.paliwal <mukesh.paliwal1@huawei.com>
Change-Id: I0fe65312fbde922064f3d464dc783e82fa4d707d
|
|
Issue-ID: SO-3534
Signed-off-by: mukesh.paliwal <mukesh.paliwal1@huawei.com>
Change-Id: I85a7ad93e9a89190805b508be25163bcbdd7c334
|
|
Change-Id: Ibddf8bf20f52c606a514d20f78a025d024686c61
Issue-ID: SO-3529
Signed-off-by: pwielebs <piotr.wielebski@nokia.com>
|
|
Updated camunda to 7.14 and updated spring boot camunda to 3.4
Started to clean up duplicate maven dependencies
Issue-ID: SO-3521
Signed-off-by: Benjamin, Max (mb388a) <mb388a@att.com>
Change-Id: Ic65b04772b91dd989e41d6b6b93872978bc4e4e2
|
|
Issue-ID: SO-2765
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
Change-Id: I563295123f7f8de7164495a7db3bc58872863098
|
|
Issue-ID: SO-2765
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
Change-Id: Ibcf2ac5a29eab84bda1c858354ff1f53518ceac9
|
|
Issue-ID: SO-2765
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
Change-Id: I66583bf031057961c1b243400d0a6004c541a346
|
|
Issue-ID: SO-3526
Signed-off-by: deepikasatheesh <deepika.s84@wipro.com>
Change-Id: I04fd6adced03c535129cf0d2adfee60f6e2b3407
|
|
This reverts commit 40fc9d52b0ca2eaba6d1e30f846797e301dc885b.
Reason for revert: it seems that docker module in SO is triggered by “docker” profile which is only triggered in so-maven-docker-* Jenkins job. Per my understanding these jobs are only used for creating docker images and I think relying on these jobs to create a docker JAR module will create unnecessary dependency. So I think option 3 is more feasible
Change-Id: Ia64778afd8fe4105ee8bf1a2f45a4d5674601289
Issue-ID: SO-3473
Signed-off-by: waqas.ikram <waqas.ikram@est.tech>
|
|
|
|
|
|
|