From 58367569491e2461b5010e72785edfc5c43e19e8 Mon Sep 17 00:00:00 2001 From: RUIJIE YUAN Date: Sun, 4 Jun 2017 12:10:21 +0800 Subject: [PATCH] revise documents releated to batch policy this patch revises documents releated to batch policy since it will not support CLUSTER_DELETE anymore. Change-Id: I13e04a4a082cb3436c5c4119d9c603032979ee41 --- doc/source/user/policy_types/batch.rst | 9 ++++----- examples/policies/batch_policy.yaml | 2 +- 2 files changed, 5 insertions(+), 6 deletions(-) diff --git a/doc/source/user/policy_types/batch.rst b/doc/source/user/policy_types/batch.rst index 61c6d4708..e85e7bc76 100644 --- a/doc/source/user/policy_types/batch.rst +++ b/doc/source/user/policy_types/batch.rst @@ -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 diff --git a/examples/policies/batch_policy.yaml b/examples/policies/batch_policy.yaml index 1560b8728..dd2b9e594 100644 --- a/examples/policies/batch_policy.yaml +++ b/examples/policies/batch_policy.yaml @@ -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