Gitiles
Code Review Sign In
gerrit.nordix.org / onap / cps / 47d6b392e984181418b920d0ea8fe658f6375acc / . / docs / deployment.rst
blob: 06e1ddcc08fcf1e5e7a258e32cf6859aead28daf [file] [log] [blame]
shivasubedi44beaa32021-09-13 15:16:30 +0100[diff] [blame]1.. This work is licensed under a Creative Commons Attribution 4.0 International License.
2.. http://creativecommons.org/licenses/by/4.0
3.. Copyright (C) 2021 Nordix Foundation
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]4.. Modifications Copyright (C) 2021 Bell Canada.
shivasubedi44beaa32021-09-13 15:16:30 +0100[diff] [blame]5
6.. DO NOT CHANGE THIS LABEL FOR RELEASE NOTES - EVEN THOUGH IT GIVES A WARNING
7.. _deployment:
8
shivasubedi44beaa32021-09-13 15:16:30 +0100[diff] [blame]9CPS Deployment
Bruno Sakotoa1129b62022-03-15 08:09:07 -0400[diff] [blame]10##############
shivasubedi44beaa32021-09-13 15:16:30 +0100[diff] [blame]11
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]12.. contents::
13 :depth: 2
shivasubedi44beaa32021-09-13 15:16:30 +0100[diff] [blame]14
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]15CPS OOM Charts
Bruno Sakotoa1129b62022-03-15 08:09:07 -0400[diff] [blame]16==============
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]17The CPS kubernetes chart is located in the `OOM repository <https://github.com/onap/oom/tree/master/kubernetes/cps>`_.
18This chart includes different cps components referred as <cps-component-name> further in the document are listed below:
19
20.. container:: ulist
21
22 - `cps-core <https://github.com/onap/oom/tree/master/kubernetes/cps/components/cps-core>`_
23 - `cps-temporal <https://github.com/onap/oom/tree/master/kubernetes/cps/components/cps-temporal>`_
24 - `ncmp-dmi-plugin <https://github.com/onap/oom/tree/master/kubernetes/cps/components/ncmp-dmi-plugin>`_
25
26Please refer to the `OOM documentation <https://docs.onap.org/projects/onap-oom/en/latest/oom_user_guide.html>`_ on how to install and deploy ONAP.
27
28Installing or Upgrading CPS Components
Bruno Sakotoa1129b62022-03-15 08:09:07 -0400[diff] [blame]29======================================
30
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]31The assumption is you have cloned the charts from the OOM repository into a local directory.
32
33**Step 1** Go to the cps charts and edit properties in values.yaml files to make any changes to particular cps component if required.
34
35.. code-block:: bash
36
37 cd oom/kubernetes/cps/components/<cps-component-name>
38
39**Step 2** Build the charts
40
41.. code-block:: bash
42
43 cd oom/kubernetes
44 make SKIP_LINT=TRUE cps
45
46.. note::
47 SKIP_LINT is only to reduce the "make" time
48
49**Step 3** Undeploying already deployed cps components
50
51After undeploying cps components, keep monitoring the cps pods until they go away.
52
53.. code-block:: bash
54
55 helm del --purge <my-helm-release>-<cps-component-name>
56 kubectl get pods -n <namespace> | grep <cps-component-name>
57
58**Step 4** Make sure there is no orphan database persistent volume or claim.
59
60First, find if there is an orphan database PV or PVC with the following commands:
61
62.. note::
63 This step does not apply to ncmp-dmi-plugin.
64
65.. code-block:: bash
66
67 kubectl get pvc -n <namespace> | grep <cps-component-name>
68 kubectl get pv -n <namespace> | grep <cps-component-name>
69
70If there are any orphan resources, delete them with
71
72.. code-block:: bash
73
74 kubectl delete pvc <orphan-cps-core-pvc-name>
75 kubectl delete pv <orphan-cps-core-pv-name>
76
77**Step 5** Delete NFS persisted data for CPS components
78
79Connect to the machine where the file system is persisted and then execute the below command
80
81.. code-block:: bash
82
83 rm -fr /dockerdata-nfs/<my-helm-release>/<cps-component-name>
84
85**Step 6** Re-Deploy cps pods
86
87After deploying cps, keep monitoring the cps pods until they come up.
88
89.. code-block:: bash
90
91 helm deploy <my-helm-release> local/cps --namespace <namespace>
92 kubectl get pods -n <namespace> | grep <cps-component-name>
93
94Restarting a faulty component
Bruno Sakotoa1129b62022-03-15 08:09:07 -0400[diff] [blame]95=============================
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]96Each cps component can be restarted independently by issuing the following command:
97
98.. code-block:: bash
99
100 kubectl delete pod <cps-component-pod-name> -n <namespace>
101
ToineSiebelink39207852021-10-21 12:11:25 +0100[diff] [blame]102.. Below Label is used by documentation for other CPS components to link here, do not remove even if it gives a warning
103.. _cps_common_credentials_retrieval:
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]104
105Credentials Retrieval
Bruno Sakotoa1129b62022-03-15 08:09:07 -0400[diff] [blame]106=====================
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]107
108Application and database credentials are kept in Kubernetes secrets. They are defined as external secrets in the
109values.yaml file to be used across different components as :
110
111.. container:: ulist
112
113 - `cps-core <https://github.com/onap/oom/blob/master/kubernetes/cps/components/cps-core/values.yaml#L18>`_
114 - `cps-temporal <https://github.com/onap/oom/blob/master/kubernetes/cps/components/cps-temporal/values.yaml#L28>`_
115 - `ncmp-dmi-plugin <https://github.com/onap/oom/blob/master/kubernetes/cps/components/ncmp-dmi-plugin/values.yaml#L22>`_
116
117Below are the list of secrets for different cps components.
118
119+--------------------------+---------------------------------+---------------------------------------------------+
120| Component | Secret type | Secret Name |
121+==========================+=================================+===================================================+
122| cps-core | Database authentication | <my-helm-release>-cps-core-pg-user-creds |
123+--------------------------+---------------------------------+---------------------------------------------------+
124| cps-core | Rest API Authentication | <my-helm-release>-cps-core-app-user-creds |
125+--------------------------+---------------------------------+---------------------------------------------------+
126| cps-temporal | Rest API Authentication | <my-helm-release>-cps-temporal-app-user-creds |
127+--------------------------+---------------------------------+---------------------------------------------------+
128| cps-temporal | Database authentication | <my-helm-release>-cps-temporal-pg-user-creds |
129+--------------------------+---------------------------------+---------------------------------------------------+
130| ncmp-dmi-plugin | Rest API Authentication | <my-helm-release>-cps-dmi-plugin-user-creds |
131+--------------------------+---------------------------------+---------------------------------------------------+
132| ncmp-dmi-plugin | SDNC authentication | <my-helm-release>-ncmp-dmi-plugin-sdnc-creds |
133+--------------------------+---------------------------------+---------------------------------------------------+
134
135The credential values from these secrets are configured in running container as environment variables. Eg:
136`cps core deployment.yaml <https://github.com/onap/oom/blob/master/kubernetes/cps/components/cps-core/templates/deployment.yaml#L46>`_
137
138If no specific passwords are provided to the chart as override values for deployment, then passwords are automatically
139generated when deploying the Helm release. Below command can be used to retrieve application property credentials
140
141.. code::
142
143 kubectl get secret <my-helm-release>-<secret-name> -n <namespace> -o json | jq '.data | map_values(@base64d)'
144
145.. note::
146 base64d works only with jq version 1.6 or above.
147
148CPS Core Pods
149=============
150To get a listing of the cps-core Pods, run the following command:
151
152.. code-block:: bash
153
154 kubectl get pods -n <namespace> | grep cps-core
155
156 dev-cps-core-ccd4cc956-r98pv 1/1 Running 0 24h
157 dev-cps-core-postgres-primary-f7766d46c-s9d5b 1/1 Running 0 24h
158 dev-cps-core-postgres-replica-84659d68f9-6qnt4 1/1 Running 0 24h
159
160
161Additional Cps-Core Customizations
162==================================
163
164The following table lists some properties that can be specified as Helm chart
Renu Kumarifb4caa62022-03-21 09:18:41 -0400[diff] [blame]165values to configure the application to be deployed. This list is not exhaustive.
166
167Any spring supported property can be configured by providing in ``config.additional.<spring-supported-property-name>: value`` Example: config.additional.spring.datasource.hikari.maximumPoolSize: 30
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]168
169+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
170| Property | Description | Default Value |
171+=======================================+=========================================================================================================+===============================+
172| config.appUserName | User name used by cps-core service to configure the authentication for REST API it exposes. | ``cpsuser`` |
173| | | |
174| | This is the user name to be used by cps-core REST clients to authenticate themselves. | |
175+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
176| config.appUserPassword | Password used by cps-core service to configure the authentication for REST API it exposes. | Not defined |
177| | | |
178| | This is the password to be used by CPS Temporal REST clients to authenticate themselves. | |
179| | | |
180| | If not defined, the password is generated when deploying the application. | |
181| | | |
lukegleesonf027cfb2021-11-08 15:53:12 +0000[diff] [blame]182| | See also :ref:`cps_common_credentials_retrieval`. | |
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]183+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
184| config.dmiPluginUserName | User name used by cps-core to authenticate themselves for using ncmp-dmi-plugin service. | ``dmiuser`` |
185+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
186| config.dmiPluginUserPassword | Internal password used by cps-core to connect to ncmp-dmi-plugin service. | Not defined |
187| | | |
188| | If not defined, the password is generated when deploying the application. | |
189| | | |
lukegleesonf027cfb2021-11-08 15:53:12 +0000[diff] [blame]190| | See also :ref:`cps_common_credentials_retrieval`. | |
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]191+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
192| postgres.config.pgUserName | Internal user name used by cps-core to connect to its own database. | ``cps`` |
193+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
194| postgres.config.pgUserPassword | Internal password used by cps-core to connect to its own database. | Not defined |
195| | | |
196| | If not defined, the password is generated when deploying the application. | |
197| | | |
lukegleesonf027cfb2021-11-08 15:53:12 +0000[diff] [blame]198| | See also :ref:`cps_common_credentials_retrieval`. | |
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]199+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
200| postgres.config.pgDatabase | Database name used by cps-core | ``cpsdb`` |
201| | | |
202+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
203| logging.level | Logging level set in cps-core | info |
204| | | |
205+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
efiacorb8691812022-03-15 11:26:46 +0000[diff] [blame]206| config.useStrimziKafka | If targeting a custom kafka cluster, ie useStrimziKakfa: false, the config.eventPublisher.spring.kafka | true |
207| | values must be set. | |
208+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
209| config.eventPublisher. | Kafka hostname and port | ``<kafka-bootstrap>:9092`` |
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]210| spring.kafka.bootstrap-servers | | |
211+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
212| config.eventPublisher. | Kafka consumer client id | ``cps-core`` |
213| spring.kafka.consumer.client-id | | |
214+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
efiacorb8691812022-03-15 11:26:46 +0000[diff] [blame]215| config.eventPublisher. | Kafka security protocol. | ``SASL_PLAINTEXT`` |
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]216| spring.kafka.security.protocol | Some possible values are: | |
217| | | |
218| | * ``PLAINTEXT`` | |
219| | * ``SASL_PLAINTEXT``, for authentication | |
220| | * ``SASL_SSL``, for authentication and encryption | |
221+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
efiacorb8691812022-03-15 11:26:46 +0000[diff] [blame]222| config.eventPublisher. | Kafka security SASL mechanism. Required for SASL_PLAINTEXT and SASL_SSL protocols. | Not defined |
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]223| spring.kafka.properties. | Some possible values are: | |
224| sasl.mechanism | | |
225| | * ``PLAIN``, for PLAINTEXT | |
226| | * ``SCRAM-SHA-512``, for SSL | |
227+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
efiacorb8691812022-03-15 11:26:46 +0000[diff] [blame]228| config.eventPublisher. | Kafka security SASL JAAS configuration. Required for SASL_PLAINTEXT and SASL_SSL protocols. | Not defined |
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]229| spring.kafka.properties. | Some possible values are: | |
230| sasl.jaas.config | | |
231| | * ``org.apache.kafka.common.security.plain.PlainLoginModule required username="..." password="...";``, | |
232| | for PLAINTEXT | |
233| | * ``org.apache.kafka.common.security.scram.ScramLoginModule required username="..." password="...";``, | |
234| | for SSL | |
235+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
efiacorb8691812022-03-15 11:26:46 +0000[diff] [blame]236| config.eventPublisher. | Kafka security SASL SSL store type. Required for SASL_SSL protocol. | Not defined |
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]237| spring.kafka.ssl.trust-store-type | Some possible values are: | |
238| | | |
239| | * ``JKS`` | |
240+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
efiacorb8691812022-03-15 11:26:46 +0000[diff] [blame]241| config.eventPublisher. | Kafka security SASL SSL store file location. Required for SASL_SSL protocol. | Not defined |
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]242| spring.kafka.ssl.trust-store-location | | |
243+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
efiacorb8691812022-03-15 11:26:46 +0000[diff] [blame]244| config.eventPublisher. | Kafka security SASL SSL store password. Required for SASL_SSL protocol. | Not defined |
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]245| spring.kafka.ssl.trust-store-password | | |
246+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
efiacorb8691812022-03-15 11:26:46 +0000[diff] [blame]247| config.eventPublisher. | Kafka security SASL SSL broker hostname identification verification. Required for SASL_SSL protocol. | Not defined |
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]248| spring.kafka.properties. | Possible value is: | |
249| ssl.endpoint.identification.algorithm | | |
250| | * ``""``, empty string to disable | |
251+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
252| config.additional. | Kafka topic to publish to cps-temporal | ``cps.data-updated-events`` |
253| notification.data-updated.topic | | |
254+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
255| config.additional. | If notification from cps-core to cps-temporal is enabled or not. | ``true`` |
256| notification.data-updated.enabled | If this is set to false, then the config.publisher properties could be skipped. | |
257+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
258| config.additional. | Dataspaces to be enabled for publishing events to cps-temporal | ```` |
259| notification.data-updated.filters. | | |
260| enabled-dataspaces | | |
261+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
262| config.additional. | If notifications should be processed in synchronous or asynchronous manner | ``false`` |
263| notification.async.enabled | | |
264+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
265| config.additional. | Core pool size in asynchronous execution of notification. | ``2`` |
266| notification.async.executor. | | |
267| core-pool-size | | |
268+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
269| config.additional. | Max pool size in asynchronous execution of notification. | ``1`` |
270| notification.async.executor. | | |
271| max-pool-size | | |
272+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
273| config.additional. | Queue Capacity in asynchronous execution of notification. | ``500`` |
274| notification.async.executor. | | |
275| queue-capacity | | |
276+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
277| config.additional. | If the executor should wait for the tasks to be completed on shutdown | ``true`` |
278| notification.async.executor. | | |
279| wait-for-tasks-to-complete-on-shutdown| | |
280+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
281| config.additional. | Prefix to be added to the thread name in asynchronous execution of notifications. | ``async_`` |
282| notification.async.executor. | | |
283| thread-name-prefix | | |
284+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
Renu Kumarifb4caa62022-03-21 09:18:41 -0400[diff] [blame]285| config.additional. | Specifies number of database connections between database and application. | ``10`` |
286| spring.datasource.hikari. | This property controls the maximum size that the pool is allowed to reach, | |
287| maximumPoolSize | including both idle and in-use connections. | |
288+---------------------------------------+---------------------------------------------------------------------------------------------------------+-------------------------------+
puthuparambil.aditya841e3df2021-10-05 10:56:04 +0100[diff] [blame]289
290CPS-Core Docker Installation
291============================
292
293CPS-Core can also be installed in a docker environment. Latest `docker-compose <https://github.com/onap/cps/blob/master/docker-compose/docker-compose.yml>`_ is included in the repo to start all the relevant services.
294The latest instructions are covered in the `README <https://github.com/onap/cps/blob/master/docker-compose/README.md>`_.