.. code-block:: bash
-cd ~/git/onap/policy/api/packages
-mvn clean install -P docker
+ cd ~/git/onap/policy/api/packages
+ mvn clean install -P docker
**Step 2:** Build the Policy PAP Docker image
.. code-block:: bash
-cd ~/git/onap/policy/pap/packages
-mvn clean install -P docker
+ cd ~/git/onap/policy/pap/packages
+ mvn clean install -P docker
**Step 3:** Build the Drools PDP docker image.
.. code-block:: bash
-cd ~/git/onap/policy/drools-pdp/
-./docker_verify.sh
+ cd ~/git/onap/policy/drools-pdp/
+ mvn clean install -P docker
**Step 4:** Build the Drools Application Control Loop image.
.. code-block:: bash
-cd ~/git/onap/policy/drools-applications
-chmod 755 controlloop/build/docker-cl
-controlloop/build/docker-cl --verify
+ cd ~/git/onap/policy/drools-applications
+ mvn clean install -P docker
**Step 5:** Build the Apex PDP docker image:
.. code-block:: bash
-cd ~/git/onap/policy/apex-pdp/packages/apex-pdp-docker/target
-docker build -t onap/policy-apex-pdp policy-apex-pdp
+ cd ~/git/onap/policy/apex-pdp
+ mvn clean install -P docker
-**Step 5:** Build the XACML PDP docker image:
+**Step 6:** Build the XACML PDP docker image:
.. code-block:: bash
-cd ~/git/onap/policy/xacml-pdp/packages
-mvn clean install -P docker
+ cd ~/git/onap/policy/xacml-pdp/packages
+ mvn clean install -P docker
**Step 7:** Build the policy engine docker image (If working with the legacy Policy Architecture/API):
.. code-block:: bash
-cd ~/git/onap/policy/engine/
-./docker_verify.sh
+ cd ~/git/onap/policy/engine/
+ mvn clean install -P docker
**Step 8:** Build the Policy SDC Distribution docker image:
.. code-block:: bash
-cd ~/git/onap/policy/distribution/packages
-mvn clean install -Pdocker
+ cd ~/git/onap/policy/distribution/packages
+ mvn clean install -P docker
Starting the ONAP Policy Framework Docker Images
.. code-block:: bash
-export MTU=9126
+ export MTU=9126
-**Step 2:** Determine if you want policies pre-loaded or not. By default, all the configuration and operational policies will be pre-loaded by the docker compose script. If you do not wish for that to happen, then export this variable:
+**Step 2:** Determine if you want the legacy Policy Engine to have policies pre-loaded or not. By default, all the configuration and operational policies will be pre-loaded by the docker compose script. If you do not wish for that to happen, then export this variable:
+
+.. note:: This applies ONLY to the legacy Engine and not the Policy Lifecycle polices
.. code-block:: bash
-export PRELOAD_POLICIES=false
+ export PRELOAD_POLICIES=false
**Step 3:** Run the system using *docker-compose*. Note that on some systems you may have to run the *docker-compose* command as root or using *sudo*. Note that this command takes a number of minutes to execute on a laptop or desktop computer.
.. code-block:: bash
-docker-compose up -d
+ docker-compose up -d
**You now have a full standalone ONAP Policy framework up and running!**
-
-
-
-End of Document
-