...
- Proposed name for the project: Multi-vimVIM for Cloud Providers
- Proposed name for the repository:
- Multi-vim-framework
- Multi-vim-vmware-plugin
- Multi-vim-azure-plugin
- Multi-vim-openstack-plugin
Project description:
- multivim
Project description:
- ONAP needs underline virtual and cloud infrastructure to deploy, run, and manage network services and VNFs. The service provider look 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 environment including OpenStack (across different distributions), VMware, Azure, and micro services containers.
- provides multiple cloud provider support multiple clouds, In ONAP, SO,
- APPC/VNF-C, DCAE, need to access to virtual and cloud infrastructure. SDC also requires knowledge of the infrastructure to onboard VNF images and VNF template. And finally, SDN-C could benefit from the capability of a local SDN to create VNF connectivity within the cloud. An abstraction layer with ONAP is necessary to consolidate all these infrastructure capabilities.
- Service providers also look for flexibility and choice in terms of multiple clouds to meet their business requirements. ONAP needs to support different infrastructure environment including OpenStack (different versioned), VMware, Azure, micro-services, and containers.
Scope:
1: A framework Add capability in infrastructure controller to allow for registration, resource, capacity, and homingdiscovery (or homing), and selection of cloud and virtual infrastructure providers
2: A plugin plugable framework that implements adapters for different cloud providers. In R1, we expect OpenStack?expect VMware VIO, OpenStack (Wind River?), VMware VIO, and Microsoft Azure.
3: DCAE close loop remediation
...
—Monitoring API collection for multi-cloud resource metrics (utilization, availability, health, performance)
...
, potential extending DCAE collectors
4: Deliverables:SDC VNF template customization and/or optimization to establish close match to the capabilities of underline cloud and virtual infrastructure provider(s)
5: In R1, we target to support
- Minimal
- Demo vFirewall in an environment with any single cloud provider, within a single site
- For VoLTE and or vCPE (or whatever is the minimal release requirement), enable single cloud provider across multi-site
- Stretch goal
- Enable multiple cloud provider For VoLTE or vCPE, enable mix of different cloud providers across multi-site
5: SDN-C
...
* SDN Controller can establish cross DC connectivity, including support public cloud SDN federation
Architecture Alignment:
- How does this project fit into the rest of the ONAP Architecture?
The proposed infrastructure mediation layer will work multi-vim layer will be added into the infrastructure controller. It has dependencies with SO, DCAE, A&AI, and will act as the single access point to be called by different components. Where, authentication federation should be provided to different adaptors/plugins, together with infrastructure management and operation API (e.g., LCM), and expose monitoring/alerts/events for DCAE or any consumerthese components for accessing the cloud and virtual infrastructure. Furthermore, we expect to align with SDN-C component for both intra DC connectivity as well as inter-DC connectivity
- How does this align with external standards/specifications?
- Support existed functions
- Information/data models
- Compliant with ETSI NFV arhitecture framework
- Are there dependencies with other open source projects?
Resources:
- Primary Contact Person: Bin Yang, Xinhui Li,
- Initial Committers:
- Andrew Philip, Microsoft
- Bin Yang, Wind River
- Xinhui Li, VMware
- Anbing Zhang, CMCCChina Mobile
Contributors
- Isaku Yanahata, Intel
- Matti Hiltunen, AT&T
- Ethan, VMware
...
- Andrew Philip, Microsoft
- Bin Yang, Wind River
- Xinhui Li, VMware
- Anbing Zhang, CMCC
...