Steps | Description | Reference | NOTEs |
---|
Perquisite | | | |
1 | [SDC, DMAAP/UEB, Policy Manager, SDN-C , A&AI] - ONAP OOM instance is instantiated | | - Yuriy to follow up with Dan T/Lalena if its enough to have SDC/DMAAP and SDNC for ingestion of the tosca model?
- Brian Freeman will help with OPEN-LAB spin of the ONAP instance needed for the vFW use case.
- OPEN LAB-- SB07
|
2 | vFW Heat is preloaded with the SDNC Model information | | |
3 | SDC TOSCA is ingested in SDNC for vFW | | - Verify the VF-Model table has all the information related to the SDNC Model Name, Artifact Name and Model Version.
- Yuriy to work with Marco.
|
4 | Netbox mS instance is instantiated | | |
5 | Naming-generation mS instance is instantiated | | |
6 | Controller Blueprint mS instance is instantiated | | |
7 | Naming Policy is preloaded in Policy Manager for vFW | | |
8 | Controller Blueprint is preloaded in mS DB for vFW | | - Yuriy to check with Brinda as part of the mS spin up if we can preload the Controller Blueprint for vFW use case.
|
9 | Pre-create A&AI object for service , generic VNF and VF Module. | | |
Assignment | | | |
1 | Script that triggers GR-API for Service Assign |
| |
2 | Script that triggers GR-API for VNF Assign |
| |
3 | Script that triggers GR-API for VF Module Assign | | |
4 | Script that triggers copy of MD-SAL Config tree for VNF and VF Module for vFW | | - Verify the Resource Accumulator is triggered to return the controller blueprint to GR-API
- Verify the Naming mS generate the name per vFW Naming Policy for the VF Module
- Verify the Netbox Capability assigns an IP Address
- Verify A&AI has VNFC inventory.
|
Activate | | | |
1 | Script that triggers GR-API for VF Module Activate | | |
2 | Script that triggers GR-API for VNF Module Activate | | |
3 | Script that triggers GR-API for Service Module Activate | | |
4 | Script that triggers copy of MD-SAL Config tree for VNF and VF Module for vFW | | |