Thanks! I’d love to take a look at that. Rolling LB’s isn’t a requirement for my current project, though it’s not entirely out of the foreseeable future.
Here is a gist of what I threw together today while fiddling around: https://gist.github.com/stanlemon/8153200 I’d appreciate any feedback or suggestions as I’m rather new to Ansible. I have two, arguably three apps that need this same type of deployment and so I was leaning towards sticking the tasks in their own separate file and including that in an app-specific playbook. Any advice there would also be appreciated. Thanks, -- Stan Lemon On December 27, 2013 at 3:16:50 PM, PePe Amengual ([email protected]) wrote: I'm doing exactly this and once I finish I will uploaded it to Ansible galaxy. The rolling restart and LB pool problem is very easy to solve if you have a LB that could check a status file to be present on the webserver and if not present take that server out of the pool automatically then you will be sure that you don't have any connections on the server so you can perform your upgrade/deploy. -- 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]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out. -- 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]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
