Policy OOM Installation

Policy OOM Charts

The policy K8S charts are located in the OOM repository.

Please refer to the OOM documentation on how to install and deploy ONAP.

Policy Pods

To get a listing of the Policy Pods, run the following command:

kubectl get pods | grep policy

brmsgw                     ClusterIP    <none>        9989/TCP                              5d15h   app=brmsgw,release=dev-policy
drools                     ClusterIP   <none>        6969/TCP,9696/TCP                     5d15h   app=drools,release=dev-policy
nexus                      ClusterIP    <none>        8081/TCP                              5d15h   app=nexus,release=dev-policy
pap                        NodePort   <none>        8443:30219/TCP,9091:30218/TCP         5d15h   app=pap,release=dev-policy
pdp                        ClusterIP   None            <none>        8081/TCP                              5d15h   app=pdp,release=dev-policy
policy-apex-pdp            ClusterIP     <none>        6969/TCP                              5d15h   app=policy-apex-pdp,release=dev-policy
policy-api                 ClusterIP    <none>        6969/TCP                              5d15h   app=policy-api,release=dev-policy
policy-distribution        ClusterIP     <none>        6969/TCP                              5d15h   app=policy-distribution,release=dev-policy
policy-pap                 ClusterIP   <none>        6969/TCP                              5d15h   app=policy-pap,release=dev-policy
policy-xacml-pdp           ClusterIP   <none>        6969/TCP                              5d15h   app=policy-xacml-pdp,release=dev-policy
policydb                   ClusterIP    <none>        3306/TCP                              5d15h   app=policydb,release=dev-policy

Some of these pods are shared between the legacy components and the latest framework components, while others are not.

Policy Pod Latest Framework Legacy
brmsgw   yes
drools yes yes
nexus yes yes
pap   yes
pdp   yes
policy-apex-pdp yes  
policy-api yes  
policy-distribution yes yes
policy-pap yes  
policy-xacml-pdp yes  
policydb yes yes

Accessing Policy Containers

Accessing the policy docker containers is the same as for any kubernetes container. Here is an example:

kubectl -n onap exec -it dev-policy-policy-xacml-pdp-584844b8cf-9zptx bash

Rebuilding and/or modifying the Policy Charts

The assumption is you have cloned the charts from the OOM repository into a local directory.

Step 1 Go into local copy of OOM charts

From your local copy, edit any of the values.yaml files in the policy tree to make desired changes.

Step 2 Build the charts

make policy
make onap

Step 3 Undeploy Policy After undeploying policy, loop on monitoring the policy pods until they go away.

helm del --purge dev-policy
kubectl get pods -n onap

Step 4 Delete NFS persisted data for Policy Sudo to root if you logged in using another account such as ubuntu.

rm -fr /dockerdata-nfs/dev-policy

Step 5 Re-Deploy Policy pods After deploying policy, loop on monitoring the policy pods until they come up.

helm deploy dev-policy local/onap --namespace onap
kubectl get pods -n onap

Exposing ports

For security reasons, the ports for the policy containers are configured as ClusterIP and thus not exposed. If you find you need those ports in a development environment, then the following will expose them.

kubectl -n onap expose service policy-api --port=7171 --target-port=6969 --name=api-public --type=NodePort

Customizing PDP-D Installations

Credentials and other configuration parameters can be set as values when deploying the policy (drools) subchart. Please refer to PDP-D Default Values for the current default values. It is strongly recommended that sensitive information is secured appropriately before using in production.

Additional customization can be applied to the PDP-D. Custom configuration goes under the “resources” directory of the drools subchart (oom/kubernetes/policy/charts/drools/resources). This requires rebuilding the policy subchart (see section Rebuilding and/or modifying the Policy Charts).

Configuration is done by adding or modifying configmaps and/or secrets. Configmaps are placed under “drools/resources/configmaps”, and secrets under “drools/resources/secrets”.

Custom configuration supportes these types of files:

  • *.conf files to support additional environment configuration.
  • features*.zip to add additional custom features.
  • *.pre.sh scripts to be executed before starting the PDP-D process.
  • *.post.sh scripts to be executed after starting the PDP-D process.
  • policy-keystore to override the PDP-D policy-keystore.
  • policy-truststore to override the PDP-D policy-truststore.
  • aaf-cadi.keyfile to override the PDP-D AAF key.
  • *.properties to override or add properties files.


To disable AAF, simply override the “aaf.enabled” value when deploying the helm chart (see the OOM installation instructions mentioned above).

To override the PDP-D keystore or trustore, add a suitable replacement(s) under “drools/resources/secrets”. Modify the drools chart values.yaml with new credentials, and follow the procedures described at Rebuilding and/or modifying the Policy Charts to redeploy the chart.

To disable https for the DMaaP configuration topic, add a copy of engine.properties with “dmaap.source.topics.PDPD-CONFIGURATION.https” set to “false”, or alternatively create a “.pre.sh” script (see above) that edits this file before the PDP-D is started.