...
- Each cloud-region has a list of HPACapabilities and list of HPA flavors. Each HPA flavor is set of HPA capabilities. There are two few ways to represent flavors and capabilities
- Approach 1:
- Represent HPA flavors in each cloud-region. (HPA flavors as children to the cloud-region)
- Represent HPA capabilities under each HPA flavor (HPA capabilities as children of each HPA flavor)
- Approach 2:
- Represent HPA flavors as children to the cloud-region. 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
{Capability Name, Schema Version, hardware-architecture, [List of HPAAttributes] - names and values} - HPAAttribute is a list of <hpaAttributeKey, hpaAttributeValue>
- ComplexAttribute is a list of list of HPAAttributes. For eg: NUMA might have list of HPAttributes for every NUMA node.
- Refer Hardware Platform Enablement In ONAP for more specific Capability names and values.
...