Project Name:
- Proposed name for the project: Multi VIM/Cloud for Infrastructure Providers
- Proposed name for the repository: multicloud
Project description:
- ONAP needs underlying virtualized 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, and related network backends. This project aims to enable ONAP to support multiple infrastructure environments, for example, OpenStack and its different distributions (e.g., openstack.org, Wind River, etc...), public and private clouds (e.g., VMware, Azure), and micro services containers, etc.
- 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 and minimize the impact to the deployed ONAP while upgrading the underlying cloud infrastructures.
Scope:
- A plugable and extensible framework that
- provides a Mediation Layer which includes
- A common northbound interface (NBI) / Multi-Cloud APIs
- A common abstraction model
- The ability to handle differences in models
- generates or extends NBI based on the functional model of underlying infrastructure
- allows Infrastructure Controller to register with capacity info & capabilities (for supporting EPA), discover and choose one or more VIM(s) to use
- allows global SDN Controller to choose and work with multiple local SDN Controller backends
- implements adapters for different providers.
- provides a Mediation Layer which includes
- Across the project the implementation of any differentiated functionalities will be done in a way where ONAP users can decide if to use or not to use those functionalities.
- 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)
- Should align with the Common Controller Framework to enable reuse by different ONAP elements.
Deliverables of Release One:
Note: this section is for brainstorming and informational purpose, and subject to change during release planning stage
...
- Minimal
- Implementation of the adapters for VMware, OpenStack (Wind River), and Microsoft Azure.
- Demo use case within a single site, supported by any single cloud provider.
- For vVoLTE or vCPE, enable single cloud provider across multi-site
- Stretch goal
- For vVoLTE or vCPE, enable mix of different cloud providers across multi-site
Architecture Alignment:
- How does this project fit into the rest of the ONAP Architecture?
...
- Are there dependencies with other open source projects?
- OpenStack
Resources:
- Primary Contact Person
- Danny Lin, lind@vmware.com, VMware
- Names, emails, and company affiliations of the committers
Alon Strikovsky, alon.Strikovsky@amdocs.com, Amdocs
- Anbing Zhang, zhanganbing@chinamobile.com, China Mobile
- Andrew Philip, aphilip@microsoft.com, Microsoft
- Bin Hu, bh526r@att.com, AT&T
- Bin Yang, bin.yang@windriver.com, Wind River
- Kanagaraj Manickam (mkr1481), kanagaraj.manickam@huawei.com, Huawei
- Xinhui Li, lxinhui@vmware.com, VMware
- Names and affiliations of any other contributors
- Claude Noshpitz claude.noshpitz@att.com, AT&T
- Ethan Lynn, ethanlynnl@vmware.com, VMware
- Gil Hellmann, gil.hellmann@windriver.com, Wind River
- Isaku Yanahata, isaku.yamahata@intel.com, Intel
- John Murray, jm2932@att.com, AT&T
- Matti Hiltunen, hiltunen@att.com, AT&T
- Project Roles (include RACI chart, if applicable)
Other Information:
- link to seed code (if applicable)
...
Use the above information to create a key project facts section on your project page
Key Project Facts
Project Name:
- JIRA project name: multicloud
- JIRA project prefix: multicloud
...