Page History

...

1. Support for vFW and vDNS use cases (100% in SO, majority will be in by Wed., Green) 
   1. In R2, only vCPE workflow in enhanced to call OOF for homing decisions. Changes are being done in R3 to ensure that SO workflow for vFW and vDNS call OOF for homing decisions. Hence test plan should ensure that both vFW and vDNS use cases are tested with HPA feature.
2. Usage of Multi-Cloud service instead of SO directly communicating with openstack instance in the cloud regions (SO, reference, will get in by late Wed., Yellow; Let PTL know our plan, will update Tue. afternoon) 
   1. In R2, E2E testing was done with SO bypassing Multi-Cloud service.  In R3, SO calls the Multi-Cloud Service. Multi-Cloud service, in turn, communicates with Openstack HEAT in the cloud-regions. Test plan should ensure that SO is configured to work with Multi-Cloud
3. Derivation of HEAT parameters from OOF homing decisions (Depends on #2, Multi-Cloud, 3 test patch submitted, reviewed and modified, left to be merged, Green; Get it in by Wed., talk to Bin ) 
   1. In R2, HEAT parameters and its values are generated based on OOF homing decision as SO was calling Openstack HEAT service directly. In R3, as mentioned above, the communication with HEAT is moved to Multi-Cloud service. As part of that changes are made to Multi-Cloud API to accept oof_directives and sdnc_directives.  Multi-Cloud service is expected to generate HEAT parameters & it values from these directives.  Test plan should ensure that HEAT parameters and values generated by Multi-Cloud are as expected.
4. SRIOV-NIC HPA feature support in R3: (Depends on #2 & #3, OOF & Multi-Cloud, assume hard template, Haibin submitted the patch and merged for HEAT; Ruoyu submitted the patch yesterday, need sometime to review,  work with Shankar make sure merged by Wed., prioritize Ruoyu's patch; Green) 
   1. SRIOV-NIC HPA feature is added in R3.  It allows VFCs that require SRIOV-NIC VFs would be placed in the right site and with right flavor. Test plan should ensure that OOF makes right decisions and right Openstack flavor is selected.
5. Cloud-region and flavor selection enhancements in OOF( OOF, Merged, Green, missing E2E integration testing, can be done after M4) 
   1. In R2, OOF is selecting always the first region that match all mandatory requirements of VNF. If there are multiple regions that satisfy mandatory requirements of VNF, then selection is expected to be based on the best score.  This enhancement is being done in R3.  Test plan should cover to ensure that the right region with best score is selected in case of multiple regions.
6. Cloud-specific features exposed through HPA Policy framework: (VMWare is working on this item, adding a new HPA feature)
   1. VMWare is adding some cloud-specific features using HPA policy and thereby making the cloud technology specific feature agnostic to ONAP. Test plan should ensure that VIO specific features are tested without having to have any special logic in ONAP (except for VIO plugin) along with rest of HPA features.
7. Support for vCPE use case (VNFSDK, code is in, still need to cook up a patch for the change, Lianhao to send email and copy Alex for the two JIRA items pending; SDC is not ok; VF-C, all patches submitted and merged; Policy is working) 
   1. In R2, SO is only component calling OOF for homing decisions and hence HPA feature only works with SO based use cases.  In R3, VF-C (NSLCM) is being enhanced to talk to OOF and hence VF-C based use cases and corresponding VNFs can leverage the OOF returned information such as the cloud-region and flavor to use.  Test plan should ensure that vCPE use case is tested to ensure that right openstack flavor is selected.  These test cases test multiple functions such as 'auto creation of HPA policies from TOSCA', 'SDC client in policy framework' and few changes made in SDC to fix some gaps in TOSCA parser.
8. HPA telemetry and HPA state based placement decisions (stretch goal, may not happen in R3 time frame) :  No test plan is going to be written for this. (Send Kiran and Eric email)

HPA & Cloud Agnostic Policy & A&AI data examples: OOF R3 HPA & Cloud Agnostic policies

...