1 .. This work is licensed under a
2 .. Creative Commons Attribution 4.0 International License.
3 .. http://creativecommons.org/licenses/by/4.0
4 .. Copyright 2019 Amdocs, Bell Canada
11 .. figure:: oomLogoV2-medium.png
14 Once a kubernetes environment is available (follow the instructions in
15 :ref:`cloud-setup-guide-label` if you don't have a cloud environment
16 available), follow the following instructions to deploy ONAP.
18 **Step 1.** Clone the OOM repository from ONAP gerrit::
20 > git clone -b 4.0.0-ONAP http://gerrit.onap.org/r/oom --recurse-submodules
23 **Step 2.** Install Helm Plugins required to deploy ONAP::
25 > sudo cp -R ~/oom/kubernetes/helm/plugins/ ~/.helm
28 **Step 3.** Customize the helm charts like oom/kubernetes/onap/values.yaml or an override
29 file like onap-all.yaml, onap-vfw.yaml or openstack.yaml file to suit your deployment with items like the
30 OpenStack tenant information.
33 Standard and example override files (e.g. onap-all.yaml, openstack.yaml) can be found in
34 the oom/kubernetes/onap/resources/overrides/ directory.
37 a. You may want to selectively enable or disable ONAP components by changing
38 the `enabled: true/false` flags.
41 b. Encyrpt the OpenStack password using the shell tool for robot and put it in
42 the robot helm charts or robot section of openstack.yaml
45 c. Encrypt the OpenStack password using the java based script for SO helm charts
46 or SO section of openstack.yaml.
49 d. Update the OpenStack parameters that will be used by robot, SO and APPC helm
50 charts or use an override file to replace them.
55 a. Enabling/Disabling Components:
56 Here is an example of the nominal entries that need to be provided.
57 We have different values file available for different contexts.
59 .. literalinclude:: onap-values.yaml
63 b. Generating ROBOT Encrypted Password:
64 The ROBOT encrypted Password uses the same encryption.key as SO but an
65 openssl algorithm that works with the python based Robot Framework.
68 To generate ROBOT openStackEncryptedPasswordHere :
70 ``cd so/resources/config/mso/``
72 ``/oom/kubernetes/so/resources/config/mso# echo -n "<openstack tenant password>" | openssl aes-128-ecb -e -K `cat encryption.key` -nosalt | xxd -c 256 -p``
74 c. Generating SO Encrypted Password:
75 The SO Encrypted Password uses a java based encryption utility since the
76 Java encryption library is not easy to integrate with openssl/python that
80 To generate SO openStackEncryptedPasswordHere and openStackSoEncryptedPassword:
82 SO_ENCRYPTION_KEY=`cat ~/oom/kubernetes/so/resources/config/mso/encryption.key`
84 OS_PASSWORD=XXXX_OS_CLEARTESTPASSWORD_XXXX
86 git clone http://gerrit.onap.org/r/integration
88 cd integration/deployment/heat/onap-rke/scripts
93 [ if javac is not installed 'apt-get update ; apt-get install default-jdk' ]
95 java Crypto "$OS_PASSWORD" "$SO_ENCRYPTION_KEY"
98 d. Update the OpenStack parameters:
100 There are assumptions in the demonstration VNF heat templates about the networking
101 available in the environment. To get the most value out of these templates and the
102 automation that can help confirm the setup is correct, please observe the following
105 openStackPublicNetId:
107 This network should allow heat templates to add interfaces.
108 This need not be an external network, floating IPs can be assigned to the ports on
109 the VMs that are created by the heat template but its important that neutron allow
110 ports to be created on them.
112 openStackPrivateNetCidr: "10.0.0.0/16"
114 This ip address block is used to assign OA&M addresses on VNFs to allow ONAP connectivity.
115 The demonstration heat templates assume that 10.0 prefix can be used by the VNFs and the
116 demonstration ip addressing plan embodied in the preload template prevent conflicts when
117 instantiating the various VNFs. If you need to change this, you will need to modify the preload
118 data in the robot helm chart like integration_preload_parametes.py and the demo/heat/preload_data
119 in the robot container. The size of the CIDR should be sufficient for ONAP and the VMs you expect
122 openStackOamNetworkCidrPrefix: "10.0"
124 This ip prefix mush match the openStackPrivateNetCidr and is a helper variable to some of the
125 robot scripts for demonstration. A production deployment need not worry about this
126 setting but for the demonstration VNFs the ip asssignment strategy assumes 10.0 ip prefix.
129 Example Keystone v2.0
130 .. literalinclude:: example-integration-override.yaml
133 Example Keystone v3 (required for Rocky and later releases)
134 .. literalinclude:: example-integration-override-v3.yaml
139 **Step 4.** To setup a local Helm server to server up the ONAP charts::
143 Note the port number that is listed and use it in the Helm repo add as
146 > helm repo add local http://127.0.0.1:8879
148 **Step 5.** Verify your Helm repository setup with::
152 local http://127.0.0.1:8879
154 **Step 6.** Build a local Helm repository (from the kubernetes directory)::
156 > make all; make onap
158 **Step 7.** Display the onap charts that available to be deployed::
160 > helm search onap -l
162 .. literalinclude:: helm-search.txt
165 The setup of the Helm repository is a one time activity. If you make changes to your deployment charts or values be sure to use `make` to update your local Helm repository.
167 **Step 8.** Once the repo is setup, installation of ONAP can be done with a
171 The --timeout 900 is currently required in Dublin to address long running initialization tasks
172 for DMaaP and SO. Without this timeout value both applications may fail to deploy.
174 a. To deploy all ONAP applications use this command::
177 > helm deploy dev local/onap --namespace onap -f onap/resources/overrides/onap-all.yaml -f onap/resources/overrides/openstack.yaml --timeout 900
179 b. If you are using a custom override (e.g. integration-override.yaml) use this command::
181 > helm deploy dev local/onap -f /root/integration-override.yaml --namespace onap --timeout 900
184 c. If you have a slower cloud environment you may want to use the public-cloud.yaml
185 which has longer delay intervals on database updates.::
187 > helm deploy dev local/onap -f /root/oom/kubernetes/onap/resources/environments/public-cloud.yaml -f /root/integration-override.yaml --namespace onap --timeout 900
190 **Step 9.** Commands to interact with the OOM installation
192 Use the following to monitor your deployment and determine when ONAP is
195 > kubectl get pods -n onap -o=wide
197 Undeploying onap can be done using the following command::
199 > helm undeploy dev --purge
202 More examples of using the deploy and undeploy plugins can be found here: https://wiki.onap.org/display/DW/OOM+Helm+%28un%29Deploy+plugins