Yep!!! This is a *MAJOR* feature of Ansible to build Continuous Deployment systems.
You can see an example using haproxy here: https://github.com/ansible/ansible-examples/tree/master/lamp_haproxy You can do this even simpler with an F5, Elastic Load Balancer, Citrix Netscaler, or whatever for swapping out the relevant modules -- though haproxy is free, so it makes a good example. See also http://www.ansibleworks.com/docs/playbooks_delegation.html You can talk to as many systems in parallel as you want by specifying --forks, ex: --forks 100 for 100 systems at a time. If you set "serial: 20" that means "20 must be fully configured before moving on to the next set", so if you had 500 systems with serial 50 (and forks --50 for maximum speed), it completes in 5 rolling update batches with only losing 10% capacity on your web farm in each batch. Lots of users use this in combination with Jenkins to do as many as 5-10 updates an hour, without any user impacts. There's also going to be a nice guide coming soon (WIP): https://github.com/ansible/ansible/pull/5221 On Tue, Dec 10, 2013 at 3:29 PM, Brian Coca <[email protected]> wrote: > it was just a placeholder for however you manage the webnodes, in my case > it is: > > service: name=nginx state=stopped > > that should work for anything that uses the system's init apps > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- Michael DeHaan <[email protected]> CTO, AnsibleWorks, Inc. http://www.ansibleworks.com/ -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
