summaryrefslogtreecommitdiffstats
path: root/docs/sections/services/pm-subscription-handler/installation.rst
diff options
context:
space:
mode:
authorVijay Venkatesh Kumar <vv770d@att.com>2020-04-28 20:27:46 +0000
committerGerrit Code Review <gerrit@onap.org>2020-04-28 20:27:46 +0000
commitb9245647657dfcde55315667c911130155b9dc1e (patch)
tree4a4cd18a3c2cdbaf57d4946f8e078ee6bc3d0bda /docs/sections/services/pm-subscription-handler/installation.rst
parent0424f6f58b83ced065a0f49fdafa3e50bff18f1e (diff)
parentcc62d2ee6ac4f016c0759051b5564e696e4fbc2f (diff)
Merge "Update PMSH Frankfurt docs"
Diffstat (limited to 'docs/sections/services/pm-subscription-handler/installation.rst')
-rw-r--r--docs/sections/services/pm-subscription-handler/installation.rst9
1 files changed, 7 insertions, 2 deletions
diff --git a/docs/sections/services/pm-subscription-handler/installation.rst b/docs/sections/services/pm-subscription-handler/installation.rst
index 3865cfbd..f858222a 100644
--- a/docs/sections/services/pm-subscription-handler/installation.rst
+++ b/docs/sections/services/pm-subscription-handler/installation.rst
@@ -6,8 +6,8 @@
Installation
============
-Due to a bug in the Frankfurt release, the PMSH cannot be deployed through CLAMP. The PMSH can instead be deployed
-using the DCAE Dashboard or via CLI. Steps to deploy using CLI will be shown below.
+In Frankfurt, the PMSH can be deployed using the DCAE Dashboard or via CLI. Steps to deploy using CLI will be shown
+below.
Deployment Prerequisites
^^^^^^^^^^^^^^^^^^^^^^^^
@@ -46,6 +46,11 @@ See :ref:`Subscription configuration<Subscription>`
-H 'Content-Type: application/json' \
-d @monitoring-policy.json
+The following JSON is an example monitoring policy.
+
+.. literalinclude:: resources/monitoring-policy.json
+ :language: json
+
To deploy the PMSH microservice using the deployment handler API, the ``serviceTypeId`` is needed, this can be retrieved
using the inventory API