...

• Each cloud-region has a list of HPACapabilities and list of flavors. Each flavor is associated with set of discovered HPA capabilities.  There are few ways to represent flavors and capabilities
  • Approach 1:
    • flavors as children to the cloud-region (Already existing)
    • Represent HPA capabilities under each flavor (HPA capabilities as children of each flavor)
  • Approach 2:
    • flavors as children to the cloud-region (Already existing). Also, represent HPA capabilities also children to the cloud-regions.
    • Then provide relationship between flavors and capabilities.
  • Approach 3:
    • Approach 1 +
    • Create another tree with capability to region+flavor list.
  • Which approach to follow?  Some guidance from A&AI team.  Requirement is this:
    • During VNF instantiation, OOF gets hold of hardware requirements and based on that requirements, it needs to find out the best cloud-region and flavor.
    • Would Approach 3 seem possible?
• Each HPACapability is defined as 
  {Capability Name, Schema Version, hardware-architecture, [List of HPAAttributes] - names and values}
• HPAFeatureAttribute is <hpaAttributeKey, hpaAttributeValue>
• Refer Hardware Platform Enablement In ONAP for more specific Capability names and values.

A&AI Schema Changes

Approach1

Image Added

Approach2

Example: Run time view of A&AI graph instance

...