...
- Proposed name for the project: Multi-VIM for Cloud Providers
- Proposed name for the repository:
- MultiVIM
...
- 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 while the underlying cloud infrastructure is upgraded.
- 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
- Minimal
- Demo use case within a single site, supported by any single VIM provider.
- For VoLTE vVoLTE or vCPE, enable single VIM provider across multi-site
- Stretch goal
- For VoLTE vVoLTE or vCPE, enable mix of different VIM providers across multi-site
- Minimal
...
- How does this align with external standards/specifications?
- Support existed functions
- Information/data models by ONAP modeling project
- Compliant with ETSI NFV architecture framework
- Are there dependencies with other open source projects?
Resources:
- Primary Contact Person: Bin Yang, Wind River; Xinhui Li, VMware; Bin Yang, Wind River
- Initial Committers:
- Andrew Philip, Microsoft
- Bin Yang, Wind River
- Xinhui Li, VMware
- Anbing Zhang, China Mobile
- Contributors
- Isaku Yanahata, Intel
- Matti Hiltunen, AT&T
- Ethan Lynn, VMware
...
- link to seed code (if applicable)
- seed code for MultiVIM framework: https://gerrit.open-o.org/r/multivimdriver-broker
- seed code for OpenStack: https://gerrit.open-o.org/r/multivimdriver-openstack
- seed code for VMware VIO: https://gerrit.open-o.org/r/multivimdriver-vmware-vio
- Vendor Neutral
- if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
- Meets Board policy (including IPR)
...