...
cloud-infrastructure and cloud-regions in A&AI DB is in Amsterdam release.
Introducing following:
- EPAHPA-flavor, EPAHPA-feature and EPAHPA-feature-attribute: A given cloud-region may support multiple groups of hardware features. Both Azure and AWS has multiple groups of HW features defined for each region. Azure calls them as "VM Sizes" and AWS calls them as "Instance types". In Openstack world, Openstack VIM administrator also defines multiple groups of HW features (called as flavors in Openstack). EPA HPA-flavor is represents these HW feature groups. Each EPAHPA-flavor has set of EPAHPA-features and each EPAHPA-feature is defined by EPAHPA-feature-attributes.
Sequence Diagrams
Discovery of
...
HPA-flavors when cloud-region is added
Periodic Discovery of
...
HPA-flavors
...
Current AAI Schema
Modified AAI Schema
...
HPA Feature Definition
Requirements that are kept in mind are :
- Expose HW capability of various CPU architecture (Intel x86, ARM etc...) in generic fashion.
- Provide flexibility to expose CPU architecture and vendor specific features.
- Support for multiple Clouds such as Openstack clouds, AWS Cloud, Azure Cloud etc...
- No hardcoding of EPA HPA feature names OR attribute names in ONAP (other than Multi-Cloud plugin)
Following table provides EPA HPA features and attributes. Also, it describes matching constraints for each EPA HPA feature. These constrains are applied while finding the best compute-group for placing VNFC.
Following format is used to represent the EPA HPA feature name:
<Hardware or Software feature>-<Generic feature or CPU architecture/vendor specific featuers>-<feature name>
Attributes are represented as <feature attribute>:<feature value>
...
Integer, Greater than & nearest
...
Enum, Exact match
...
If threading is enabled, this feature provides capability on whether the constituting compute group provides best method
to put all threads as siblings (if prefer is used), must put threads as siblings (if require is used) and isolate across
multiple physical cores (if isolate is used)
...
distribution: <equal or specific>
Valid if <specific>
List of following:
NumaNode.<N> : <No. of vCPUs>
...
Boolean, exact match
List, Greater than & nearest
(All vCPUs across all NUMA nodes can't exceed number of vCPUs
...
This capability exposes Numa capability for vCPUs in the compute-group.
"equal' means when VNF is placed using this compute-group, vCPUs are equally divided across possible NUMA nodes.
"specific" means that CPUs assigned to VNFs are acorss multiple NUMA nodes as specified.
...
distribution: <equal or specific>
Valid if <specific>
List of following:
NumaNode.<N> : <Amount of memory>
Boolean, exact match
List, Greater than & nearest
...
This capability exposes Numa capability for memory in the compute-group.
"equal' means when VNF is placed using this compute-group, memory assigned to VNFs comes equally NUMA nodes.
"specific" means that memory is assigned to VNF is acorss multiple NUMA nodes as specified.
...
TBD...
| <HPA feature name |
|---|
AAI Database examples :
Azure
...