blob: 5d8b3341e04270b704427f270d31cb273d029f67 (
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
|
Deployment Steps
################
DL-handler consists of two pods- the feeder and admin UI. 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.
Pre-requisite
----------------
- Make sure mariadb-galera from OOM is properly deployed and functional.
- An external database, such as Elasticsearch and MongoDB is deployed.
After datalake getting deployed, the admin UI can be used to configure the sink database address and credentials.
Log-in to the DCAE Bootstrap POD
---------------------------------------------------
First, we should find the bootstrap pod name through the following command and make sure that DCAE coudify manager is properly deployed.
.. image :: .images/bootstrap-pod.png
Login to the DCAE bootstrap pod through the following command.
.. code-block :: bash
#kubectl exec -it <DCAE bootstrap pod> /bin/bash -n onap
Validate Blueprint
-------------------
Before the blueprints uploading to Cloudify manager, the blueprints shoule be validated first throuhg the following command.
.. code-block :: bash
#cfy blueprint validate /bluerints/k8s-datalake-feeder.yaml
#cfy blueprint validate /blueprints/k8s-datalake-admin-ui.yaml
Upload the Blueprint to Cloudify Manager.
-----------------------------------------
After validating, we can start to proceed blueprints uploading.
.. code-block :: bash
#cfy blueprint upload -b datalake-feeder /bluerints/k8s-datalake-feeder.yaml
#cfy blueprint upload -b datalake-admin-ui /blueprints/k8s-datalake-admin-ui.yaml
Verify Uploaded Blueprints
--------------------------
Using "cft blueprint list" to varify your work.
.. code-block :: bash
#cfy blueprint list
You can see the following returned message to show the blueprints have been correctly uploaded.
.. image :: ./imagesblueprint-list.png
Verify Plugin Versions
------------------------------------------------------------------------------
If the version of the plugin used is different, update the blueprint import to match.
.. code-block :: bash
#cfy plugins list
Create Deployment
-----------------
Here we are going to create deployments for both feeder and admin UI.
.. code-block :: bash
#cfy deployments create -b datalake-feeder feeder-deploy
#cfy deployments create -b datalake-admin-ui admin-ui-deploy
Launch Service
---------------
Next, we are going to launch the datalake.
.. code-block :: bash
#cfy executions start -d feeder-deploy install
#cfy executions start -d admin-ui-deploy install
Verify the Deployment Result
-----------------------------
The following command can be used to list the datalake logs.
.. code-block :: bash
#kubectl logs <datalake-pod> -n onap
The output should looks like.
.. image :: ./feeder-log.png
If you find any Java exception from log, make sure that the external database and datalake configuration are properly configured.
Admin UI can be used to configure the external database configuration.
Uninstall
----------
Uninstall running component and delete deployment
.. code-block :: bash
#cfy uninstall feeder-deploy
#cfy uninstall admin-ui-deploy
Delete Blueprint
------------------
.. code-block :: bash
#cfy blueprints delete datalake-feeder
#cfy blueprints deltet datalake-admin-ui
|
