4 DL-handler consists of three pods- the feeder, admin UI and des. It can be deployed by using cloudify blueprint. Datalake can be easily deployed through DCAE cloudify manager. The following steps guides you launch Datalake though cloudify manager.
8 Make sure mariadb-galera from OOM is properly deployed and functional.
9 An external database, such as Elasticsearch and MongoDB is deployed. Install mongodb through the following command.
11 #docker run -itd --restart=always --name dl-mongo -p 27017:27017 mongo
13 For DES service deployment, presto service is deployed. Here is a sample how presto deploy in the environment.
15 The package of presto version we are using is v0.0.2:presto-v0.0.2.tar.gz
17 #docker build -t presto:v0.0.2 .
18 #docker tag presto:v0.0.2 registry.baidubce.com/onap/presto:v0.0.2
19 #docker push registry.baidubce.com/onap/presto:v0.0.2
21 Note: Replace the repository path with your own repository.
23 Install presto service:
25 #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"
26 #kubectl -n onap expose deployment dl-presto --port=9000 --target-port=9000 --type=NodePort
28 Note: MonoDB_IP and Mongo_PORT you can replace this two values with your own configuration.
30 After datalake getting deployed, the admin UI can be used to configure the sink database address and credentials.
32 Log-in to the DCAE Bootstrap POD
33 --------------------------------
35 First, we should find the bootstrap pod name through the following command and make sure that DCAE coudify manager is properly deployed.
36 .. image :: ./images/bootstrap-pod.png
38 Login to the DCAE bootstrap pod through the following command.
41 #kubectl exec -it <DCAE bootstrap pod> /bin/bash -n onap
45 Before the blueprints uploading to Cloudify manager, the blueprints shoule be validated first through the following command.
48 #cfy blueprint validate /bluerints/k8s-datalake-feeder.yaml
49 #cfy blueprint validate /blueprints/k8s-datalake-admin-ui.yaml
50 #cfy blueprint validate /blueprints/k8s-datalake-des.yaml
52 Upload the Blueprint to Cloudify Manager.
53 -----------------------------------------
54 After validating, we can start to proceed blueprints uploading.
57 #cfy blueprint upload -b dl-feeder /bluerints/k8s-datalake-feeder.yaml
58 #cfy blueprint upload -b dl-admin-ui /blueprints/k8s-datalake-admin-ui.yaml
59 #cfy blueprint upload -b des /blueprints/k8s-datalake-des.yaml
61 Verify Uploaded Blueprints
62 --------------------------
63 Using "cfy blueprint list" to verify your work.
68 You can see the following returned message to show the blueprints have been correctly uploaded.
69 .. image :: ./images/blueprint-list.png
72 Verify Plugin Versions
73 ----------------------
74 If the version of the plugin used is different, update the blueprint import to match.
81 Here we are going to create deployments for both feeder and admin UI.
84 #cfy deployments create -b dl-feeder feeder-deploy
85 #cfy deployments create -b dl-admin-ui admin-ui-deploy
86 #cfy deployments create -b des des
90 Next, we are going to launch the datalake.
93 #cfy executions start -d feeder-deploy install
94 #cfy executions start -d admin-ui-deploy install
95 #cfy executions start -d des install
98 Verify the Deployment Result
99 ----------------------------
100 The following command can be used to list the datalake logs.
102 .. code-block :: bash
104 #kubectl logs <datalake-pod> -n onap
106 The output should looks like.
107 .. image :: ./images/feeder-log.png
109 The des output should looks like.
110 .. image :: ./des-log.png
112 If you find any Java exception from log, make sure that the external database and datalake configuration are properly configured.
113 Admin UI can be used to configure the external database configuration.
118 Uninstall running component and delete deployment
119 .. code-block :: bash
121 #cfy uninstall feeder-deploy
122 #cfy uninstall admin-ui-deploy
127 .. code-block :: bash
129 #cfy blueprints delete dl-feeder
130 #cfy blueprints delett dl-admin-ui
131 #cfy blueprints delete des