1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
2 .. http://creativecommons.org/licenses/by/4.0
4 Barometer post installation procedures
5 ======================================
6 Add a brief introduction to the methods of validating the installation
7 according to this specific installer or feature.
9 Automated post installation activities
10 --------------------------------------
11 Describe specific post installation activities performed by the OPNFV
12 deployment pipeline including testing activities and reports. Refer to
13 the relevant testing guides, results, and release notes.
15 note: this section should be singular and derived from the test projects
16 once we have one test suite to run for all deploy tools. This is not the
17 case yet so each deploy tool will need to provide (hopefully very simillar)
18 documentation of this.
20 Barometer post configuration procedures
21 --------------------------------------
22 The fuel plugin installs collectd and its plugins on compute nodes.
23 separate config files for each of the collectd plugins. These
24 configuration files can be found on the compute node @
25 `/etc/collectd/collectd.conf.d/` directory. Each collectd plugin will
26 have its own configuration file with a default configuration for each
27 plugin. You can override any of the plugin configurations, by modifying
28 the configuration file and restarting the collectd service on the compute node.
30 Platform components validation
31 ---------------------------------
32 1. SSH to a compute node and ensure that the collectd service is running.
34 2. On the compute node, you need to inject a corrected memory error:
38 $ git clone https://git.kernel.org/pub/scm/utils/cpu/mce/mce-inject.git
43 Modify the test/corrected script to include the following:
48 STATUS 0xcc00008000010090
55 $ ./mce-inject < test/corrected
57 3. SSH to openstack controller node and query the ceilometer DB:
62 $ ceilometer sample-list -m interface.if_packets
63 $ ceilometer sample-list -m hugepages.vmpage_number
64 $ ceilometer sample-list -m ovs_events.gauge
65 $ ceilometer sample-list -m mcelog.errors
67 As you run each command above, you should see output similar to the examples below:
70 | node-6.domain.tld-br-prv-link_status | ovs_events.gauge | gauge | 1.0 | None | 2017-01-20T18:18:40 |
71 | node-6.domain.tld-int-br-prv-link_status | ovs_events.gauge | gauge | 1.0 | None | 2017-01-20T18:18:39 |
72 | node-6.domain.tld-br-int-link_status | ovs_events.gauge | gauge | 0.0 | None | 2017-01-20T18:18:39 |
74 | node-6.domain.tld-mm-2048Kb-free | hugepages.vmpage_number | gauge | 0.0 | None | 2017-01-20T18:17:12 |
75 | node-6.domain.tld-mm-2048Kb-used | hugepages.vmpage_number | gauge | 0.0 | None | 2017-01-20T18:17:12 |
76 +-------------------------------------+-------------------------+-------+--------+------+---------------------+
78 | bf05daca-df41-11e6-b097-5254006ed58e | node-6.domain.tld-SOCKET_0_CHANNEL_0_DIMM_any-uncorrected_memory_errors_in_24h | mcelog.errors | gauge | 0.0 | None | 2017-01-20T18:53:34 |
79 | bf05dacb-df41-11e6-b097-5254006ed58e | node-6.domain.tld-SOCKET_0_CHANNEL_any_DIMM_any-uncorrected_memory_errors_in_24h | mcelog.errors | gauge | 0.0 | None | 2017-01-20T18:53:34 |
80 | bdcb930d-df41-11e6-b097-5254006ed58e | node-6.domain.tld-SOCKET_0_CHANNEL_any_DIMM_any-uncorrected_memory_errors | mcelog.errors | gauge | 0.0 | None | 2017-01-20T18:53:33 |