| Table of Contents |
|---|
Overview
...
Βlueprint (deployment artifact) : k8s-datalake-feeder.yaml, k8s-datalake-admin-ui.yaml
Docker image image:
feeder, onap/org.onap.dcaegen2.services.datalakefeeder:1.0.0
admin UI, onap/org.onap.dcaegen2.services.datalakeadminui:1.0.1
Deployment Prerequisite/dependencies
Since datalake can log the message from the DMaap to several different external databases, such as Elasticsearch, Couch Base, MongoDB, Relational databases...etc. Once Datalake is successfully deployed, you can start to deploy configure the external databases and configure the sink databases through our admin UI. The following sections will guide you to deploy datalake microservice, including cloudify blueprint upload, deployment, and un-deployment.
...
Log-in to the DCAE bootstrap POD's main container
First, we should find the bootstrap pod name through the following command and make sure that DCAE coudify manager is properly deployed.
Login to the DCAE bootstrap pod through the following command.
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
kubectl exec -it <DCAE bootstrap pod> /bin/bash -n onap |
...
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
cfy blueprint list |
...
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
cfy blueprints delete datalake-feeder cfy blueprints deltet datalake-admin-ui |
Deploy external database
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
docker run -d -p 27017:27017 --name mongodb mongo
docker start mongodb |