...

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

Affinity/Anti-Affinity & Impact on HPA compute profile selection

There is some discussion about introducing Affinity and Anti-Affinity policies in OOF as part of R3.  As we understand, affinity/anti-affinity rule granularity is at

• NFVI-PoP level.
• Availability zone level
• NFVI-node level

NFVI-node level may not be relevant for ONAP.

Currently, input to HPA filter is just set of regions (NFVI-PoPs).  This may need to be enhanced to support "availability zones'.

Also, HPA filter may need to output best availability zone within NFVI-PoP (region).

Features that are being carried over from R2

...