...
- Data centers typically have flavors (openstack calls them flavors, Azure calls them VM sizes and AWS calls them as Instance types). Each flavor is represented by hardware features. When these are discovered by ONAP, there are few ways to represent them in A&AI DB.
- 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?
- Approach 1:
- Each HPACapability is defined as
{HPACapability-id,HPAFeature, Schema Version, hardware-architecture, [List of HPAAttributes] - names and values} - HPAFeatureAttribute is <hpaAttributeKey, hpaAttributeValue>
- Refer Hardware Platform Enablement In ONAPSupported HPA Capability Requirements(DRAFT) for more specific Capability names and values.
...