Page History

...

Cloud agnostic placement attributes are targeted to abstract the following cloud specific placement attributes
- HPA attributes (e.g. Smart NIC Family, GPU Family) based on Cloud specific HW/SW support
- Normalized CPU capacity for VMs/Containers based on Cloud specific HW support
  - Reference for CPU Normalization: https://d1.awsstatic.com/whitepapers/Demystifying_vCPUs.df200b766578b75009ad8d15c72e493d6408c68a.pdf
- Fine-grained Placement attributes (based on Cloud specific SW support
  - e.g., Rack-level Anti-affinity
  , anti-affinity, specific physical DC) based on Cloud specific SW support
  - -> Azure: Fault-Domain, AWS: Placement-Group
  - e.g., Exclusivity -> Azure: Isolated VM, AWS: Dedicated Host
  - e.g., Fine grained QoS -> VMware Minimum guarantee, Kubernetes Burstable Class
For the 5G Service/VNF placement example in Note 3
- Multi-Cloud interprets opaque TLV as Physical DC Endpoint as translates to cloud-specific placement attribute such as Availability Zone
  - For this example, each distributed physical DC is in a separate Availability Zone for a OpenStack-based Cloud

...

ONAP Component	Life cycle phase	Activities
AAI and ESR	Deploy & Run time	Add/Modify/Delete recording and alerting rules
AAI and ESR	Run time	Add/Modify/Delete Edge-cloud information
Multi-Cloud	Run time	Get Edge information from A&AI whenever Edge-Cloud is added or removed. Prepare to wait for information from that Edge-cloud Receive information from edge-cloud and put it in the time series DB. Summation based on recording & alerting rules Export information to DCAE via DMAPP or VES

Intent-based Cloud Agnostic IaaS API for Cloud Infrastructure

ONAP Component	Life Cycle Phase	Enhancements
Policy	Design