...
- ONAP needs underline virtual and cloud infrastructure to deploy, run, and manage network services and VNFs. The service provider looks for flexibility in its choice of on-premise private cloud, public cloud, or hybrid cloud implementations. This project aims to enable ONAP to support multiple infrastructure environments including OpenStack (across different distributions), VMware, Azure, and micro services containers.
- ONAP needs to maintain platform backward compatibility with every new release. This project decouples the evolution of ONAP platform from the evolution of underlying cloud infrastructure to enable the deployed ONAP intact when upgrading the underlying cloud infrastructures.
- Support Use cases for R1: vCPE, vVoLTE, vFW/vDNS
Scope:
- Add capability in infrastructure controller to allow for registration, discovery (or homing), and invocation of a VIM provider.
- A plugable framework that implements adapters for different providers. In R1, we expect VMware VIO, OpenStack (Wind River), and Microsoft Azure.
- Close loop remediation — Monitoring API collection for multi-cloud resource metrics (utilization, availability, health, performance), potential integration with DCAE collectors
- SDC VNF template customization and/or optimization to establish close match to the underline capabilities of the infrastructure provider(s)
- In R1, we target to support
...
Resources:
- Primary Contact Person: Bin Yang, Wind River; Xinhui Li, VMware; Danny Lin, VMware
- Initial Committers:
- Andrew Philip, Microsoft
- Bin Yang, Wind River
- Xinhui Li, VMware
- Anbing Zhang, China Mobile
- Kanagaraj Manickam (mkr1481), Huawei
- Contributors
- Isaku Yanahata, Intel
- Matti Hiltunen, AT&T
- Ethan Lynn, VMware
...