aboutsummaryrefslogtreecommitdiffstats
path: root/docs/release/configguide/postinstall.rst
diff options
context:
space:
mode:
authorramamani yeleswarapu <ramamani.yeleswarapu@intel.com>2017-12-13 11:46:05 -0800
committerMaryam Tahhan <maryam.tahhan@intel.com>2017-12-14 10:29:02 +0000
commitc8fb69defcc4f33371827a2889910b940fe70123 (patch)
treea8d87661bfde7cfba79806b05140732ff680418b /docs/release/configguide/postinstall.rst
parentf04e17c162ed39fed95b3823ca106d195ee62342 (diff)
docs: Adding Compass4nfv installer support details
The following two files have been updated with info on deploying Barometer with Compass4nfv installer: docs/release/configguide/featureconfig.rst docs/release/configguide/postinstall.rst Change-Id: I99364b2e08afeee51407020149677c249ed75484 Signed-off-by: Ramamani Yeleswarapu <ramamani.yeleswarapu@intel.com>
Diffstat (limited to 'docs/release/configguide/postinstall.rst')
-rw-r--r--docs/release/configguide/postinstall.rst43
1 files changed, 41 insertions, 2 deletions
diff --git a/docs/release/configguide/postinstall.rst b/docs/release/configguide/postinstall.rst
index 45a79ff..7ec047d 100644
--- a/docs/release/configguide/postinstall.rst
+++ b/docs/release/configguide/postinstall.rst
@@ -21,8 +21,8 @@ is controlled as described in the User Guide through their individual ``.conf``
the ``/etc/collectd/collectd.conf.d/`` folder on the compute node(s). In order for any changes to
take effect, the collectd service must be stopped and then started again.
-Platform components validation
-------------------------------
+Platform components validation - Apex
+-------------------------------------
The following steps describe how to perform a simple "manual" testing of the Barometer components:
1. Connect to any compute node and ensure that the collectd service is running. The log file
@@ -98,3 +98,42 @@ The following steps describe how to perform a simple "manual" testing of the Bar
| fbd06539-45dd-42c5-a991-5c5dbf679730 | event | gauge.memory_erros(overcloud-novacompute-0.jf.intel.com-mcelog) | ok | moderate | True |
| d73251a5-1c4e-4f16-bd3d-377dd1e8cdbe | event | gauge.mcelog_status(overcloud-novacompute-0.jf.intel.com-mcelog) | ok | moderate | True |
[...]
+
+
+Platform components validation - Compass4nfv
+--------------------------------------------
+
+The procedure is similar to the above.
+
+The following steps describe how to perform a simple "manual" testing of the Barometer components:
+
+On the compute:
+
+1. Connect to any compute node and ensure that the collectd service is running. The log file
+ ``collectd.log`` should contain no errors and should indicate that each plugin was successfully
+ loaded. For example, ssh into a compute node and test:
+
+ .. code:: bash
+
+ $ ls /etc/collectd/collectd.conf.d/
+ $ systemctl status collectd
+ $ vi /var/log/collectd.log
+
+ The following plugings should be found loaded:
+ aodh, gnocchi, hugepages, mcelog, ovs_events, ovs_stats, cpu, interface, memory, disk, numa, virt, rrdtool
+
+2. Testing using mce-inject is similar to #2 shown above.
+
+On the controller:
+
+3. Connect to the controller and query the monitoring services. Make sure to log in to the lxc-utility
+container before using the OpenStack CLI. Please refer to this wiki for details:
+https://wiki.opnfv.org/display/compass4nfv/Containerized+Compass#ContainerizedCompass-HowtouseOpenStackCLI
+
+ .. code:: bash
+
+ $ source ~/openrc
+ $ gnocchi metric list
+ $ aodh alarm list
+
+ The output for the gnocchi and aodh queries should be similar to the excerpts shown in #3 above.