2 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
3 .. http://creativecommons.org/licenses/by/4.0
16 PDP-D applications uses the PDP-D Engine middleware to provide domain specific services.
17 See :ref:`pdpd-engine-label` for the description of the PDP-D infrastructure.
19 At this time *Control Loops* are the only type of applications supported.
21 *Control Loop* applications must support the following *Policy Type*:
23 - **onap.policies.controlloop.operational.common.Drools** (Tosca Compliant Operational Policies)
28 Source Code repositories
29 ~~~~~~~~~~~~~~~~~~~~~~~~
31 The PDP-D Applications software resides on the `policy/drools-applications <https://git.onap.org/policy/drools-applications>`__ repository. The actor libraries introduced in the *frankfurt* release reside in
32 the `policy/models repository <https://git.onap.org/policy/models>`__.
34 At this time, the *control loop* application is the only application supported in ONAP.
35 All the application projects reside under the
36 `controlloop directory <https://git.onap.org/policy/drools-applications/tree/controlloop>`__.
41 See the *drools-applications*
42 `released versions <https://wiki.onap.org/display/DW/Policy+Framework+Project%3A+Component+Versions>`__
43 for the latest images:
47 docker pull onap/policy-pdpd-cl:1.8.2
49 At the time of this writing *1.8.2* is the latest version.
51 The *onap/policy-pdpd-cl* image extends the *onap/policy-drools* image with
52 the *usecases* controller that realizes the *control loop* application.
57 The `usecases <https://git.onap.org/policy/drools-applications/tree/controlloop/common/controller-usecases>`__
58 controller is the *control loop* application in ONAP.
60 There are three parts in this controller:
62 * The `drl rules <https://git.onap.org/policy/drools-applications/tree/controlloop/common/controller-usecases/src/main/resources/usecases.drl>`__.
63 * The `kmodule.xml <https://git.onap.org/policy/drools-applications/tree/controlloop/common/controller-usecases/src/main/resources/META-INF/kmodule.xml>`__.
64 * The `dependencies <https://git.onap.org/policy/drools-applications/tree/controlloop/common/controller-usecases/pom.xml>`__.
66 The `kmodule.xml` specifies only one session, and declares in the *kbase* section the two operational policy types that
69 The Usecases controller relies on the new Actor framework to interact with remote
70 components, part of a control loop transaction. The reader is referred to the
71 *Policy Platform Actor Development Guidelines* in the documentation for further information.
73 Operational Policy Types
74 ========================
76 The *usecases* controller supports the following policy type:
78 - *onap.policies.controlloop.operational.common.Drools*.
80 The *onap.policies.controlloop.operational.common.Drools*
81 is the Tosca compliant policy type introduced in *frankfurt*.
83 The Tosca Compliant Operational Policy Type is defined at the
84 `onap.policies.controlloop.operational.common.Drools <https://git.onap.org/policy/models/tree/models-examples/src/main/resources/policytypes/onap.policies.controlloop.operational.common.Drools.yaml>`__.
86 An example of a Tosca Compliant Operational Policy can be found
87 `here <https://git.onap.org/policy/models/tree/models-examples/src/main/resources/policies/vDNS.policy.operational.input.tosca.json>`__.
92 Since the PDP-D Control Loop Application image was created from the PDP-D Engine one (*onap/policy-drools*),
93 it inherits all features and functionality.
95 The enabled features in the *onap/policy-pdpd-cl* image are:
97 - **distributed locking**: distributed resource locking.
98 - **healthcheck**: healthcheck.
99 - **lifecycle**: enables the lifecycle APIs.
100 - **controlloop-trans**: control loop transaction tracking.
101 - **controlloop-management**: generic controller capabilities.
102 - **controlloop-usecases**: new *controller* introduced in the guilin release to realize the ONAP use cases.
104 The following features are installed but disabled:
106 - **controlloop-tdjam**: experimental java-only *controller* to be deprecated post guilin.
107 - **controlloop-utils**: *actor* simulators.
109 Control Loops Transaction (controlloop-trans)
110 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
112 It tracks Control Loop Transactions and Operations. These are recorded in
113 the *$POLICY_LOGS/audit.log* and *$POLICY_LOGS/metrics.log*, and accessible
114 through the telemetry APIs.
116 Control Loops Management (controlloop-management)
117 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
119 It installs common control loop application resources, and provides
120 telemetry API extensions. *Actor* configurations are packaged in this
123 Usecases Controller (controlloop-usecases)
124 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
126 It is the *guilin* release implementation of the ONAP use cases.
127 It relies on the new *Actor* model framework to carry out a policy's
130 TDJAM Controller (controlloop-tdjam)
131 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
133 This is an experimental, java-only controller that will be deprecated after the
136 Utilities (controlloop-utils)
137 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
139 Enables *actor simulators* for testing purposes.
144 The default ONAP installation in *onap/policy-pdpd-cl:1.8.2* is *OFFLINE*.
145 In this configuration, the *rules* artifact and the *dependencies* are all in the local
146 maven repository. This requires that the maven dependencies are preloaded in the local
149 An offline configuration requires two configuration items:
151 - *OFFLINE* environment variable set to true (see `values.yaml <https://git.onap.org/oom/tree/kubernetes/policy/values.yaml>`__.
152 - override of the default *settings.xml* (see
153 `settings.xml <https://git.onap.org/oom/tree/kubernetes/policy/components/policy-drools-pdp/resources/configmaps/settings.xml>`__) override.
155 Running the PDP-D Control Loop Application in a single container
156 ================================================================
161 First create an environment file (in this example *env.conf*) to configure the PDP-D.
165 # SYSTEM software configuration
167 POLICY_HOME=/opt/app/policy
168 POLICY_LOGS=/var/log/onap/policy/pdpd
169 KEYSTORE_PASSWD=Pol1cy_0nap
170 TRUSTSTORE_PASSWD=Pol1cy_0nap
172 # Telemetry credentials
175 TELEMETRY_HOST=0.0.0.0
176 TELEMETRY_USER=demo@people.osaaf.org
177 TELEMETRY_PASSWORD=demo123456!
181 SNAPSHOT_REPOSITORY_ID=
182 SNAPSHOT_REPOSITORY_URL=
183 RELEASE_REPOSITORY_ID=
184 RELEASE_REPOSITORY_URL=
187 REPOSITORY_OFFLINE=true
189 MVN_SNAPSHOT_REPO_URL=
190 MVN_RELEASE_REPO_URL=
192 # Relational (SQL) DB access
201 AAF_NAMESPACE=org.onap.policy
202 AAF_HOST=aaf.api.simpledemo.onap.org
204 # PDP-D DMaaP configuration channel
206 PDPD_CONFIGURATION_TOPIC=PDPD-CONFIGURATION
207 PDPD_CONFIGURATION_API_KEY=
208 PDPD_CONFIGURATION_API_SECRET=
209 PDPD_CONFIGURATION_CONSUMER_GROUP=
210 PDPD_CONFIGURATION_CONSUMER_INSTANCE=
211 PDPD_CONFIGURATION_PARTITION_KEY=
213 # PAP-PDP configuration channel
215 POLICY_PDP_PAP_TOPIC=POLICY-PDP-PAP
216 POLICY_PDP_PAP_GROUP=defaultGroup
218 # Symmetric Key for encoded sensitive data
222 # Healthcheck Feature
224 HEALTHCHECK_USER=demo@people.osaaf.org
225 HEALTHCHECK_PASSWORD=demo123456!
229 POOLING_TOPIC=POOLING
246 PDP_CONTEXT_URI=pdp/api/getDecision
248 PDP_PASSWORD=password
253 DCAE_TOPIC=unauthenticated.DCAE_CL_OUTPUT
254 DCAE_SERVERS=localhost
255 DCAE_CONSUMER_GROUP=dcae.policy.shared
259 DMAAP_SERVERS=localhost
274 SO_URL=https://localhost:6667/
282 VFC_CONTEXT_URI=api/nslcm/v1/
290 SDNC_CONTEXT_URI=restconf/operations/
298 In order to avoid the noise in the logs that relate to dmaap configuration, a startup script (*noop.pre.sh*) is added
299 to convert *dmaap* endpoints to *noop* in the host directory to be mounted.
305 sed -i "s/^dmaap/noop/g" $POLICY_HOME/config/*.properties
310 We can enable the *controlloop-utils* and disable the *distributed-locking* feature to avoid using the database.
316 bash -c "/opt/app/policy/bin/features disable distributed-locking"
317 bash -c "/opt/app/policy/bin/features enable controlloop-utils"
322 The *active.post.sh* script makes the PDP-D active.
328 bash -c "http --verify=no -a ${TELEMETRY_USER}:${TELEMETRY_PASSWORD} PUT https://localhost:9696/policy/pdp/engine/lifecycle/state/ACTIVE"
333 In the *guilin* release, some *actors* configurations need to be overridden to support *http* for compatibility
334 with the *controlloop-utils* feature.
336 AAI-http-client.properties
337 """"""""""""""""""""""""""
341 http.client.services=AAI
343 http.client.services.AAI.managed=true
344 http.client.services.AAI.https=false
345 http.client.services.AAI.host=${envd:AAI_HOST}
346 http.client.services.AAI.port=${envd:AAI_PORT}
347 http.client.services.AAI.userName=${envd:AAI_USERNAME}
348 http.client.services.AAI.password=${envd:AAI_PASSWORD}
349 http.client.services.AAI.contextUriPath=${envd:AAI_CONTEXT_URI}
351 SDNC-http-client.properties
352 """""""""""""""""""""""""""
356 http.client.services=SDNC
358 http.client.services.SDNC.managed=true
359 http.client.services.SDNC.https=false
360 http.client.services.SDNC.host=${envd:SDNC_HOST}
361 http.client.services.SDNC.port=${envd:SDNC_PORT}
362 http.client.services.SDNC.userName=${envd:SDNC_USERNAME}
363 http.client.services.SDNC.password=${envd:SDNC_PASSWORD}
364 http.client.services.SDNC.contextUriPath=${envd:SDNC_CONTEXT_URI}
366 VFC-http-client.properties
367 """"""""""""""""""""""""""
371 http.client.services=VFC
373 http.client.services.VFC.managed=true
374 http.client.services.VFC.https=false
375 http.client.services.VFC.host=${envd:VFC_HOST}
376 http.client.services.VFC.port=${envd:VFC_PORT}
377 http.client.services.VFC.userName=${envd:VFC_USERNAME}
378 http.client.services.VFC.password=${envd:VFC_PASSWORD}
379 http.client.services.VFC.contextUriPath=${envd:VFC_CONTEXT_URI:api/nslcm/v1/}
384 The *standalone-settings.xml* file is the default maven settings override in the container.
388 <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
389 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
390 xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
392 <offline>true</offline>
396 <id>policy-local</id>
399 <id>file-repository</id>
400 <url>file:${user.home}/.m2/file-repository</url>
402 <enabled>true</enabled>
403 <updatePolicy>always</updatePolicy>
406 <enabled>true</enabled>
407 <updatePolicy>always</updatePolicy>
415 <activeProfile>policy-local</activeProfile>
420 Bring up the PDP-D Control Loop Application
421 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
425 docker run --rm -p 9696:9696 -v ${PWD}/config:/tmp/policy-install/config --env-file ${PWD}/env/env.conf -it --name PDPD -h pdpd nexus3.onap.org:10001/onap/policy-pdpd-cl:1.6.4
427 To run the container in detached mode, add the *-d* flag.
429 Note that we are opening the *9696* telemetry API port to the outside world, mounting the *config* host directory,
430 and setting environment variables.
432 To open a shell into the PDP-D:
436 docker exec -it pdp-d bash
438 Once in the container, run tools such as *telemetry*, *db-migrator*, *policy* to look at the system state:
442 docker exec -it PDPD bash -c "/opt/app/policy/bin/telemetry"
443 docker exec -it PDPD bash -c "/opt/app/policy/bin/policy status"
444 docker exec -it PDPD bash -c "/opt/app/policy/bin/db-migrator -s ALL -o report"
446 Controlled instantiation of the PDP-D Control Loop Appplication
447 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
449 Sometimes a developer may want to start and stop the PDP-D manually:
455 docker run --rm -p 9696:9696 -v ${PWD}/config:/tmp/policy-install/config --env-file ${PWD}/env/env.conf -it --name PDPD -h pdpd nexus3.onap.org:10001/onap/policy-pdpd-cl:1.6.4 bash
457 # use this command to start policy applying host customizations from /tmp/policy-install/config
459 pdpd-cl-entrypoint.sh vmboot
461 # or use this command to start policy without host customization
465 # at any time use the following command to stop the PDP-D
469 # and this command to start the PDP-D back again
473 Scale-out use case testing
474 ==========================
476 First step is to create the *operational.scaleout* policy.
484 "type": "onap.policies.controlloop.operational.common.Drools",
485 "type_version": "1.0.0",
486 "name": "operational.scaleout",
489 "policy-id": "operational.scaleout"
492 "id": "ControlLoop-vDNS-6f37f56d-a87d-4b85-b6a9-cc953cf779b3",
495 "trigger": "unique-policy-id-1-scale-up",
498 "id": "unique-policy-id-1-scale-up",
499 "description": "Create a new VF Module",
502 "operation": "VF Module Create",
504 "targetType": "VFMODULE",
506 "modelInvariantId": "e6130d03-56f1-4b0a-9a1d-e1b2ebc30e0e",
507 "modelVersionId": "94b18b1d-cc91-4f43-911a-e6348665f292",
508 "modelName": "VfwclVfwsnkBbefb8ce2bde..base_vfw..module-0",
510 "modelCustomizationId": "47958575-138f-452a-8c8d-d89b595f8164"
514 "requestParameters": "{\"usePreload\":true,\"userParams\":[]}",
515 "configurationParameters": "[{\"ip-addr\":\"$.vf-module-topology.vf-module-parameters.param[9]\",\"oam-ip-addr\":\"$.vf-module-topology.vf-module-parameters.param[16]\",\"enabled\":\"$.vf-module-topology.vf-module-parameters.param[23]\"}]"
520 "success": "final_success",
521 "failure": "final_failure",
522 "failure_timeout": "final_failure_timeout",
523 "failure_retries": "final_failure_retries",
524 "failure_exception": "final_failure_exception",
525 "failure_guard": "final_failure_guard"
531 To provision the *scale-out policy*, issue the following command:
535 http --verify=no -a "${TELEMETRY_USER}:${TELEMETRY_PASSWORD}" https://localhost:9696/policy/pdp/engine/lifecycle/policies @usecases/policy.vdns.json
537 Verify that the policy shows with the telemetry tools:
541 docker exec -it PDPD bash -c "/opt/app/policy/bin/telemetry"
542 > get /policy/pdp/engine/lifecycle/policies
543 > get /policy/pdp/engine/controllers/usecases/drools/facts/usecases/controlloops
552 "closedLoopControlName": "ControlLoop-vDNS-6f37f56d-a87d-4b85-b6a9-cc953cf779b3",
553 "closedLoopAlarmStart": 1463679805324,
554 "closedLoopEventClient": "microservice.stringmatcher",
555 "closedLoopEventStatus": "ONSET",
556 "requestID": "c7c6a4aa-bb61-4a15-b831-ba1472dd4a65",
557 "target_type": "VNF",
558 "target": "vserver.vserver-name",
560 "vserver.is-closed-loop-disabled": "false",
561 "vserver.prov-status": "ACTIVE",
562 "vserver.vserver-name": "OzVServer"
568 To initiate a control loop transaction, simulate a DCAE ONSET to Policy:
572 http --verify=no -a "${TELEMETRY_USER}:${TELEMETRY_PASSWORD}" PUT https://localhost:9696/policy/pdp/engine/topics/sources/noop/DCAE_TOPIC/events @dcae.vdns.onset.json Content-Type:'text/plain'
574 This will trigger the scale out control loop transaction that will interact with the *SO*
575 simulator to complete the transaction.
577 Verify in *$POLICY_LOGS/network.log* that a *FINAL: SUCCESS* notification is sent over the POLICY-CL-MGT channel.
578 An entry in the *$POLICY_LOGS/audit.log* should indicate successful completion as well.
580 vCPE use case testing
581 =====================
583 First step is to create the *operational.restart* policy.
591 "type": "onap.policies.controlloop.operational.common.Drools",
592 "type_version": "1.0.0",
593 "name": "operational.restart",
596 "policy-id": "operational.restart"
599 "id": "ControlLoop-vCPE-48f0c2c3-a172-4192-9ae3-052274181b6e",
602 "trigger": "unique-policy-id-1-restart",
605 "id": "unique-policy-id-1-restart",
606 "description": "Restart the VM",
609 "operation": "Restart",
616 "success": "final_success",
617 "failure": "final_failure",
618 "failure_timeout": "final_failure_timeout",
619 "failure_retries": "final_failure_retries",
620 "failure_exception": "final_failure_exception",
621 "failure_guard": "final_failure_guard"
627 To provision the *operational.restart policy* issue the following command:
631 http --verify=no -a "${TELEMETRY_USER}:${TELEMETRY_PASSWORD}" https://localhost:9696/policy/pdp/engine/lifecycle/policies @usecases/policy.vcpe.json
633 Verify that the policy shows with the telemetry tools:
637 docker exec -it PDPD bash -c "/opt/app/policy/bin/telemetry"
638 > get /policy/pdp/engine/lifecycle/policies
639 > get /policy/pdp/engine/controllers/usecases/drools/facts/usecases/controlloops
648 "closedLoopControlName": "ControlLoop-vCPE-48f0c2c3-a172-4192-9ae3-052274181b6e",
649 "closedLoopAlarmStart": 1463679805324,
650 "closedLoopEventClient": "DCAE_INSTANCE_ID.dcae-tca",
651 "closedLoopEventStatus": "ONSET",
652 "requestID": "664be3d2-6c12-4f4b-a3e7-c349acced200",
653 "target_type": "VNF",
654 "target": "generic-vnf.vnf-id",
656 "vserver.is-closed-loop-disabled": "false",
657 "vserver.prov-status": "ACTIVE",
658 "generic-vnf.vnf-id": "vCPE_Infrastructure_vGMUX_demo_app"
664 To initiate a control loop transaction, simulate a DCAE ONSET to Policy:
668 http --verify=no -a "${TELEMETRY_USER}:${TELEMETRY_PASSWORD}" PUT https://localhost:9696/policy/pdp/engine/topics/sources/noop/DCAE_TOPIC/events @dcae.vcpe.onset.json Content-Type:'text/plain'
670 This will spawn a vCPE control loop transaction in the PDP-D. Policy will send a *restart* message over the
671 *APPC-LCM-READ* channel to APPC and wait for a response.
673 Verify that you see this message in the network.log by looking for *APPC-LCM-READ* messages.
675 Note the *sub-request-id* value from the restart message in the *APPC-LCM-READ* channel.
677 Replace *REPLACEME* in the *appc.vcpe.success.json* with this sub-request-id.
679 appc.vcpe.success.json
680 ~~~~~~~~~~~~~~~~~~~~~~
688 "timestamp": "2017-08-25T21:06:23.037Z",
690 "originator-id": "664be3d2-6c12-4f4b-a3e7-c349acced200",
691 "request-id": "664be3d2-6c12-4f4b-a3e7-c349acced200",
692 "sub-request-id": "REPLACEME",
697 "message": "Restart Successful"
702 "rpc-name": "restart",
703 "correlation-id": "664be3d2-6c12-4f4b-a3e7-c349acced200-1",
708 Send a simulated APPC response back to the PDP-D over the *APPC-LCM-WRITE* channel.
712 http --verify=no -a "${TELEMETRY_USER}:${TELEMETRY_PASSWORD}" PUT https://localhost:9696/policy/pdp/engine/topics/sources/noop/APPC-LCM-WRITE/events @appc.vcpe.success.json Content-Type:'text/plain'
714 Verify in *$POLICY_LOGS/network.log* that a *FINAL: SUCCESS* notification is sent over the *POLICY-CL-MGT* channel,
715 and an entry is added to the *$POLICY_LOGS/audit.log* indicating successful completion.
717 vFirewall use case testing
718 ===========================
720 First step is to create the *operational.modifyconfig* policy.
728 "type": "onap.policies.controlloop.operational.common.Drools",
729 "type_version": "1.0.0",
730 "name": "operational.modifyconfig",
733 "policy-id": "operational.modifyconfig"
736 "id": "ControlLoop-vFirewall-d0a1dfc6-94f5-4fd4-a5b5-4630b438850a",
739 "trigger": "unique-policy-id-1-modifyConfig",
742 "id": "unique-policy-id-1-modifyConfig",
743 "description": "Modify the packet generator",
746 "operation": "ModifyConfig",
750 "resourceID": "bbb3cefd-01c8-413c-9bdd-2b92f9ca3d38"
754 "streams": "{\"active-streams\": 5 }"
759 "success": "final_success",
760 "failure": "final_failure",
761 "failure_timeout": "final_failure_timeout",
762 "failure_retries": "final_failure_retries",
763 "failure_exception": "final_failure_exception",
764 "failure_guard": "final_failure_guard"
771 To provision the *operational.modifyconfig policy*, issue the following command:
775 http --verify=no -a "${TELEMETRY_USER}:${TELEMETRY_PASSWORD}" https://localhost:9696/policy/pdp/engine/lifecycle/policies @usecases/policy.vfw.json
777 Verify that the policy shows with the telemetry tools:
781 docker exec -it PDPD bash -c "/opt/app/policy/bin/telemetry"
782 > get /policy/pdp/engine/lifecycle/policies
783 > get /policy/pdp/engine/controllers/usecases/drools/facts/usecases/controlloops
792 "closedLoopControlName": "ControlLoop-vFirewall-d0a1dfc6-94f5-4fd4-a5b5-4630b438850a",
793 "closedLoopAlarmStart": 1463679805324,
794 "closedLoopEventClient": "microservice.stringmatcher",
795 "closedLoopEventStatus": "ONSET",
796 "requestID": "c7c6a4aa-bb61-4a15-b831-ba1472dd4a65",
797 "target_type": "VNF",
798 "target": "generic-vnf.vnf-name",
800 "vserver.is-closed-loop-disabled": "false",
801 "vserver.prov-status": "ACTIVE",
802 "generic-vnf.vnf-name": "fw0002vm002fw002",
803 "vserver.vserver-name": "OzVServer"
810 To initiate a control loop transaction, simulate a DCAE ONSET to Policy:
814 http --verify=no -a "${TELEMETRY_USER}:${TELEMETRY_PASSWORD}" PUT https://localhost:9696/policy/pdp/engine/topics/sources/noop/DCAE_TOPIC/events @dcae.vfw.onset.json Content-Type:'text/plain'
816 This will spawn a vFW control loop transaction in the PDP-D. Policy will send a *ModifyConfig* message over the
817 *APPC-CL* channel to APPC and wait for a response. This can be seen by searching the network.log for *APPC-CL*.
819 Note the *SubRequestId* field in the *ModifyConfig* message in the *APPC-CL* topic in the network.log
821 Send a simulated APPC response back to the PDP-D over the *APPC-CL* channel.
822 To do this, change the *REPLACEME* text in the *appc.vcpe.success.json* with this *SubRequestId*.
824 appc.vcpe.success.json
825 ~~~~~~~~~~~~~~~~~~~~~~
831 "TimeStamp": 1506051879001,
833 "RequestID": "c7c6a4aa-bb61-4a15-b831-ba1472dd4a65",
834 "SubRequestID": "REPLACEME",
843 "generic-vnf.vnf-id": "f17face5-69cb-4c88-9e0b-7426db7edddd"
849 http --verify=no -a "${TELEMETRY_USER}:${TELEMETRY_PASSWORD}" PUT https://localhost:9696/policy/pdp/engine/topics/sources/noop/APPC-CL/events @appc.vcpe.success.json Content-Type:'text/plain'
851 Verify in *$POLICY_LOGS/network.log* that a *FINAL: SUCCESS* notification is sent over the POLICY-CL-MGT channel,
852 and an entry is added to the *$POLICY_LOGS/audit.log* indicating successful completion.
855 Running PDP-D Control Loop Application with other components
856 ============================================================
858 The reader can also look at the `policy/docker repository <https://github.com/onap/policy-docker/tree/master/csit>`__.
859 More specifically, these directories have examples of other PDP-D Control Loop configurations:
861 * `plans <https://github.com/onap/policy-docker/tree/master/csit/drools-pdp/plans>`__: startup scripts.
862 * `tests <https://github.com/onap/policy-docker/tree/master/csit/drools-pdp/tests>`__: test plan.
864 Additional information
865 ======================
867 For additional information, please see the
868 `Drools PDP Development and Testing (In Depth) <https://wiki.onap.org/display/DW/2020+Frankfurt+Tutorials>`__ page.