I believe this to be possible. I don't think I can architect you a full
solution via email and what not, but we can go over some key points. There
are likely to be a number of "moving" parts here.
It sounds like you are roughly wanting to perform something similar to a
Blue-Green deployment, while maintaining the original LB.
Here are some of my thoughts.
1. Run a task using rax_clb and register the results. This will contain a
list of current nodes
2. Run your provisioning task using the rax module with exact_count,
however you should have a way to double the exact_count (e.g. 20 instead of
the normal 10), so that you can provision new servers, register this result
too
3. The rax module returns some top level keys of importance, in this case
'success' will hold a list of all of the machines that were just created.
a. You could also run the rax module with an existing exact_count which
would return something like rax.instance_ids.instances
4. add these new servers to a hostgroup using add_host
5. configure the new servers
6. run rax_clb_nodes to add in the new servers
7. Test somehow
8. using the node information provided in #1, use rax_clb_nodes to mark as
draining
9. Same as #8 but now remove
10. Run a rax module task again, and drop the exact_count to what you
expect (e.g. 10 instead of 20). The way that the rax module works is it
deletes the oldest servers in this scenario, which should delete the ones
you expect
a. If you did 3a, you could use a rax task with state=absent and pass
in rax.instance_ids.instances to the 'instance_ids' attribute, to delete
the old servers
Without having tried it, those are roughly the steps I would try to perform.
You might also want to look at
https://developer.rackspace.com/blog/rolling-deployments-with-ansible-and-cloud-load-balancers/
--
Matt Martz
sivel.net
@sivel
On Tue, Sep 16, 2014 at 9:05 AM, Graham Hay <[email protected]> wrote:
> Hi,
>
> We were considering taking an "immutable server" approach to deployments
> (we may not be able to due to 3rd party restrictions whitelisting IPs), is
> that something that would be possible using the rax module? So, a
> deployment would consist of spinning up and provisioning x new servers,
> adding them to the LB, waiting to check for errors, and then removing the
> old servers. I couldn't think of a way to do so while using the name &
> exact_count approach.
>
> Thanks,
>
> Graham
>
> --
> 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].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/68a61851-432d-4e4b-942c-9de821eeabd2%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/68a61851-432d-4e4b-942c-9de821eeabd2%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAD8N0v-VihpJ%2BVRCyS38NMG9H_T_BF-JhjWky8cfyGrMTVZtig%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
