Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Objective

The purpose of this page is to show how to run the Blueprints Processor 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

Pre-requisite: Use attached settings.xml to have recommended repository settings 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 Processor 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/blueprintsprocessor/distribution/

Build it using the Maven profile called Docker:

    mvn clean install -Pdocker



 El Alto

Start Docker containers using docker-composer

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

    cd src/main/dc/

Edit docker-compose.yaml as below

docker-compose.yaml
version: '3.3'

services:
  db:
    image: mariadb:latest
    container_name: ccsdk-mariadb
    ports:
    - "3306:3306"
    volumes:
    - ~/vm_mysql:/var/lib/mysql
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: sdnctl
      MYSQL_DATABASE: sdnctl
      MYSQL_USER: sdnctl
      MYSQL_PASSWORD: sdnctl
      MYSQL_INITDB_SKIP_TZINFO: 1
  blueprints-processor:
    depends_on:
    - db
    image: onap/ccsdk-blueprintsprocessor:latest
    container_name: bp-rest
    ports:
    - "8000:8080"
    restart: always
    environment:
      APPLICATIONNAME: BlueprintsProcessor
      BUNDLEVERSION: 1.0.0
      APP_CONFIG_HOME: /opt/app/onap/config
      STICKYSELECTORKEY:
      ENVCONTEXT: dev


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
 Dublin

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:8000/api/v1/execution-service/ping (please note that the port is 8000, not 8080)

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


















  • No labels