...
- Proposed name for the project: Multi VIM/Cloud for Infrastructure Providers
- Proposed name for the repository: multicloud
Project description:
Motivation
- ONAP needs underlying virtualized infrastructure to deploy, run, and manage network services and VNFs.
- The service provider looks providers always look for flexibility in its choice of onand choice in selecting virtual and cloud infrastructure implementations, for example, on-premise private cloud, public cloud, or hybrid cloud implementations, and related network backends.
- ONAP needs to maintain platform backward compatibility with every new release.
Goal
- Multi-VIM/Cloud project This project aims to enable ONAP to support deploy and run on multiple infrastructure environments, for example, OpenStack and its different distributions (e.g. , openstack.orgvanilla OpenStack, Wind River, etc...), public and private clouds (e.g. , VMware, Azure), and micro services containers, etc.
- Multi-VIM/Cloud project will provide a Cloud Mediation Layer supporting multiple infrastructures and network backends so as to effectively prevents vendor lock-in.
- Multi-VIM/Cloud project 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 minimizes the impact to on the deployed ONAP while upgrading the underlying cloud infrastructures independently.
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.
...
*Link to TSC approval:
Link to approval of additional submitters:
in selecting virtual and cloud infrastructure implementations