blob: 805cfa89c02021f0f6b9f565d60c95db87baf96b (
plain)
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
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. Copyright (C) 2019 IBM.
Design Time Tools Guide
=======================
Below are the requirements to enable automation for a service within ONAP.
For instantiation, the goal is to be able to automatically resolve all the HEAT/Helm variables, called cloud parameters.
For post-instantiation, the goal is to configure the VNF with initial configuration.
Prerequisite
------------
* Gather the cloud parameters:
Instantiation:
~~~~~~~~~~~~~~
Have the HEAT template along with the HEAT environment file (or) Have the Helm chart along with the Values.yaml file
(CDS supports, but whether SO → Multicloud support for Helm/K8S is different story)
Post-instantiation:
~~~~~~~~~~~~~~~~~~~
Have the configuration template to apply on the VNF.
* XML for NETCONF
* JSON / XML for RESTCONF
* not supported yet - CLI
* JSON for Ansible [not supported yet]
* Identify which template parameters are static and dynamic
* Create and fill-in the a table for all the dynamic values
While doing so, identify the resources using the same process to be resolved; for instance, if two IPs has to be resolved through the same IPAM, the process the resolve the IP is the same.
Services:
---------
.. toctree::
:maxdepth: 2
../cba/index
../resourcedefinition/index
resourceassignment
|
