summaryrefslogtreecommitdiffstats
path: root/docs/sections/services/datalake-handler/installation-helm.rst
blob: e52f2fa2c92da213174c599603aebefbbb7df7cf (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
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
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. _dl-installation-helm:

Helm Installation
=================

DL-handler consists of three pods- the feeder, admin UI and des. It can be deployed by using helm charts. The following steps guides you launch datalake though helm.


Pre-requisites
~~~~~~~~~~~~~~
- Datalake postgres should be properly deployed and functional.

- Presto service should be deployed for des deployment.Here is a sample how presto is deployed in the environment.

   Deploying presto service:
    The package of presto version we are using is v0.0.2:presto-v0.0.2.tar.gz

     #docker build -t presto:v0.0.2 .
     #docker tag presto:v0.0.2 registry.baidubce.com/onap/presto:v0.0.2
     #docker push registry.baidubce.com/onap/presto:v0.0.2

    Note: Replace the repository path with your own repository.

     #kubectl -n onap run dl-presto --image=registry.baidubce.com/onap/presto:v0.0.2 --env="MongoDB_IP=192.168.235.11" --env="MongoDB_PORT=27017"
     #kubectl -n onap expose deployment dl-presto --port=9000 --target-port=9000 --type=NodePort

    Note: MonoDB_IP and Mongo_PORT you can replace this two values with your own configuration.

- The environment should have helm and kubernetes installed.

- Check whether all the charts mentioned in the requirements.yaml file are present in the charts/ folder. If not present, package the respective chart and put it in the charts/ folder.

 For example:
    .. code-block:: bash

        helm package <dcaegen2-services-common>


Deployment steps
~~~~~~~~~~~~~~~~
Validate the charts using below commands
    .. code-block:: bash

        helm lint <dcae-datalake-admin-ui>
        helm lint <dcae-datalake-feeder>
        helm lint <dcae-datalake-des>

Deploy the charts using below commands
    .. code-block:: bash

        helm install <datalake-admin-ui> <dcae-datalake-admin-ui> --namespace onap --set global.masterPassword=<password>
        helm install <datalake-feeder> <dcae-datalake-feeder> --namespace onap --set global.masterPassword=<password>
        helm install <datalake-des> <dcae-datalake-des> --namespace onap --set global.masterPassword=<password>

For checking logs of the containers
    .. code-block:: bash

        kubectl logs -f -n onap <dev-dcae-datalake-admin-ui-843bfsk4f4-btd7s> -c <dcae-datalake-admin-ui>
        kubectl logs -f -n onap <dev-dcae-datalake-feeder-758bbf547b-ctf6s> -c <dcae-datalake-feeder>
        kubectl logs -f -n onap <dev-dcae-datalake-des-56465d86fd-2w56c> -c <dcae-datalake-des>

To un-deploy
    .. code-block:: bash

        helm uninstall <datalake-admin-ui>
        helm uninstall <datalake-feeder>
        helm uninstall <datalake-des>


Application configurations
~~~~~~~~~~~~~~~~~~~~~~~~~~
Datalake-admin-ui:

+-------------------------------+------------------------------------------------+
|Configuration                  | Description                                    |
+===============================+================================================+
|FEEDER_ADDR                    | Host where dl-feeder is running                |
+-------------------------------+------------------------------------------------+

Datalake-feeder:

+-------------------------------+------------------------------------------------+
|Configuration                  | Description                                    |
+===============================+================================================+
|PRESTO_HOST                    | Host where the presto application is running   |
+-------------------------------+------------------------------------------------+
|PG_HOST                        | Host where the postgres application is running |
+-------------------------------+------------------------------------------------+
|CONSUL_HOST                    | Host where counsul loader container is running |
+-------------------------------+------------------------------------------------+
|PG_DB                          | Postgress database name                        |
+-------------------------------+------------------------------------------------+

Datalake-Des:

+-------------------------------+------------------------------------------------+
|Configuration                  | Description                                    |
+===============================+================================================+
|PRESTO_HOST                    | Host where the presto application is running   |
+-------------------------------+------------------------------------------------+
|PG_HOST                        | Host where the postgres application is running |
+-------------------------------+------------------------------------------------+
|PG_DB                          | Postgress database name                        |
+-------------------------------+------------------------------------------------+