From 7d5026a330cd01e7370964b03099973ae708dbb2 Mon Sep 17 00:00:00 2001 From: daburmistrov Date: Thu, 6 Aug 2015 16:46:09 +0300 Subject: [PATCH] removing confusing parts --- docsite/rst/playbooks_delegation.rst | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docsite/rst/playbooks_delegation.rst b/docsite/rst/playbooks_delegation.rst index d66ab97e94..4411e4aa29 100644 --- a/docsite/rst/playbooks_delegation.rst +++ b/docsite/rst/playbooks_delegation.rst @@ -192,7 +192,7 @@ Interrupt execution on any error With option ''any_errors_fatal'' any failure on any host in a multi-host play will be treated as fatal and Ansible will exit immediately without waiting for the other hosts. -This option is used when ''serial'' keyword is used. But sometimes ''serial'' execution is unsuitable - number of hosts is unpredictable (because of dynamic inventory), speed is crucial (simultaneous execution is required). But all tasks must be 100% successful to continue playbook execution. +Sometimes ''serial'' execution is unsuitable - number of hosts is unpredictable (because of dynamic inventory), speed is crucial (simultaneous execution is required). But all tasks must be 100% successful to continue playbook execution. For example there is a service located in many datacenters, there a some load balancers to pass traffic from users to service. There is a deploy playbook to upgrade service deb-packages. Playbook stages: @@ -213,8 +213,6 @@ For datacenter "A" playbook can be written this way:: command: /usr/bin/disable-dc - hosts: frontends_dc_a - serial: '100%' - max_fail_percentage: 19 tasks: - name: 'stopping service' command: /usr/bin/stop-software