Goal
ONAP has to be able to create and manage the life cycle of VNFs and services with operations automation in the context of multiple clouds, for example:
- Clouds with OpenStack etc. as service managers
- Clouds like Microsoft Azure, Amazon Web Services, Google Compute Platform etc.
- Public clouds where information about the underlying infrastructure and operations on them are limited.
- ONAP operator-owned clouds where much more information and operations on the cloud infrastructure are potentially available.
Ideally, the data model is cloud-agnostic. The impact to ONAP of introducing a new cloud type (or upgraded version of a cloud type) is to be minimized. To meet this objective, the architecture calls for all the specific-to-a-particular cloud knowledge to be localized, and for the rest of ONAP to use a cloud-agnostic model. The various cloud-specific template objects, attributes and APIs that are relevant to ONAP should be readily mapped into this data model.
The data model should be structured to help and not hinder, to the extent possible for a data model, the architectural desired separation of concerns between ONAP and the clouds.
Challenge
Scope