Assumption:
- That the regression test suite will cover the existing use case for vFW instantiation using the preload mechanism.
The CDS initiative will add a new test suite for testing the vFW instantiation use case with the automated assignment mechanism using the self-service flow integrated with CDS for Casablanca Release.
Action Items:
...
Yang to enhance the robot script for the option 2 use case if SO code is stable. Else we will focus on Option 1.
...
Yuriy to follow on the action items for the SO Payload, GR-API Payload and Ingestion of Tosca and Blueprint information.
Yuriy to follow up with Brian on the SB07 lab setup. Are the minimal set of component available for option 2?
...
Assumption:
- That the regression test suite will cover the existing use case for vFW instantiation using the preload mechanism.
The CDS initiative will add a new test suite for testing the vFW instantiation use case with the automated assignment mechanism using the self-service flow integrated with CDS for Casablanca Release.
Action Items:
- Yang to check the existing robot script.
Yang to enhance the robot script for the option 2 use case if SO code is stable. Else we will focus on Option 1.
Yuriy to follow on the action items for the SO Payload, GR-API Payload and Ingestion of Tosca and Blueprint information.
Yuriy to follow up with Brian on the SB07 lab setup. Are the minimal set of component available for option 2?
[SDC, DMAAP/UEB, SO, Policy Manager, SDN-C , A&A]I ONAP OOM instance is instantiated
Yang to estimate the work effort required for the vFW instantiation use case.
Yuriy to create the JIRA US for the testing use case.
| Expand |
|---|
| title | 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. | | - Yuriy to verify with Brinda on the Payload API needed for the blueprint creation and activation.
| | 2 | Script to Activate and Publish the Controller Blueprint | | - Yuriy to verify with Brinda on the Payload API needed for the blueprint creation and activation.
| | 3 | Script to Verify the Controller blueprint is persisted in the DB | | | | | | | | | | | | | | | | | |
|
| Expand |
|---|
| title | Run Time - Use Cases for Instantiation --Option 1: Full ONAP Use Case Starting with SO |
|---|
|
| Steps | Description | Reference | NOTEs |
|---|
| Perquisite | | | | | 1 | [SDC, SO, DMAAP, Policy Manager, SDN-C , A& |
|
...
...
| ONAP OOM instance is instantiated | |
|
...
Yang to estimate the work effort required for the vFW instantiation use case.
Based on the effort Yang will might request additional effort and/or work with CDS team to help with the robot script implementation.
...
Yuriy to create the JIRA US for the testing use case.
| Expand |
|---|
| title | Design Time - Use Cases |
|---|
|
| Steps | Description | Reference | NOTEs |
|---|
| Perquisite | - 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.
| | 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 | | | 1 | 5 | [APP-C, SDN-C]I ONAP OOM Naming-generation mS instance is instantiated | | | 2| 6 | Controller Blueprint mS instance is instantiated | | | | Activate Controller Blueprint 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 to use the API to create a controller blueprint for vFW. | | - Yuriy to verify with Brinda on the Payload API needed for the blueprint creation and activation.
| | 2 | Script to Activate and Publish the Controller Blueprint | | - Yuriy to verify with Brinda on the Payload API needed for the blueprint creation and activation.
| | 3 | Script to Verify the Controller blueprint is persisted in the DB | | | | | | | | | | | | | | | | | | Script that triggers Macro instantiation vFW request to SO using assign, create an activate building block. |
| Yuriy to request SO team on the Payload for the MACRO Instantiation request. | | 2 | Script that copies MD-SAL instance for vFW |
| |
|
| Expand |
|---|
| title | Run Time - Use Cases for Instantiation --Option 12: Full ONAP Use Case Starting with Partial ONAP without SO |
|---|
|
| Steps | Description | Reference | NOTEs |
|---|
| Perquisite | | | | | 1 | [SDC, SO, DMAAP/UEB, Policy 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 |
| | | | Assign Create, & Activate| 2 | Script that triggers GR-API for VNF Assign |
| | | | 3 | 1 | Script that triggers | Macro instantiation vFW request to SO using assign, create an activate building block.Yuriy to request SO team on the Payload for the MACRO Instantiation request.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.
| 2 | Script that copies MD-SAL instance | | 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 | | |
|
| Expand |
|---|
| title | Run Time - Use Cases for Instantiation --Option 23: Partial ONAP without SO , DCAE, SDC |
|---|
|
| 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 3 | Netbox mS instance is instantiated | | | | 5 4 | Naming-generation mS instance is instantiated | | | | 6 5 | Controller Blueprint mS instance is instantiated | | | | 7 6 | Naming Policy is preloaded in Policy Manager for vFW | | | | 8 7 | 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 8 | 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 | | 2 | Script that triggers GR-API for VNF Module Activate- 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 | | | | | Activate | | | | | Steps | Description | Reference | NOTEs |
|---|
| 3 1 | 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 | | |
|
| Expand |
|---|
| title | Run Time - Use Cases for Instantiation --Option 3: Partial ONAP without SO , DCAE, SDC |
|---|
|
| Perquisite VF Module Activate | | | | 2 | | 1 | [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 | 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.
| | 3 | Netbox mS instance is instantiated | | | | 4 | Naming-generation mS instance is instantiated | | | | 5 | Controller Blueprint mS instance is instantiated | | | | 6 | Naming Policy is preloaded in Policy Manager for vFW | | | | 7 | 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.
| | 8 | 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 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 | | |
|
| Expand |
|---|
| title | Run Time Test Case Progress |
|---|
|
| Steps | Description | Status | NOTEs |
|---|
| | | | | 1 | Robot Script to Trigger SO for Macro Instantiation Request | Complete | | | 2 | SO Triggers A&AI for Service Creation | Complete | | | 3 | SO Trigger SDNC for Service Assign | Complete | | | 4 | SO Triggers A&AI for VNF Object Creation | Complete |
| | 5 | SO Triggers SDNC for VNF Assign | Complete |
| | 6 | SDNC Triggers Resource Accumulator mS | Complete | | | 7 | SDNC Trigger Naming mS | Complete | | | 8 | Naming mS retrieves Policy Instance from Policy Manager | Failed | Naming mS Is not configure with policy manager URL. | | 9 | Naming mS Generates the name and returns the output to SDNC | Pending | | | 10 | SDNC Triggers Netbox IP Capability | Pending | | | 11 | Netbox Assign IP and Returns the values to SDNC | Pending | | | 12 | SDNC Triggers A&AI Updates | Pending | | | 13 | SDNC returns status to SO | Pending | | | | NOTE Steps 14 to 21 will be repeated for base and each add on vf module (base template, vFW, vPG, vSN) | Pending | | | 14 | SO Triggers SDNC with VF Module assign | Pending | | | 15 | SDNC Triggers Resource Accumulator mS | Pending | | | 16 | SDNC Trigger Naming mS | Pending | | | 17 | Naming mS retrieves Policy Instance from Policy Manager | Pending | | | 18 | SDNC Triggers Netbox IP Capability | Pending | | | 19 | Netbox Assign IP and Returns the values to SDNC | Pending | | | 20 | SDNC Triggers A&AI Updates | Pending | | | 21 | SDNC returns status to SO | Pending | |
| | | |
| | | |
|