aboutsummaryrefslogtreecommitdiffstats
path: root/docs/installation
diff options
context:
space:
mode:
authorramagp <ramakrishnagp@aarnanetworks.com>2020-10-17 17:53:25 +0000
committerramagp <ramakrishnagp@aarnanetworks.com>2020-10-17 17:53:48 +0000
commita0fa153cdb11be9d75d79a43183e4aac80124615 (patch)
treebf89dd9147a3db7203e07577569a4a7a243050e4 /docs/installation
parent9f9c7426dcbc31279644fa704f6349e77bcf5b05 (diff)
Addressing review comments
Change-Id: Ice9bff30b6e9223546b76fc9f56ce13f8faeeac6 Issue-ID: POLICY-2868 Signed-off-by: ramagp <ramakrishnagp@aarnanetworks.com>
Diffstat (limited to 'docs/installation')
-rw-r--r--docs/installation/oom.rst54
1 files changed, 19 insertions, 35 deletions
diff --git a/docs/installation/oom.rst b/docs/installation/oom.rst
index 1170e4a8..fda154de 100644
--- a/docs/installation/oom.rst
+++ b/docs/installation/oom.rst
@@ -21,37 +21,18 @@ To get a listing of the Policy Pods, run the following command:
.. code-block:: bash
- kubectl get pods | grep policy
-
- brmsgw ClusterIP 10.43.77.177 <none> 9989/TCP 5d15h app=brmsgw,release=dev-policy
- drools ClusterIP 10.43.167.154 <none> 6969/TCP,9696/TCP 5d15h app=drools,release=dev-policy
- nexus ClusterIP 10.43.239.92 <none> 8081/TCP 5d15h app=nexus,release=dev-policy
- pap NodePort 10.43.207.229 <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 10.43.226.0 <none> 6969/TCP 5d15h app=policy-apex-pdp,release=dev-policy
- policy-api ClusterIP 10.43.102.56 <none> 6969/TCP 5d15h app=policy-api,release=dev-policy
- policy-distribution ClusterIP 10.43.4.211 <none> 6969/TCP 5d15h app=policy-distribution,release=dev-policy
- policy-pap ClusterIP 10.43.175.164 <none> 6969/TCP 5d15h app=policy-pap,release=dev-policy
- policy-xacml-pdp ClusterIP 10.43.181.208 <none> 6969/TCP 5d15h app=policy-xacml-pdp,release=dev-policy
- policydb ClusterIP 10.43.93.233 <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.
-
-.. csv-table::
- :header: "Policy Pod", "Latest Framework", "Legacy"
- :widths: 15,10,10
-
- "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"
+ kubectl get pods -n onap | grep dev-policy
+
+ dev-policy-59684c7b9c-5gd6r 2/2 Running 0 8m41s
+ dev-policy-apex-pdp-0 1/1 Running 0 8m41s
+ dev-policy-api-56f55f59c5-nl5cg 1/1 Running 0 8m41s
+ dev-policy-distribution-54cc59b8bd-jkg5d 1/1 Running 0 8m41s
+ dev-policy-mariadb-0 1/1 Running 0 8m41s
+ dev-policy-xacml-pdp-765c7d58b5-l6pr7 1/1 Running 0 8m41s
+
+.. note::
+ To get a listing of the Policy services, run this command:
+ kubectl get svc -n onap | grep policy
Accessing Policy Containers
***************************
@@ -74,7 +55,10 @@ From your local copy, edit any of the values.yaml files in the policy tree to ma
.. code-block:: bash
make policy
- make onap
+ make SKIP_LINT=TRUE onap
+
+.. note::
+ SKIP_LINT is only to reduce the "make" time
**Step 3** Undeploy Policy
After undeploying policy, loop on monitoring the policy pods until they go away.
@@ -82,13 +66,13 @@ After undeploying policy, loop on monitoring the policy pods until they go away.
.. code-block:: bash
helm del --purge dev-policy
- kubectl get pods -n onap
+ kubectl get pods -n onap | grep dev-policy
**Step 4** Delete NFS persisted data for Policy
.. code-block:: bash
- rm -fr /dockerdata-nfs/dev-policy
+ rm -fr /dockerdata-nfs/dev/policy
**Step 5** Make sure there is no orphan policy database persistent volume or claim.
@@ -113,7 +97,7 @@ After deploying policy, loop on monitoring the policy pods until they come up.
.. code-block:: bash
helm deploy dev-policy local/onap --namespace onap
- kubectl get pods -n onap
+ kubectl get pods -n onap | grep dev-policy
Restarting a faulty component
*****************************