Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
Issue-ID: SO-3868
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
Change-Id: Ib5a1b8622e6b852f4ecbbbc1f967f26fe0f34b36
|
|
Issue-ID: SO-3848
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
Change-Id: I7070bfc511d79b8a68d2079551829c397f24909f
|
|
|
|
|
|
|
|
Issue-ID: SO-3864
Signed-off-by: deepikasatheesh <deepika.s84@wipro.com>
Change-Id: Ibb7342a2eb6adb44c5a03e717e908699997e79b4
|
|
|
|
|
|
-Catalog DB Changes with new macro action.
Issue-ID: SO-3859
Change-Id: I99f33f225d114d713f42f0a900aeb6532d7c6afe
Signed-off-by: sanket12345 <SX00562924@techmahindra.com>
|
|
-Adding new blocking UpgradeVfModuleBB
-Integrating new block in bpmn-infra wih new macro-action in catalogDB.
-Changes added in Workflow to call UpgradeVfModuleBB.
Issue-ID: SO-3857
Change-Id: I98f81f325a311d723f62f0a802bcd8641b9a6cbc
Signed-off-by: sanket12345 <SX00562924@techmahindra.com>
Signed-off-by: Lukasz.Rajewski <lukasz.rajewski@orange.com>
|
|
-Added new endpoint in API-Handler
-upgradeCnf as new action
Issue-ID: SO-3856
Change-Id: I49f12f215c312b712f32f0a700beb8590b7c6dfe
Signed-off-by: sanket12345 <SX00562924@techmahindra.com>
|
|
-Added new endpoint in CNF Adapter for CNF-Upgrade.
Issue-ID: SO-3858
Change-Id: I68f32f215d232d723f44f1a103acf5431d6c7abe
Signed-off-by: sanket12345 <SX00562924@techmahindra.com>
|
|
Issue-ID: SO-3796
Signed-off-by: Lukasz Muszkieta <lukasz.muszkieta@nokia.com>
Change-Id: I018ecc1b3eb8a8252f8b88dca928d830abb4af14
|
|
Issue-ID: SO-3847
Signed-off-by: deepikasatheesh <deepika.s84@wipro.com>
Change-Id: Ib6d2817bcf3e340713a2f72630915173344b81d5
|
|
Issue-ID: SO-3836
Signed-off-by: MD IRSHAD SHEIKH <md.irshad.sheikh@huawei.com>
Change-Id: I07dc6c8073197aae2aac5ff3ea3429563b3cbb38
|
|
Issue-ID: SO-3844
Signed-off-by: deepikasatheesh <deepika.s84@wipro.com>
Change-Id: I206f0ddbb05c30abedfb558e70d320f547f8b6e7
|
|
Vnfs can be part of different clouds and thus cloud configuration
is fetched from vnf itself and passed along the flow to create vnf
in the correct region.
Issue-ID: SO-3423
Change-Id: I1a91486a0bbc6a13aaa292905caeb0c72c4b4885
Signed-off-by: kuldipr <kuldip.rai@amdocs.com>
|
|
|
|
Re-added Macro DB Entries in below tables
- orchestration_flow_reference
- building_block_detail
Issue-ID: SO-3834
Signed-off-by: sanket12345 <SX00562924@techmahindra.com>
Change-Id: I33f12f156c122d723f52f0a855adb9430b7c6ade
|
|
|
|
|
|
-Enhancement of CNFO model with helm upgrade
-Included code changes with respect to HealthCheckBB
Issue-ID: SO-3814
Signed-off-by: sreejatechm <sg00744975@techmahindra.com>
Change-Id: I44f11f156c132d713f42f0a855adb6730b7c6abe
|
|
|
|
The listener was using a customizationId from the requestPayload.
Since the requestPayload is slightly different for VNF LCM requests,
this logic was inconsistent and not working properly.
By adding modelCustomizationId and modelVersionId to the Resource
class, the SkipCDSBuildingBlockListener can leverage this to perform
more reliable lookups for customization objects.
This also enables SkipCDSBuildingBlockListener to run for delete
requests. Previously this would have failed as the resourceKey is
instance-id in the delete case and customization-id in for create.
By using the explicit property of the resource object, there will
be no confusion.
Issue-ID: SO-3807
Change-Id: I0922e5e7373990d9b409651cb4365e11d5618558
Signed-off-by: Jozsef Csongvai <jozsef.csongvai@bell.ca>
|
|
|
|
|
|
Issue-ID: SO-3786
Signed-off-by: deepikasatheesh <deepika.s84@wipro.com>
Change-Id: I5b7c5376d225043a196a1d92ce24d4ffae47e7e1
|
|
|
|
Issue-ID: SO-3772
Signed-off-by: Lukasz Muszkieta <lukasz.muszkieta@nokia.com>
Change-Id: Ia49b9e849eb4a331295194282e8d656f5eafd75a
|
|
Issue-ID: SO-3764
Signed-off-by: krishnaa96 <krishna981996@gmail.com>
Change-Id: I899191a47a3c50ac7fe6f0633c658fef09a3ad5c
|
|
Issue-ID: SO-3796
Signed-off-by: Lukasz Muszkieta <lukasz.muszkieta@nokia.com>
Change-Id: Ic499c0ec10548f1f2297b66f60faa99e6cd6dd6c
|
|
|
|
Issue-ID: SO-3784
Signed-off-by: krishnaa96 <krishna.moorthy6@wipro.com>
Change-Id: I3214cfe5faf3bc9d10081859d63d5a67ee2d6318
|
|
|
|
Issue-ID: SO-3806
Signed-off-by: deepikasatheesh <deepika.s84@wipro.com>
Change-Id: I95adb639f0037ada945d6216d4bfb0d94f84c59d
|
|
The validator will fail if there are active vf-modules for the vnf.
The downstream vnf-delete macro will delete these vf-modules so the
validator should not apply for this flow.
Change-Id: If45c872e3b06d9dbb925bff21f7643694503c481
Issue-ID: SO-3801
Signed-off-by: Jozsef Csongvai <jozsef.csongvai@bell.ca>
|
|
|
|
Issue-ID: SO-3785
Signed-off-by: deepikasatheesh <deepika.s84@wipro.com>
Change-Id: Id4eea6a32d204f59f11cc93c18555f1ac50b4b55
|
|
|
|
Issue-ID: SO-3796
Signed-off-by: Lukasz Muszkieta <lukasz.muszkieta@nokia.com>
Change-Id: Iaf63f2e80da64795b2c4be107e2288bc36db228b
|
|
|
|
Issue-ID: SO-3787
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
Change-Id: Iaad6c7d570824cf89c642aa1568f909350c100f0
|
|
|
|
|
|
This ensures isBase is set on vf-modules in delete flows, which will
ensure correct deletion order. It also adds a AAI lookup for vnfs to
fetch modelCustomization ids, which are necessary for validations in
service-macro-upgrade.
Issue-ID: SO-3794
Signed-off-by: Jozsef Csongvai <jozsef.csongvai@bell.ca>
Change-Id: I4a6f5eb21633b4a8be8107b290b04c77d854bc0d
|
|
|