**The "Core" Design Process includes the following steps:**
-* Pre-Onboarding
- A VNF/PNF Provider delivers VNF descriptor, model and
- artefacts (e.g. HEAT template), which will be validated
+**Pre-Onboarding**
+ 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
-* (Resource)-Onboarding
- In the SDC a License Model is created, the VNF/PNF package imported
+**(Resource)-Onboarding**
+ 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
+**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
The created VF will pass a testing workflow to be used
in a Service Model
-* Service Design
- A Service Model is created as a composition of resources
+**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 pass a testing workflow and
- handed over to a Governance Approval and Distribution process
+ The created Service Model will ber certified and handed over to
+ the Service Distribution process
-* Governance Approval and Distribution
- The Service Provider will have a specific set of policies and
- procedures for approving Services and deploying them in the
+**Service Distribution**
+ The Service Provider will distribute the Service Model to the
Runtime Service Catalog
**The optional/additional Design steps are:**
-* Controller Blueprint Design
- The Controller Blueprint is the overall service design, fully model-driven,
- intent based package needed for self service provisioning and configuration
- management automation. The framework to automate the resolution of resources
- for instantiation and any config provisioning operation,
- such as day0, day1 or day2 configuration.
- It provides a tool called Controller Design Studio
-
-* Policy Design
- The Policy Creation component deals with policies.
+**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 the overall service design,
+ 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.
+ 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.
-* APPC Controller Design
+**VNF LifeCycle Command templating**
APPC Controller Design Tool (CDT) is used for self-service onboarding of
VNF’s. VNF owners can create templates and other artifacts for APPC
Configure command (used to apply a post-instantiation configuration)
as well as other life cycle commands.
-* Workflow Design
+**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.
-* Control Loop Design
+**Control Loop Design**
This phase includes the Design of a closed loop template and associate it
to a Service. The template represents the theoretical flow of the CL.
It generates a deployment artifact that can be ingested by the DCAE in
The design is done in the SDC DCAE-DS (Design Studio).
The DCAE Design Studio enables to define and configure
the monitoring flows of DCAE.
- The configuration and deployment of a Control Loop will be done with
+ The configuration and deployment of a Control Loop will be done with
Control Loop Automation Management (CLAMP) tool.
The follwing sections will focus on the different Design steps:
Service Design <./service-design/index.rst>
- Governance Approval and Service Distribution <./service-distribution/index.rst>
+ Service Distribution <./service-distribution/index.rst>
- Controller Blueprint Design <../../../submodules/ccsdk/cds.git/docs/index.rst>
+ VNF parameter resolution Design <./parameter_resolution/index.rst>
Policy Design <../../../submodules/policy/parent.git/docs/design/design.rst>
- APPC Controller Design <../../../submodules/appc.git/docs/APPC CDT Guide/APPC CDT Guide.rst>
+ VNF LifeCycle Command templating <../../../submodules/appc.git/docs/APPC CDT Guide/APPC CDT Guide.rst>
Workflow Design <../../../submodules/sdc.git/docs/workflow.rst>
Code Review / doc.git / blobdiff