You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Design Time - Use Cases
Steps | Description | Reference | NOTEs |
---|
Perquisite | | | |
1 | [APP-C, SDN-C]I ONAP OOM instance is instantiated |
| |
2 | Controller Blueprint mS instance is instantiated |
| |
Activate Controller Blueprint | | | |
1 | Script to use the API to create a controller blueprint for vFW. | | |
2 | Script to Activate and Publish the Controller Blueprint | | |
3 | Script to Verify the Controller blueprint is persisted in the DB | | |
| | | |
| | | |
| | | |
Run Time - Use Cases for Instantiation
Steps | Description | Reference | NOTEs |
---|
Perquisite | | | |
1 | [SDC, Policy Manager, SDN-C , A&A] - ONAP OOM instance is instantiated | | |
2 | vFW Heat is preloaded with the SDNC Model information | | |
3 | SDC TOSCA is ingested in SDNC for vFW | | |
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 | | |
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 | | |
Run Time - Use Cases for Instantiation
Steps | Description | Reference | NOTEs |
---|
Perquisite | | | |
1 | [SDC, SO, Policy Manager, SDN-C , A&A]I ONAP OOM instance is instantiated | | |
2 | vFW Heat is preloaded with the SDNC Model information | | |
3 | SDC TOSCA is ingested in SDNC for vFW | | |
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 | | |
|
| | |
Assign Create, & Activate | | | |
1 | Script that triggers Macro instantiation vFW request to SO using assign, create an activate building block. |
| - 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 VNF Module
- 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.
|
2 | Script that copies MD-SAL instance for vFW |
| |