NOTE: Instructions are valid ONLY for the Dublin release. In El Alto, the release controller blueprint microservice functionality has been consolidated into blueprints processor microservice.  

→ Yes, let's move all this documentation to git (readthedocs)

Objective

The purpose of this page is to show how to run the Blueprints Controller microservice locally, using the docker-compose.yaml file provided in the project.

Check out the CDS' code

Check out the latest code from Gerrit: https://gerrit.onap.org/r/#/admin/projects/ccsdk/cds

Build CDS locally

In the checked out directory, type

    mvn clean install -DskipTests=true -Dmaven.test.skip=true -Dmaven.javadoc.skip=true -Dadditionalparam=-Xdoclint:none

Create the needed Docker images

The Blueprints Controller microservice project has a module, called distribution, that provides a docker-compose.yaml file that can be used to spin up Docker containers to run this microservice.

The first step is to create any custom image needed, by building the distribution module.  From the CDS home directory (where the code was checked out), navigate to the module:

    cd ms/controllerblueprints/distribution/

Build it using the Maven profile called Docker:

    mvn clean install -Pdocker

Start Docker containers using docker-composer

Navigate to the docker-compose file in the distribution module:

    cd src/main/dc/

From there, start the containers:

    docker-compose up -d

This will spin the Docker containers declared inside the docker-compose.yaml file in the background:

To verify the logs generated by docker-composer, type:

    docker-compose logs -f

Testing the environment

Point your browser to http://localhost:8080/api/v1/blueprint-model

To authenticate, use ccsdkapps / ccsdkapps as login / password.


















  • No labels