path: root/docs/development/devtools/devtools.rst

.. This work is licensed under a
.. Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0

.. _policy-development-tools-label:

Policy Platform Development Tools
#################################

.. contents::
    :depth: 3


This article explains how to build the ONAP Policy Framework for development purposes and how to run stability/
performance tests for a variety of components. To start, the developer should consult the latest ONAP Wiki to
familiarize themselves with developer best practices and how-tos to setup their environment,
see `https://wiki.onap.org/display/DW/Developer+Best+Practices`.

This article assumes that:

* You are using a *\*nix* operating system such as linux or macOS.
* You are using a directory called *git* off your home directory *(~/git)* for your git repositories
* Your local maven repository is in the location *~/.m2/repository*
* You have copied the settings.xml from oparent to *~/.m2/* directory
* You have added settings to access the ONAP Nexus to your M2 configuration,
  see `Maven Settings Example <https://wiki.onap.org/display/DW/Setting+Up+Your+Development+Environment>`_
  (bottom of the linked page)

The procedure documented in this article has been verified to work on a MacBook laptop running macOS Mojave Version
10.14.6 and an Ubuntu 18.06 VM.

Cloning All The Policy Repositories
***********************************

Run a script such as the script below to clone the required modules from the
`ONAP git repository <https://gerrit.onap.org/r/admin/repos/q/filter:policy>`_.
This script clones all the ONAP Policy Framework repositories.

ONAP Policy Framework has dependencies to the ONAP Parent *oparent* module, the ONAP ECOMP SDK *ecompsdkos* module,
and the A&AI Schema module.


.. code-block:: bash
   :caption: Typical ONAP Policy Framework Clone Script
   :linenos:

    #!/usr/bin/env bash

    ## script name for output
    MOD_SCRIPT_NAME=`basename $0`

    ## the ONAP clone directory, defaults to "onap"
    clone_dir="onap"

    ## the ONAP repos to clone
    onap_repos="\
    policy/parent \
    policy/common \
    policy/models \
    policy/docker \
    policy/api \
    policy/pap \
    policy/apex-pdp \
    policy/drools-pdp \
    policy/drools-applications \
    policy/xacml-pdp \
    policy/distribution \
    policy/clamp "

    ##
    ## Help screen and exit condition (i.e. too few arguments)
    ##
    Help()
    {
        echo ""
        echo "$MOD_SCRIPT_NAME - clones all required ONAP git repositories"
        echo ""
        echo "       Usage:  $MOD_SCRIPT_NAME [-options]"
        echo ""
        echo "       Options"
        echo "         -d          - the ONAP clone directory, defaults to '.'"
        echo "         -h          - this help screen"
        echo ""
        exit 255;
    }

    ##
    ## read command line
    ##
    while [ $# -gt 0 ]
    do
        case $1 in
            #-d ONAP clone directory
            -d)
                shift
                if [ -z "$1" ]; then
                    echo "$MOD_SCRIPT_NAME: no clone directory"
                    exit 1
                fi
                clone_dir=$1
                shift
            ;;

            #-h prints help and exists
            -h)
                Help;exit 0;;

            *)    echo "$MOD_SCRIPT_NAME: undefined CLI option - $1"; exit 255;;
        esac
    done

    if [ -f "$clone_dir" ]; then
        echo "$MOD_SCRIPT_NAME: requested clone directory '$clone_dir' exists as file"
        exit 2
    fi
    if [ -d "$clone_dir" ]; then
        echo "$MOD_SCRIPT_NAME: requested clone directory '$clone_dir' exists as directory"
        exit 2
    fi

    mkdir $clone_dir
    if [ $? != 0 ]
    then
        echo cannot clone ONAP repositories, could not create directory '"'$clone_dir'"'
        exit 3
    fi

    for repo in $onap_repos
    do
        repoDir=`dirname "$repo"`
        repoName=`basename "$repo"`

        if [ ! -z $dirName ]
        then
            mkdir "$clone_dir/$repoDir"
            if [ $? != 0 ]
            then
                echo cannot clone ONAP repositories, could not create directory '"'$clone_dir/repoDir'"'
                exit 4
            fi
        fi

        git clone https://gerrit.onap.org/r/${repo} $clone_dir/$repo
    done

    echo ONAP has been cloned into '"'$clone_dir'"'


Execution of the script above results in the following directory hierarchy in your *~/git* directory:

    *  ~/git/onap
    *  ~/git/onap/policy
    *  ~/git/onap/policy/parent
    *  ~/git/onap/policy/common
    *  ~/git/onap/policy/models
    *  ~/git/onap/policy/api
    *  ~/git/onap/policy/pap
    *  ~/git/onap/policy/docker
    *  ~/git/onap/policy/drools-applications
    *  ~/git/onap/policy/drools-pdp
    *  ~/git/onap/policy/clamp
    *  ~/git/onap/policy/apex-pdp
    *  ~/git/onap/policy/xacml-pdp
    *  ~/git/onap/policy/distribution


Building ONAP Policy Framework Components
*****************************************

**Step 1:** Optionally, for a completely clean build, remove the ONAP built modules from your local repository.

    .. code-block:: bash

        rm -fr ~/.m2/repository/org/onap


**Step 2:**  A pom such as the one below can be used to build the ONAP Policy Framework modules. Create the *pom.xml*
file in the directory *~/git/onap/policy*.

.. code-block:: xml
   :caption: Typical pom.xml to build the ONAP Policy Framework
   :linenos:

    <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
        <modelVersion>4.0.0</modelVersion>
        <groupId>org.onap</groupId>
        <artifactId>onap-policy</artifactId>
        <version>1.0.0-SNAPSHOT</version>
        <packaging>pom</packaging>
        <name>${project.artifactId}</name>
        <inceptionYear>2017</inceptionYear>
        <organization>
            <name>ONAP</name>
        </organization>

        <modules>
            <module>parent</module>
            <module>common</module>
            <module>models</module>
            <module>api</module>
            <module>pap</module>
            <module>apex-pdp</module>
            <module>xacml-pdp</module>
            <module>drools-pdp</module>
            <module>drools-applications</module>
            <module>distribution</module>
            <module>clamp</module>
        </modules>
    </project>

**Policy Architecture/API Transition**

In Dublin, a new Policy Architecture was introduced. The legacy architecture runs in parallel with the new
architecture. It will be deprecated after Frankfurt release. If the developer is only interested in working with the
new architecture components, the engine sub-module can be ommitted.


**Step 3:** You can now build the Policy framework.

Java artifacts only:

    .. code-block:: bash

       cd ~/git/onap
       mvn clean install

With docker images:

    .. code-block:: bash

       cd ~/git/onap
       mvn clean install -P docker

Developing and Debugging each Policy Component
**********************************************


Running the API component standalone
++++++++++++++++++++++++++++++++++++

Assuming you have successfully built the codebase using the instructions above. The only requirement for the API
component to run is a running MariaDb/Postgres database instance. The easiest way to do this is to run the docker
image, please see the official documentation for the latest information on doing so. Once the database is up and
running, a configuration file must be provided to the api in order for it to know how to connect to the database.
You can locate the default configuration file in the packaging of the api component:

`Default Policy API Configuration <https://github.com/onap/policy-api/blob/master/packages/policy-api-tarball/src/main/resources/etc/apiParameters.yaml>`_

You will want to change the fields pertaining to "host", "port" and "databaseUrl" to your local environment settings
and start the policy-api springboot application either using your IDE of choice or using the run goal from Spring Boot
Maven plugin: *mvn spring-boot:run*.

Running the API component using Docker Compose
++++++++++++++++++++++++++++++++++++++++++++++

An example of running the api using a docker compose script is located in the Policy Integration CSIT test repository.

`Policy CSIT Docker Compose <https://github.com/onap/policy-docker/blob/master/compose/compose.yaml>`_

Running the PAP component standalone
++++++++++++++++++++++++++++++++++++

Once you have successfully built the PAP codebase, a running MariaDb/Postgres database and Kafka instance will also be
required to start up the application. To start database and Kafka, check official documentation on how to run an
instance of each. After database and Kafka are up and running, a configuration file must be provided to the PAP
component in order for it to know how to connect to the database and Kafka along with other relevant configuration
details. You can locate the default configuration file in the packaging of the PAP component:

`Default PAP Configuration <https://github.com/onap/policy-pap/blob/master/packages/policy-pap-tarball/src/main/resources/etc/papParameters.yaml>`_

Update the fields related to database, Kafka and the RestServer for the application as per your local environment
settings. Then to start the application, just run the Spring Boot application using IDE or command line.


Running the Smoke Tests
***********************

The following links contain instructions on how to run the smoke tests. These may be helpful to developers to become
familiar with the Policy Framework components and test any local changes.

.. toctree::
   :maxdepth: 1

   smoke/db-migrator-smoke.rst
   smoke/acm-participants-smoke.rst
   smoke/clamp-smoke.rst
   smoke/clamp-ac-participant-protocol-smoke.rst
   smoke/policy-participant-smoke.rst
   smoke/api-smoke.rst
   smoke/pap-smoke.rst
   smoke/apex-smoke.rst
   smoke/drools-smoke.rst
   smoke/xacml-smoke.rst
   smoke/distribution-smoke.rst


Running the Stability/Performance Tests
***************************************

The following links contain instructions on how to run the S3P Stability and Performance tests. These may be helpful
to developers to become familiar with the Policy Framework components and test any local changes.

.. toctree::
   :maxdepth: 2

   testing/s3p/run-s3p.rst
   testing/s3p/api-s3p.rst
   testing/s3p/pap-s3p.rst
   testing/s3p/apex-s3p.rst
   testing/s3p/drools-s3p.rst
   testing/s3p/xacml-s3p.rst
   testing/s3p/distribution-s3p.rst
   testing/s3p/clamp-s3p.rst


Running the Pairwise Tests
**************************

The following links contain instructions on how to run the pairwise tests. These may be helpful to developers check
that the Policy Framework works in a full ONAP deployment.

.. toctree::
   :maxdepth: 1

   pairwise/clamp-policy.rst
   pairwise/clamp-dcae.rst
   pairwise/policy-cds.rst
   pairwise/clamp-sdc.rst

..
   api-pairwise.rst

..
   pap-pairwise.rst

..
   apex-pairwise.rst

..
   drools-pairwise.rst

..
   xacml-pairwise.rst

..
   distribution-pairwise.rst


Running Continuous System and Integration Testing suites
********************************************************

.. toctree::
   :maxdepth: 1

   testing/csit.rst


Testing OpenSuse docker images
******************************

Policy Framework offers docker images in two flavors: Alpine and OpenSuse.
Alpine images are used in OOM for ONAP deployments.
The OpenSuse images are built manually if needed, by running Maven with the -Pdockersuse profile.
To test these images, CSITs will be run.

1. Build the OpenSuse image you want by running Maven with -Pdockersuse:

    .. code-block:: bash

        cd policy/apex-pdp
        mvn clean install -Pdockersuse

    The image onap/policy-apex-pdp:latest will be produced.

2. To avoid ambiguity, tag the image as opensuse:

    .. code-block:: bash

        docker tag onap/policy-apex-pdp:latest onap/policy-apex-pdp:opensuse

3. Clone policy/docker repo.

4. Modify docker/csit/docker-compose.yml to use the tagged OpenSuse image.

    Replace:

    .. code-block:: yaml

        apex-pdp:
          image: nexus3.onap.org:10001/onap/policy-apex-pdp:${POLICY_APEX_PDP_VERSION}

    with:

    .. code-block:: yaml

        apex-pdp:
          image: onap/policy-apex-pdp:opensuse

5. Run the project CSIT. For apex-pdp:

    .. code-block:: bash

        cd docker/csit
        ./run-project-csit.sh apex-pdp

    Automated tests will be run, and log files displayed.

Running Policy Components Locally
*********************************

The following page outlines how to run the policy framework components locally using IntelliJ,
Eclipse and the Command Line.

.. toctree::
   :maxdepth: 1

   ./installation/local-installation.rst

Running the Policy Framework in Microk8s
****************************************

The following page outlines how to run the policy framework components using microk8s.

.. toctree::
   :maxdepth: 1

   ./installation/microk8s-installation.rst


Generating Swagger Documentation
********************************

1. Accessing Swagger documentation for springboot based policy applications
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Springfox Swagger2 maven dependency aids with auto-generation of Swagger documentation.

Using the Swagger-UI maven dependency Swagger HTML documentation can be accessed at the root url.

- The generated swagger.json can be accessed at: *https://service_IP:service_port/v2/api-docs*
- Swagger UI can be accessed at: *https://service_IP:service_port/swagger-ui/index.html*


Bringing up Strimzi-Kafka Deploment with Policy Framework
*********************************************************

This page will explain how to setup a local Kubernetes cluster and minimal helm setup to run and deploy
Policy Framework on a single host.

This is meant for a development purpose only as we are going to use microk8s in this page:

.. toctree::
   :maxdepth: 1

   strimzi-policy.rst