openstack/aodh
Code Issues Proposed changes

Merge "fix partitioning documentation"

Browse Source
This commit is contained in:
Zuul 2018-01-30 19:17:26 +00:00 committed by Gerrit Code Review
commit 49bde26207
2 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
aodh/coordination.py
View File

@ -29,10 +29,9 @@ LOG = log.getLogger(__name__)
OPTS = [ OPTS = [
cfg.StrOpt('backend_url', cfg.StrOpt('backend_url',
help='The backend URL to use for distributed coordination. If ' help='The backend URL to use for distributed coordination. If '
'left empty, per-deployment central agent and per-host ' 'left empty, alarm evaluation won\'t do workload '
'compute agent won\'t do workload '
'partitioning and will only function correctly if a ' 'partitioning and will only function correctly if a '
'single instance of that service is running.'), 'single instance of the service is running.'),
cfg.FloatOpt('heartbeat', cfg.FloatOpt('heartbeat',
default=1.0, default=1.0,
help='Number of seconds between heartbeats for distributed ' help='Number of seconds between heartbeats for distributed '

4
doc/source/admin/telemetry-alarms.rst
View File

@ -108,8 +108,8 @@ intended primarily for testing purposes.
Workload partitioning Workload partitioning
--------------------- ---------------------
The alarm evaluation process uses the same mechanism for workload The alarm evaluation process can be scaled horizontally but requires
partitioning as the central and compute agents. The workload partitioning to function correctly. The
`Tooz <https://pypi.python.org/pypi/tooz>`_ library provides the `Tooz <https://pypi.python.org/pypi/tooz>`_ library provides the
coordination within the groups of service instances. For further coordination within the groups of service instances. For further
information about this approach, see the `high availability guide information about this approach, see the `high availability guide