openstack/deb-senlin
Code Issues Proposed changes

revise documents releated to batch policy

Browse Source 
this patch revises documents releated to batch policy since it will
not support CLUSTER_DELETE anymore.

Change-Id: I13e04a4a082cb3436c5c4119d9c603032979ee41
This commit is contained in:
RUIJIE YUAN 2017-06-04 12:10:21 +08:00
parent b6cd2f5bce
commit 5836756949
2 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/source/user/policy_types/batch.rst
View File

@ -23,9 +23,8 @@ managed and there won't be flood of service requests sending to any other
services that will form a DOS (denial-of-service) attack.
Currently, this policy is applicable to clusters of all profile types and it
is enforced when cluster is updated or deleted. The development team is still
looking for an elegant solution that can regulate the resource creation
requests.
is enforced when cluster is updated. The development team is still looking
for an elegant solution that can regulate the resource creation requests.
Properties
@ -46,8 +45,8 @@ Below is a typical spec for a batch policy:
The ``min_in_service`` property specifies the minimum number of nodes to be
kept in ACTIVE status. This is mainly for cluster update use cases. The
other property ``max_batch_size`` specifies the number of nodes to be updated
or deleted in each batch. This property is mainly used to ensure that batch
requests are still within the processing capability of a backend service.
in each batch. This property is mainly used to ensure that batch requests
are still within the processing capability of a backend service.
Between each batch of service requests, you can specify an interval in the
unit of seconds using the ``pause_time`` property. This can be used to ensure

2
examples/policies/batch_policy.yaml
View File

@ -3,7 +3,7 @@ type: senlin.policy.batch
version: 1.0
properties:
# Minimum number of nodes that should remain in service when
# performing actions like CLUSTER_UPDATE, CLUSTER_DELETE.
# performing actions like CLUSTER_UPDATE.
min_in_service: 1
# Maximum number of nodes that can be processed at the