From a0b7010ed18a04e4a1aa6a6db2d6b0a18072e955 Mon Sep 17 00:00:00 2001 From: Ezhilarasi Date: Wed, 14 Aug 2019 23:38:10 +0530 Subject: Formatted Doc text Formmated contents of Read the docs text Change-Id: I44ebf3894f55ad72c35600f263b58a3235880af4 Issue-ID: CCSDK-1453 Signed-off-by: Ezhilarasi --- docs/microservices/bluePrintsProcessorMS.rst | 26 ++++++++++++++++++++------ 1 file changed, 20 insertions(+), 6 deletions(-) (limited to 'docs/microservices') diff --git a/docs/microservices/bluePrintsProcessorMS.rst b/docs/microservices/bluePrintsProcessorMS.rst index 3f308138f..bd0b6997d 100644 --- a/docs/microservices/bluePrintsProcessorMS.rst +++ b/docs/microservices/bluePrintsProcessorMS.rst @@ -34,7 +34,9 @@ Check out the latest code from Gerrit: https://gerrit.onap.org/r/#/admin/project 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 +.. code-block:: none + + mvn clean install -DskipTests=true -Dmaven.test.skip=true -Dmaven.javadoc.skip=true -Dadditionalparam=-Xdoclint:none Create the needed Docker images: @@ -42,27 +44,39 @@ The Blueprints Processor microservice project has a module, called distribution, 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/ +.. code-block:: none + + cd ms/blueprintsprocessor/distribution/ + Build it using the Maven profile called Docker: - mvn clean install -Pdocker +.. code-block:: none + + mvn clean install -Pdocker Start Docker containers using docker-composer: ---------------------------------------------- Navigate to the docker-compose file in the distribution module: - cd src/main/dc/ +.. code-block:: none + + cd src/main/dc/ From there, start the containers: - docker-compose up -d +.. code-block:: none + + 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 +.. code-block:: none + + docker-compose logs -f Testing the environment: -- cgit 1.2.3-korg