Merge "change to section_telemetry-data-collection"

This commit is contained in:
Jenkins 2015-03-24 08:55:26 +00:00 committed by Gerrit Code Review
commit af556495ee

View File

@ -341,20 +341,20 @@
agent requires an IPMI capable node with <application>ipmitool</application> installed, which
is a common utility for IPMI control on various Linux distributions.</para>
<para>An IPMI agent instance could be installed on each and every compute node
with IPMI support, except when the node is managed by Bare metal module for OpenStack
with IPMI support, except when the node is managed by the Bare metal module for OpenStack
and the <option>conductor.send_sensor_data</option> option is set to <literal>true</literal>
in the Bare metal module for OpenStack.
It is no harm to install this agent on compute node without IPMI or Intel Node
It is no harm to install this agent on a compute node without IPMI or Intel Node
Manager support, as the agent checks for the hardware and if none is available, returns empty data.
But it is suggested that you install IPMI agent only on IPMI capable node for performance reason.
It is suggested that you install the IPMI agent only on an IPMI capable node for performance reasons.
</para>
<para>Just like the central agent, this component also does not need a direct database
<para>Just like the central agent, this component also does not need direct database
access. The samples are sent via AMQP to the collector.
</para>
<para>The list of collected meters can be found in <xref linkend=
"section_telemetry-ironic-metrics"/>.</para>
<note>
<para>Do not deploy both IPMI agent and Bare metal module for OpenStack on
<para>Do not deploy both the IPMI agent and the Bare metal module for OpenStack on
one compute node. If <option>conductor.send_sensor_data</option> set, this
misconfiguration causes duplicated IPMI sensor samples.
</para>