1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
2 .. http://creativecommons.org/licenses/by/4.0
9 Due to a bug in the Frankfurt release, the PMSH cannot be deployed through CLAMP. The PMSH can instead be deployed
10 using the DCAE Dashboard or via CLI. Steps to deploy using CLI will be shown below.
12 Deployment Prerequisites
13 ^^^^^^^^^^^^^^^^^^^^^^^^
15 In order to successfully deploy the PMSH, one will need administrator access to the kubernetes cluster, as a service
16 will need to be exposed. As well as this, the following components are required to be running. They can be verified by
17 running the health checks.
24 The healthcheck can be run from one of the Kubernetes controllers.
28 ./oom/kubernetes/robot/ete-k8s.sh onap health
33 To deploy the PMSH in the Frankfurt release, the monitoring policy needs to be pushed directly to CONSUL. The CONSUL
34 service must first be exposed.
38 kubectl expose svc -n onap consul-server-ui --name=x-consul-server-ui --type=NodePort
40 The monitoring policy can then be pushed with the following request, for information on creating a monitoring policy see
41 See :ref:`Subscription configuration<Subscription>`
45 curl -X PUT http://<k8s-node-ip>:<consul-port>/v1/kv/dcae-pmsh:policy \
46 -H 'Content-Type: application/json' \
47 -d @monitoring-policy.json
49 To deploy the PMSH microservice using the deployment handler API, the ``serviceTypeId`` is needed, this can be retrieved
50 using the inventory API
54 curl https://<k8s-node-ip>:<inventory-port>/dcae-service-types
56 The ``serviceTypeId`` for the PMSH can be found under typeID. The PMSH can then be deployed.
60 curl https://<k8s-node-ip>:<dep-handler-port>/dcae-deployments/dcae-pmsh \
61 -H 'Content-Type: application/json' \
64 "serviceTypeId": "<typeId>"