From 3564314d48306a2e3d0b4464017b05b94e442f9a Mon Sep 17 00:00:00 2001 From: Ildiko Vancsa Date: Tue, 18 Nov 2014 12:50:28 +0100 Subject: [PATCH] Update Telemetry Admin Guide 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 --- .../telemetry/section_telemetry-alarms.xml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml b/doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml index 5495acc0d0..5b339caaaf 100644 --- a/doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml +++ b/doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml @@ -74,6 +74,24 @@ These are a lightweight alternative to webhooks, whereby the state transition is simply logged by the alarm-notifier, and are intended primarily for testing purposes. +
+ Workload partitioning + The alarm evaluation process uses the same mechanism for + workload partitioning as the central and compute agents. + The + Tooz library provides the coordination within the + groups of service instances. For further information + about this approach see + . + + To use this workload partitioning solution set the + option to + default. For more information, see the alarm + section in the + + OpenStack Configuration Reference. + +
Using alarms