-
Bug
-
Resolution: Done
-
Highest
-
Beijing Release
-
None
-
None
Sev 1 - Property assignments (needed for preload automation) on SDC UI is not grouped by VM/VNFC type(s), instead it lists ALL VMs/VNFCs. This is an issue affecting preload automation
We just started working on a VoIP VNF vCCF to test out preload automation for VoIP. We have issues (not just related to VoIP, it will be the same for Mobility as well)
Enclose is the vCCF HEAT zip – it has only one module, the base. It contains 3 VM types – iox, plt & app. Each VM type has multiple instances – 2 ioxes, 2 plts, 3 apps.
When we go do property assignments, we had expected to see on SDC UI 3 VM types (consolidate all VMs for each VM type) to fill in properties. This is also the expectation of SDNC – per SDNC SE Madhu, ie to see 3 VM types in the TOSCA, not each individual VMs.
Instead this is what we see on SDC (see red box highlight)– this is not the complete list, but still you can see EACH VM is listed here, and we end up having to fill out property assignments for each VM, Not on each VM TYPE
The TOSCA model also enumerate each VMs, which is NOT what SDNC expects.
There are also other issues raise by VoIP team – all IP counts should have been able to be extracted out of HEAT and auto filled by SDC.
I have attached the zip, and resource level of TOSCA.