summaryrefslogtreecommitdiffstats
path: root/docs/sections/services/pm-subscription-handler/installation.rst
diff options
context:
space:
mode:
authorTony Hansen <tony@att.com>2021-03-03 16:32:04 +0000
committerTony Hansen <tony@att.com>2021-03-03 16:32:04 +0000
commitc1e9c2f17ce8a9800e3a8b22068411258989d7ea (patch)
treef6823c8aac6d3ea63cebe43b7f162751dc75956f /docs/sections/services/pm-subscription-handler/installation.rst
parent6132c206cc4a64df2248647326d569393605cf90 (diff)
Revert "[PMSH] Add doc updates for update sub use case"
This reverts commit 6132c206cc4a64df2248647326d569393605cf90. Reason for revert: Container not ready; functionality deferred to I release Issue-ID: DCAEGEN2-2653 Issue-ID: DCAEGEN2-2152 Change-Id: I2ed41ce31d0b4e02e8e8a2faaffaef412d61b6d7 Signed-off-by: Tony Hansen <th1395@att.com>;
Diffstat (limited to 'docs/sections/services/pm-subscription-handler/installation.rst')
-rw-r--r--docs/sections/services/pm-subscription-handler/installation.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/sections/services/pm-subscription-handler/installation.rst b/docs/sections/services/pm-subscription-handler/installation.rst
index 4cc0d833..ea55256a 100644
--- a/docs/sections/services/pm-subscription-handler/installation.rst
+++ b/docs/sections/services/pm-subscription-handler/installation.rst
@@ -6,7 +6,7 @@
Installation
============
-The PMSH microservice can be deployed using the DCAE Dashboard or via CLI. Steps to deploy using CLI will be shown
+In Guilin, the PMSH can be deployed using the DCAE Dashboard or via CLI. Steps to deploy using CLI will be shown
below.
Deployment Prerequisites
@@ -21,7 +21,7 @@ As well as this, the following components are required to be running. They can b
- A&AI
- AAF
-The robot healthcheck test suite can be run from the local OOM repository.
+The robot healthcheck can be run from one of the Kubernetes controllers.
.. code-block:: bash
@@ -30,7 +30,7 @@ The robot healthcheck test suite can be run from the local OOM repository.
Deployment Procedure
^^^^^^^^^^^^^^^^^^^^
-To deploy the PMSH, the monitoring policy needs to be pushed directly to CONSUL.
+To deploy the PMSH in the Frankfurt release, the monitoring policy needs to be pushed directly to CONSUL.
To begin, kubectl exec on to the dcae-bootstrap pod and move to the /tmp directory.
.. code-block:: bash