X-Git-Url: https://gerrit.onap.org/r/gitweb?a=blobdiff_plain;f=docs%2Fdrools%2FpdpdEngine.rst;h=22e5cbeb2ef870193e143447f255c1416ae3f272;hb=ce601f27a0c8f2cb969d2ba2c3a5e21990b46287;hp=360d85eb524805b48644d31f66eb73051c4b2276;hpb=1afc46d467ea77769ca5c91a4debf3a2715a81b8;p=policy%2Fparent.git diff --git a/docs/drools/pdpdEngine.rst b/docs/drools/pdpdEngine.rst index 360d85eb..22e5cbeb 100644 --- a/docs/drools/pdpdEngine.rst +++ b/docs/drools/pdpdEngine.rst @@ -40,11 +40,11 @@ Docker Image ~~~~~~~~~~~~ Check the *drools-pdp* `released versions `__ page for the latest versions. -At the time of this writing *1.6.3* is the latest version. +At the time of this writing *1.8.2* is the latest version. .. code-block:: bash - docker pull onap/policy-drools:1.6.3 + docker pull onap/policy-drools:1.8.2 A container instantiated from this image will run under the non-priviledged *policy* account. @@ -60,7 +60,7 @@ The following command can be used to explore the directory layout. .. code-block:: bash - docker run --rm -it nexus3.onap.org:10001/onap/policy-drools:1.6.3 -- bash + docker run --rm -it nexus3.onap.org:10001/onap/policy-drools:1.8.2 -- bash Communication Endpoints ======================= @@ -438,7 +438,6 @@ The PDP-D also recognizes Tosca Operational Policies, although it needs an application *controller* that understands them to execute them. These are: - *onap.policies.controlloop.operational.common.Drools* -- *onap.policies.controlloop.Operational* A minimum of one application *controller* that supports these capabilities must be installed in order to honor the *operational policy types*. @@ -474,7 +473,7 @@ commit to execute policies against these policy types if a supporting controller Software Architecture -====================== +===================== PDP-D is divided into 2 layers: @@ -783,6 +782,7 @@ unnecessary or have not been thoroughly tested: feature_sesspersist.rst feature_statemgmt.rst feature_testtransaction.rst + feature_nolocking.rst Data Migration ============== @@ -872,7 +872,7 @@ The drools libraries in the PDP-D uses maven to fetch rules artifacts and softwa The default *settings.xml* file specifies the repositories to search. This configuration can be overriden with a custom copy that would sit in a mounted configuration directory. See an example of the OOM override -`settings.xml `__. +`settings.xml `_. The default ONAP installation of the *control loop* child image *onap/policy-pdpd-cl:1.6.4* is *OFFLINE*. In this configuration, the *rules* artifact and the *dependencies* retrieves all the artifacts from the local @@ -883,7 +883,7 @@ An offline configuration requires two items: - *OFFLINE* environment variable set to true. - override *settings.xml* customization, see - `settings.xml `__. + `settings.xml `_. The default mode in the *onap/policy-drools:1.6.3* is ONLINE instead. @@ -1357,7 +1357,7 @@ A post-start script *config/active.post.sh* can place PDP-D in *active* mode at .. code-block:: bash - bash -c "http --verify=no -a ${TELEMETRY_USER}:${TELEMETRY_PASSWORD} PUT https://localhost:9696/policy/pdp/engine/lifecycle/state/ACTIVE" + bash -c "http --verify=no -a ${TELEMETRY_USER}:${TELEMETRY_PASSWORD} PUT ://localhost:9696/policy/pdp/engine/lifecycle/state/ACTIVE" Bring up the PDP-D, nexus, and mariadb ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -1377,22 +1377,22 @@ To take it down: Other examples ~~~~~~~~~~~~~~ -The reader can also look at the `integration/csit repository `__. +The reader can also look at the `policy/docker repository `__. More specifically, these directories have examples of other PDP-D configurations: -* `plans `__: startup scripts. -* `scripts `__: docker-compose related files. -* `plans `__: test plan. +* `plans `__: startup & teardown scripts. +* `scripts `__: docker-compose file. +* `tests `__: test plan. Configuring the PDP-D in an OOM Kubernetes installation ======================================================= -The `PDP-D OOM chart `__ can be +The `PDP-D OOM chart `__ can be customized at the following locations: -* `values.yaml `__: custom values for your installation. -* `configmaps `__: place in this directory any configuration extensions or overrides to customize the PDP-D that does not contain sensitive information. -* `secrets `__: place in this directory any configuration extensions or overrides to customize the PDP-D that does contain sensitive information. +* `values.yaml `__: custom values for your installation. +* `configmaps `__: place in this directory any configuration extensions or overrides to customize the PDP-D that does not contain sensitive information. +* `secrets `__: place in this directory any configuration extensions or overrides to customize the PDP-D that does contain sensitive information. The same customization techniques described in the docker sections for PDP-D, fully apply here, by placing the corresponding files or scripts in these two directories. @@ -1401,4 +1401,4 @@ Additional information ====================== For additional information, please see the -`Drools PDP Development and Testing (In Depth) `__ page. +`Drools PDP Development and Testing (In Depth) `__ page.