fix partitioning documentation

Change-Id: I8da18f2e9f63f27f22d2d03d7ea476305c3acd42
This commit is contained in:
gord chung 2018-01-29 21:02:30 +00:00 committed by gordon chung
parent f9d322ea9e
commit d2c6722d85
2 changed files with 4 additions and 5 deletions

View File

@ -29,10 +29,9 @@ LOG = log.getLogger(__name__)
OPTS = [
cfg.StrOpt('backend_url',
help='The backend URL to use for distributed coordination. If '
'left empty, per-deployment central agent and per-host '
'compute agent won\'t do workload '
'left empty, alarm evaluation won\'t do workload '
'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',
default=1.0,
help='Number of seconds between heartbeats for distributed '

View File

@ -108,8 +108,8 @@ 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
The alarm evaluation process can be scaled horizontally but requires
workload partitioning to function correctly. The
`Tooz <https://pypi.python.org/pypi/tooz>`_ library provides the
coordination within the groups of service instances. For further
information about this approach, see the `high availability guide