openstack/openstack-manuals
Code Issues Proposed changes

Update Telemetry Admin Guide

Browse Source 
Add description of alarm workload partitioning that was introduced in this
patch: https://review.openstack.org/#/c/115237/9

Closes-Bug: #1364807
Change-Id: I5659b6dc9afd5af322b92247ced0a368f152a045
This commit is contained in:
Ildiko Vancsa 2014-11-18 12:50:28 +01:00
parent 902b08d560
commit 3564314d48
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml
View File

@ -74,6 +74,24 @@
<para>These are a lightweight alternative to webhooks, whereby the state transition is simply logged by the <systemitem class="service">alarm-notifier</systemitem>, and are intended primarily for testing purposes.</para>
</section>
</section>
<section xml:id="section_telemetry-alarm-workload-partitioning">
<title>Workload partitioning</title>
<para>The alarm evaluation process uses the same mechanism for
workload partitioning as the central and compute agents.
The <link xlink:href="https://pypi.python.org/pypi/tooz">
Tooz</link> library provides the coordination within the
groups of service instances. For further information
about this approach see
<xref linkend="section_telemetry-cetral-compute-agent-ha"/>.
</para>
<para>To use this workload partitioning solution set the
<option>evaluation_service</option> option to <literal>
default</literal>. For more information, see the alarm
section in the
<link xlink:href="http://docs.openstack.org/trunk/config-reference/content/ch_configuring-openstack-telemetry.html">
<citetitle>OpenStack Configuration Reference</citetitle></link>.
</para>
</section>
</section>
<section xml:id="section_telemetry-alarm-usage">
<title>Using alarms</title>