Gitiles
Code Review Sign In
gerrit.nordix.org / onap / dcaegen2 / platform / blueprints / b9d1f7a30168cc1811b63b442a7e546e69e57d78
commitb9d1f7a30168cc1811b63b442a7e546e69e57d78[log] [tgz]
authorVijay Venkatesh Kumar <vv770d@att.com>Mon Mar 02 23:36:13 2020 +0000
committerVijay Venkatesh Kumar <vv770d@att.com>Mon Mar 02 23:38:28 2020 +0000
tree1bb5a426ac8fbb41efc0989b89f6e6bc9b0548cf
parent7ff0bf92b927d244550e9b3d489930feda5ac602 [diff]
Fix bp defaults for passing dashboard typecheck

Change-Id: I4ff351fb55ffc7d4bfa4f3d63bbfa9b8fb7addfe
Signed-off-by: Vijay Venkatesh Kumar <vv770d@att.com>
Issue-ID: DCAEGEN2-2120
8 files changed
tree: 1bb5a426ac8fbb41efc0989b89f6e6bc9b0548cf
  1. blueprints/
  2. config/
  3. reference_templates/
  4. releases/
  5. scripts/
  6. .gitignore
  7. .gitreview
  8. Dockerfile-template
  9. INFO.yaml
  10. LICENSE.txt
  11. mvn-phase-script.sh
  12. pom.xml
  13. README.md
  14. version.properties
README.md

DCAE Blueprints and Bootstrap Container

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.

DCAE Bootstrap Container

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 Manager
  • CMPASS -- the password for Cloudify Manager

The 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.