1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
|
.. This work is licensed under a Creative Commons Attribution 4.0
.. International License. http://creativecommons.org/licenses/by/4.0
.. Copyright 2017 AT&T Intellectual Property. All rights reserved.
.. _doc_guide_user_des:
Design Service
==============
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.
|image1|
**The "Core" Design Process includes the following steps:**
**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/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:
.. toctree::
:maxdepth: 1
:titlesonly:
Pre-Onboarding <./pre-onboarding/index.rst>
Resource-Onboarding <./resource-onboarding/index.rst>
VF Creation and Testing <./vfcreation/index.rst>
Service Design <./service-design/index.rst>
Service Distribution <./service-distribution/index.rst>
VNF Parameter Resolution Design <./parameter_resolution/index.rst>
Control Loop Design <./control-loop/index.rst>
Instructions for Control Loop Design <./control-loop-design-steps/cl_design_instructions.rst>
The following section provide links to the projects:
- :ref:`Policy Design<onap-policy-parent:design-label>`
- :ref:`Workflow Design<onap-sdc:workflow>`
- :ref:`DCAE Onboard/Design<onap-dcaegen2:master_index>`
- :ref:`Control Loop Automation Management<onap-policy-parent:clamp-label>`
.. |image1| image:: media/Design-Overview.png
|
