cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

removing confusing parts

Browse source
This commit is contained in:
daburmistrov 2015-08-06 16:46:09 +03:00
parent 0b277b43a4
commit 7d5026a330
1 changed files with 1 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docsite/rst/playbooks_delegation.rst
View file

@ -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