...

• SO/Multi-Cloud 
  • Check the profile returned by OOF.
  • For each CP of VDUs/VNF, 
    • Check whether that CP requires SRIOV-NIC and verify whether the NIC supported by that profile.
  • If above condition is true for all CPs, then there si no change required in HEAT information.
  • If not, modify appropriate portion of HEAT information from SRIOV-NIC to normal vswitch.

VF-C with HPA policies

In ONAP, there are two projects are doing similar orchestration - SO and VF-C.  SO to OOF integration with HPA is done in R2.  VF-C to OOF integration with HPA is slated for R3.

We believe there are following activities:

• Though VF-C understand TOSCA based models,  we will not touch existing HPA capability support as VF-C will be moving to support new TOSCA models (R3 based models).  Hence, we don't expect to work on auto-creation of HPA policies based on R2 DM HPA information.  Only R3 DM HPA to HPA policies will be supported.  This work will not be started until VF-C supports R3 model.
• Support VF-C and OOF integration with manually created HPA policies
  • VF-C (GVNFM) to OOF integration  to get the best region and set of flavors (compute profiles)
  • Pass this compute profile (for each PDU) to the Multi-Cloud instead of asking Multi-Cloud to create the compute profile.
• Since, GVNFM is not used by any use case, make vFW use case work with VF-C.

Features that are being carried over from R2

...