Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

titleDesign Time - Use Cases



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.

    • 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
titleDesign Time - Use Cases
StepsDescriptionReference NOTEs
Perquisite   
1[APP-C, SDN-C]I ONAP OOM instance is instantiated 
 
2Controller 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
titleRun Time - Use Cases for Instantiation --Option 1: Full ONAP Use Case Starting with SO
StepsDescriptionReference NOTEs
Perquisite    
 1[SDC, SO, 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  
 
  
Assign Create, & Activate   
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.

  • 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


 
Expand
titleRun Time - Use Cases for Instantiation --Option 2: Partial ONAP without SO
1[APP-CI
StepsDescriptionReference NOTEs
Perquisite    
 1 [SDC, DMAAP/UEB, Policy Manager, SDN-C , A&AI] - ONAP OOM instance is instantiated   2Controller Blueprint mS instance is instantiated   Activate Controller Blueprint 
  • 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   
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  
  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       
Expand
titleRun Time - Use Cases for Instantiation
 Netbox mS instance is instantiated      for Service Assign2   Assign
StepsDescriptionReference NOTEs
Perquisite   6 Controller Blueprint mS instance is instantiated  
 7 Naming Policy is preloaded in Policy Manager for vFW  
 1 [SDC, Policy Manager, SDN-C , A&A] - ONAP OOM instance is instantiated    
 2 vFW Heat is preloaded with the SDNC Model information  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.   
 3Assignment SDC TOSCA is ingested in SDNC for vFW   4
1

Script that triggers GR-API   for Service Assign


 
  5 Naming-generation mS instance is instantiated  2

Script that triggers GR-API   for VNF Assign


 
 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   
13

Script that triggers GR-API   for VF Module Assign

 
  • 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

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 3 Script that triggers GR-API   for VF Service Module AssignActivate 
  • 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

 
 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 



Expand
titleRun Time - Use Cases for Instantiation --Option 3: Partial ONAP without SO , DCAE, SDC
StepsDescriptionReference NOTEs
Perquisite    
 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
titleRun Time - Use Cases for Instantiation
 Naming Policy is preloaded in Policy Manager for vFW Script that triggers Macro instantiation vFW request to SO using assign, create an activate building block.Script that copies MD-SAL instance for vFW
StepsDescriptionReference NOTEs
Perquisite  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
 2SDC 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.
 3Netbox mS instance is instantiated    
 1[SDC, SO, Policy Manager, SDN-C , A&A]I ONAP OOM  4Naming-generation mS instance is instantiated      
 2 vFW Heat is preloaded with the SDNC Model information  5Controller Blueprint mS instance is instantiated  
 3 SDC TOSCA is ingested in SDNC  6Naming Policy is preloaded in Policy Manager for vFW  
 4 Netbox mS instance is instantiated    
 5 Naming-generation mS instance is instantiated   7Controller 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.
 8Pre-create A&AI object for service , generic VNF and VF Module.   
 6Assignment Controller Blueprint mS instance is instantiated   7
1

Script that triggers GR-API   for Service Assign


   8 Controller Blueprint is preloaded in mS DB for vFW 
2

Script that triggers GR-API   for VNF Assign


   
Assign Create, & Activate   
13

Script that triggers GR-API   for VF Module Assign

 
  • 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

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
  • 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.
  • 2Activate  
     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