The goal of the design process is to create all artifacts (models) that are required to instantiate and manage resources, services, and products on the ONAP platform.
Design progresses logically through a series of phases. Each phase:
is organized into steps that are completed in sequence
generates artifacts that are used in other phases of design
is performed by multiple Design components
The following figure show the different phases and tools involved in Onboarding, Design and Distribution process.
The “Core” Design Process includes the following steps:
A VNF/PNF/CNF Provider delivers its descriptor, model and artefacts (e.g. HEAT template, Helm Chart), which will be validated and packaged for onboarding to ONAP
In the SDC a License Model is created, the VNF/PNF/CNF package imported and a Vendor Software Product (VSP) is created
- VF Creation and Testing
A V(N)F, PNF or CR Model is created (a) import of a VSP or VFC (b) manual creation and import of artefacts created via external tools like the Controller Design Studio (CDS), responsible for the Controller Blueprint Design The created VF Model will be used in a Service Model
- Service Design
A Service Model is created as a composition of resources (e.g. V(N)Fs, PNFs,…), Policies, Workflows,… The created Service Model will be certified and handed over to the Service Distribution process
- Service Distribution
The Service Provider will distribute the Service Model to the Runtime Service Catalog
The optional/additional Design steps are:
- VNF parameter assignment templating
The objective is to automate the resolution of resources for instantiation and any config provisioning operation, such as day0, day1 or day2 configuration. The Controller Blueprint archive (CBA) is a fully model-driven, intent based package needed to design self service provisioning and configuration management automation. ONAP CDS (Controller Design Studio) is the controller that will process the Controller Blueprint archive (CBA) at run-time.
- Policy Design
These are rules, conditions, requirements, constraints, attributes, or needs that must be provided, maintained, and/or enforced. At a lower level, Policy involves machine-readable rules enabling actions to be taken based on triggers or requests. ONAP Policy framework provides some policy models that are implemented and pre-loaded when installing ONAP.
- Workflow Design
The purpose of the Workflow Designer is to enable designers to define or modify workflows to support Service/Resource change management scenarios executed by the Service Orchestrator.
- DCAE Onboard/Design
This phase includes the Onboarding of DCAE Microservices and their Policy Models, the Service Assurance Design and Distribution to Policy and CLAMP for Closed Loop Automation Management. The DCAE Onboard/Design component contains an own Design Catalog, which is not yet integrated with the SDC Design Catalog to exchange models and artefacts.
The following sections focus on the different Design steps:
The following section provide links to the projects: