diff options
| -rw-r--r-- | docs/sections/healthcheck.rst | 6 | ||||
| -rw-r--r-- | docs/sections/installation_test.rst | 11 |
2 files changed, 13 insertions, 4 deletions
diff --git a/docs/sections/healthcheck.rst b/docs/sections/healthcheck.rst index f7fcba15..b85a1dea 100644 --- a/docs/sections/healthcheck.rst +++ b/docs/sections/healthcheck.rst @@ -26,6 +26,12 @@ blueprints after the initial DCAE installation. The healthcheck service is exposed as a Kubernetes ClusterIP Service named `dcae-healthcheck`. The service can be queried for status as shown below. +.. note:: + Run the below commands before running "curl dcae-healthcheck" + + * To get the dcae-healthcheck pod name, run this: kubectl get pods -n onap | grep dcae-healthcheck + * Then enter in to the shell of the container, run this: kubectl exec -it <dcae-healthcheck pod> -n onap bash + .. code-block:: json $ curl dcae-healthcheck diff --git a/docs/sections/installation_test.rst b/docs/sections/installation_test.rst index 2d2f357d..1c36bf37 100644 --- a/docs/sections/installation_test.rst +++ b/docs/sections/installation_test.rst @@ -99,17 +99,20 @@ After the platform is assessed as healthy, the next step is to check the functio kubectl logs -f -n onap <vescollectorpod> dcae-ves-collector +.. note:: + To get the "vescollectorpod" run this command: kubectl -n onap get pods | grep dcae-ves-collector + 2. Check VES Output VES publishes received VNF data, after authentication and syntax check, onto DMaaP Message Router. To check this is happening we can subscribe to the publishing topic. - 1. Run the subscription command to subscribe to the topic: **curl -H "Content-Type:text/plain" -X GET http://{{K8S_NODEIP}}:30227/events/unauthenticated.VES_MEASUREMENT_OUTPUT/group1/C1?timeout=50000**. The actual format and use of Message Router API can be found in DMaaP project documentation. + 1. Run the subscription command to subscribe to the topic: **curl -H "Content-Type:text/plain" -k -X GET https://{{K8S_NODEIP}}:30226/events/unauthenticated.VES_MEASUREMENT_OUTPUT/group1/C1?timeout=50000**. The actual format and use of Message Router API can be found in DMaaP project documentation. * When there are messages being published, this command returns with the JSON array of messages; * If no message being published, up to the timeout value (i.e. 50000 seconds as in the example above), the call is returned with empty JAON array; - * It may be useful to run this command in a loop: **while :; do curl -H "Content-Type:text/plain" -X GET http://{{K8S_NODEIP}}:3904/events/unauthenticated.VES_MEASUREMENT_OUTPUT/group1/C1?timeout=50000; echo; done**; + * It may be useful to run this command in a loop: **while :; do curl -H "Content-Type:text/plain" -k -X GET https://{{K8S_NODEIP}}:30226/events/unauthenticated.VES_MEASUREMENT_OUTPUT/group1/C1?timeout=50000; echo; done**; 3. Check TCA Output TCA also publishes its events to Message Router under the topic of "unauthenticated.DCAE_CL_OUTPUT". The same Message Router subscription command can be used for checking the messages being published by TCA; - * Run the subscription command to subscribe to the topic: **curl -H "Content-Type:text/plain" -X GET http://{{K8S_NODEIP}}:3904/events/unauthenticated.DCAE_CL_OUTPUT/group1/C1?timeout=50000**. - * Or run the command in a loop: **while :; do curl -H "Content-Type:text/plain" -X GET http://{{K8S_NODEIP}}:3904/events/unauthenticated.DCAE_CL_OUTPUT/group1/C1?timeout=50000; echo; done**; + * Run the subscription command to subscribe to the topic: **curl -H "Content-Type:text/plain" -k -X GET https://{{K8S_NODEIP}}:30226/events/unauthenticated.DCAE_CL_OUTPUT/group1/C1?timeout=50000**. + * Or run the command in a loop: **while :; do curl -H "Content-Type:text/plain" -k -X GET https://{{K8S_NODEIP}}:30226/events/unauthenticated.DCAE_CL_OUTPUT/group1/C1?timeout=50000; echo; done**; |