diff options
| author |   Hansen, Tony (th1395) <th1395@att.com> | 2023-05-23 21:27:17 +0000 |
|---|---|---|
| committer | Hansen, Tony (th1395) <th1395@att.com> | 2023-05-31 21:01:29 +0000 |
| commit | 663df2c1b8d9176094a62b00b7e80de096180621 (patch) | |
| tree | 849841dc428fcfba07d9c39494f95ccd1f25da8a /docs/sections/installation_test.rst | |
| parent | bcd436a1be4fbe2c8ad7ce074d86b94b8ff44f4e (diff) | |
clean up some sphinx warnings
Change-Id: I8c2d925e8b27b4740227af0be3ab5d6f7153ec38
Signed-off-by: Hansen, Tony (th1395) <th1395@att.com>
Issue-ID: DCAEGEN2-3399
Signed-off-by: Hansen, Tony (th1395) <th1395@att.com>
Signed-off-by: Vijay Venkatesh Kumar <vv770d@att.com>
Signed-off-by: Hansen, Tony (th1395) <th1395@att.com>
Diffstat (limited to 'docs/sections/installation_test.rst')
| -rw-r--r-- | docs/sections/installation_test.rst | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/docs/sections/installation_test.rst b/docs/sections/installation_test.rst index 1062f526..3bfbb03b 100644 --- a/docs/sections/installation_test.rst +++ b/docs/sections/installation_test.rst @@ -1,3 +1,7 @@ +.. This work is licensed under a + Creative Commons Attribution 4.0 International License. + http://creativecommons.org/licenses/by/4.0 + DCAE Deployment Validation ========================== @@ -8,7 +12,7 @@ Check Deployment Status The healthcheck service is exposed as a Kubernetes ClusterIP Service named `dcae-ms-healthcheck`. The service can be queried for status as shown below. -.. code-block:: json +.. code-block:: bash $ curl dcae-ms-healthcheck { @@ -19,7 +23,7 @@ The healthcheck service is exposed as a Kubernetes ClusterIP Service named "name": "onap-dcae-hv-ves-collector", "ready": 1, "unavailable": 0 - }, + }, { "name": "onap-dcae-prh", "ready": 1, @@ -50,8 +54,8 @@ Data Flow Verification After the platform is assessed as healthy, the next step is to check the functionality of the system. This can be monitored at a number of "observation" points. -1. Incoming VNF Data into VES Collector can be verified through logs using kubectl - +1. Incoming VNF Data into VES Collector can be verified through logs using kubectl + kubectl logs -f -n onap <vescollectorpod> dcae-ves-collector .. note:: @@ -70,4 +74,3 @@ After the platform is assessed as healthy, the next step is to check the functio 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" -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**; - |