blob: 20a03efbcdcb35f984a46df348efc21426579bbe [file] [log] [blame]
Ezhilarasi4b46bb12019-04-23 20:43:47 +05301.. This work is licensed under a Creative Commons Attribution 4.0 International License.
2.. http://creativecommons.org/licenses/by/4.0
3.. Copyright (C) 2019 IBM.
4
5Design Time User Guide
6======================
7
8Bellow are the requirements to enable automation for a service within ONAP.
9
10For instantiation, the goal is to be able to automatically resolve all the HEAT/Helm variables, called cloud parameters.
11
12For post-instantiation, the goal is to configure the VNF with initial configuration.
13
14Prerequisite
15============
16
17* Gather the cloud parameters:
18
19instantiation:
20
21Have the HEAT template along with the HEAT environment file.
22
23or
24
25Have the Helm chart along with the Values.yaml file
26
27(CDS supports, but whether SO Multicloud support for Helm/K8S is different story)
28
29
30Post-instantiation:
31
32Have the configuration template to apply on the VNF.
33
34* XML for NETCONF
35* JSON / XML for RESTCONF
36* not supported yet - CLI
37* JSON for Ansible [not supported yet]
38
39*Identify which template parameters are static and dynamic
40*Create and fill-in the a table for all the dynamic values
41
42While 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.
43
44
45Services:
Ezhilarasi3b4a9f62019-08-16 15:26:54 +053046=========
Ezhilarasi4b46bb12019-04-23 20:43:47 +053047
48.. toctree::
49 :maxdepth: 1
50
51 CBA/index
52 datadictionary/index
53 resourceassignment
54 component
55 template
56 resquirement