...
- 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.
- CDP-PAL ( Continuous Deployment Platform - Provider Abstraction Layer) is a thin, opaque API that surrounds the underlying cloud implementation, abstracting the implementation, providing a consistent and standard interface to access cloud infrastructure providers. CDP-PAL helps automate the creation, migration, and management of cloud-deployed applications and their needed hardware/software environment. PAL will be used in the common cloud architecture to allow for the deployment, migration, and scaling up/down of cloud deployed applications. CDP-PAL supports AWS, Azure, Baremetal, VMware and Openstack.
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.
...
The proposed Multi VIM/Cloud layer will be added into the infrastructure controller. It has dependencies with SO, DCAE, A&AI, APP-C/VNF-C, Modeling, and will act as the single access point to be called by these components for accessing the cloud and virtual infrastructure. Furthermore, it will align with SDN-C component for both intra DC connectivity as well as inter-DC connectivity. Thus it is also the single access point for SDN-C to work with other local SDN Controllers. Applications/VNFs can be homed to the different cloud providers through the standard ONAP methods. For automated homing (SNIRO), different cloud providers can register attributes that differentiate their cloud platforms (e.g., reliability, latency, other capabilities) in A&AI and application placement policies/constraints can request for these specific properties (e.g., reliability > 0.999).
CDP-PAL is a multi-tenant online application, with access provided by a web interface. The user signs in to CDP-PAL to manage their "tenant" (similar to an account or a business organization within CDP-PAL which may have any number of users associated with it). A user can then create, edit, provision, etc a blueprint model, manage the created stacks (the instances that are created from the model), and administer the tenant and all of its resources.
What other ONAP projects does this project depend on?
...