summaryrefslogtreecommitdiffstats
path: root/docs/sections/installation_test.rst
diff options
context:
space:
mode:
authorLusheng Ji <lji@research.att.com>2017-11-22 00:38:22 -0500
committerLusheng Ji <lji@research.att.com>2017-11-22 00:52:57 -0500
commitc5e0375e36c4acab3d81855a0c438dc5a2c86bad (patch)
tree8d2509f85a90c56ca022e50507101c6764e0ac35 /docs/sections/installation_test.rst
parentc02a89f5f38ad111b3808517db5629b8c28b63f0 (diff)
Fix section titles, add more doc
Issue-ID: DCAEGEN2-199 Change-Id: I4b489a604fcdef9fc57eab92ad7c1cecd6b843f4 Signed-off-by: Lusheng Ji <lji@research.att.com>
Diffstat (limited to 'docs/sections/installation_test.rst')
-rw-r--r--docs/sections/installation_test.rst5
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/sections/installation_test.rst b/docs/sections/installation_test.rst
index 641a8616..83d4c8e3 100644
--- a/docs/sections/installation_test.rst
+++ b/docs/sections/installation_test.rst
@@ -3,7 +3,7 @@ Testing and Debugging ONAP DCAE Deployment
Check Component Status
-======================
+----------------------
Testing of a DCAE system starts with checking the health of the deployed components. This can be done by accessing the Consul becsue all DCAE components register their staus with Consul. Such API is accessible at http://{{ANY_CONSUL_VM_IP}}:8500.
@@ -22,7 +22,8 @@ In addition, more details status information can be obtained in additional ways.
Check data Flow
-===============
+---------------
+
After the platform is assessed as heathy, the next step is to check the functionality of the system. This can be monitored at a number of "observation" points.
1. Check incoming VNF Data