Page History

...

• Multi-VIM/Cloud project aims to enable ONAP to deploy and run on multiple infrastructure environments, for example, OpenStack and its different distributions (e.g. vanilla 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 decouples the evolution of ONAP platform from the evolution of underlying cloud infrastructure, and minimizes the impact on the deployed ONAP while upgrading the underlying cloud infrastructures independently.

Scope:

...

The scope of Multi-VIM/Cloud project is a plugable and extensible framework that

1. provides a Cloud Mediation Layer which includes the following functional modules
   1. Provider Registry to register infrastructure site/location/region and their attributes and capabilities in A&AI
   2. Infra Resource to manage resource request (compute, storage and memory) from SO, DCAE, or other ONAP components, so as to get VM created and VNF instantiated at the right infrastructure
   3. SDN Overlay to configure overlay network via local SDN controllers for the corresponding cloud infrastructure
   4. VNF Resource LCM to perform VM lifecycle management as requested by VNFM (APP-C or VNF-C)
   5. FCAPS to report infrastructure resource metrics (utilization, availability, health, performance) to DCAE Collectors for Close Loop Remediation
2. provides a common northbound interface (NBI) / Multi-Cloud APIs of the functional modules to be consumed by SO, SDN-C, APP-C, VF-C, DCAE etc.
3. provides a A common abstraction model
4. The provides the ability to
   1. handle differences in models
   2. generates generate or extends extend NBI based on the functional model of underlying infrastructure
   3. allows Infrastructure Controller to register with capacity info & capabilities (for supporting EPA), discover and choose one or more VIM(s) to use
   4. allows global SDN Controller to choose and work with multiple local SDN Controller backends
   5. implements implement adapters for different providers.

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.

...

Multi-VIM/Cloud project will align with the Common Controller Framework to enable reuse by different ONAP elements.

Deliverables of Release One:

...