Gitiles
Code Review Sign In
gerrit.nordix.org / onap / dcaegen2 / platform / blueprints / 9df737ec9c8d9d0e2dfc0e13f7d369b801a20abd
commit9df737ec9c8d9d0e2dfc0e13f7d369b801a20abd[log] [tgz]
authordhebeha <dhebeha.mj71@wipro.com>Tue Sep 22 15:20:43 2020 +0530
committerdhebeha <dhebeha.mj71@wipro.com>Wed Sep 30 17:30:22 2020 +0530
tree876c077424c774d4278c77d4b77693cab6f97a82
parentfac7c42190aabbd45c7bb7673e7414b96ff65fce [diff]
Add blueprint for slice analysis ms

Issue-ID: DCAEGEN2-2255
Signed-off-by: dhebeha <dhebeha.mj71@wipro.com>
Change-Id: I964b03144c65ed3fd07df2302a7b1950d5dbc9a1
1 file changed
tree: 876c077424c774d4278c77d4b77693cab6f97a82
  1. blueprints/
  2. reference_templates/
  3. releases/
  4. scripts/
  5. .gitignore
  6. .gitreview
  7. Dockerfile-template
  8. INFO.yaml
  9. LICENSE.txt
  10. mvn-phase-script.sh
  11. pom.xml
  12. README.md
  13. 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 blueprints onto the DCAE Cloudify Manager instance and for launching DCAE components.

The Docker image build process loads blueprints into the image's file system. The blueprints are copied from the blueprints directory in this repository. At run time, the main script in the container (bootstrap.sh) 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.