| commit | dd0ceb35abdd19678e2a3a88e1fd923192d155af | [log] [tgz] |
|---|---|---|
| author | Vijay Venkatesh Kumar <vv770d@att.com> | Wed Mar 04 18:38:22 2020 +0000 |
| committer | Gerrit Code Review <gerrit@onap.org> | Wed Mar 04 18:38:22 2020 +0000 |
| tree | 122a5a515ecff4d41f5827fae22f6abdec574ea9 | |
| parent | 1274e65f0edecf81c64dbcf6980342236f33a394 [diff] | |
| parent | 2df41c826778908d19584672a123bf9db6a6866e [diff] |
Merge "Upload latest pgaas & sshkeyshare plugins"
This repository holds the source code needed to build the Docker image for the DCAE bootstrap container. The bootstrap container runs at DCAE deployment time (via a Helm chart) and does initial setup of the DCAE environment. This includes deploying several service components using Cloudify Manager.
This repository also holds Cloudify blueprints for service components. The Docker build process copies these blueprints into the Docker image for the bootstrap container.
Note: Prior to the Frankfurt release (R6), this repository held blueprint templates for components deployed using Cloudify Manager. The build process for this repository expanded the templates and pushed them to the Nexus raw repository. The DCAE bootstrap container was hosted in the dcaegen2.deployments repository. The Docker build process for the bootstrap containter image pulled the blueprints it needed from the Nexus raw repository.
This container is responsible for loading plugins and wagons onto the DCAE Cloudify Manager instance and for launching DCAE components.
The Docker image build process loads plugins and blueprints into the image's file system. The plugins are pulled from the Nexus raw repository. The blueprints are copied from the blueprints directory in this repository. At run time, the main script in the container (bootstrap.sh) uploads the plugins to Cloudify Manager, then installs components using the blueprints.
The container expects to be started with two environment variables:
CMADDR -- the address of the target Cloudify ManagerCMPASS -- the password for Cloudify ManagerThe container expects input files to use when deploying the blueprints. It expects to find them in /inputs. The normal method for launching the container is via a Helm Chart launched by OOM. That chart creates a Kubernetes ConfigMap containing the input files. The ConfigMap is mounted as a volume at /inputs.