Tower provisioning callbacks embedded into the image are a GREAT solution for this.
http://www.ansible.com/tower Alternatively schedule a run to configure and apply policy periodically, only adding machines into the LB once configured. Alternatively, ansible-pull The provisioning callbacks are the cleanest option and allow ephmeral systems to request configuration as they come online, while still operating in push mode and getting full history/status/logging of activity during that configuration (as with ansible-pull this info can be lost). On Thu, Jul 24, 2014 at 10:51 AM, Guy Matz <[email protected]> wrote: > Right, but with an auto-scaling group I don't know of a way to get the new > hostnames of the servers the AS group creates . . . the new host are not > returned in the output from the call to create the autoscaling group > > Thanks, > Guy > > > On Thursday, July 24, 2014 10:09:02 AM UTC-4, Michael Peters wrote: > >> If I understand correctly, this is what add_hosts is for. After you've >> dynamically created a host you can add it to a group and then in a >> subsequent play include a role that would configure that group. >> >> Is that what you're looking for? >> >> On Thu, Jul 24, 2014 at 9:43 AM, Guy Matz <[email protected]> wrote: >> > Hi! Is there any way to provision hosts built by a rax_scaling_group? >> Is >> > it possible to re-read dynamic inventory midway through the run - after >> the >> > servers have been built - and have them ansibled? Or is the only >> option to >> > have them pull after they build? >> > >> > Thanks a lot! >> > Guy >> > >> > -- >> > 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/ >> afa8953b-437e-4c7e-847c-8372ca63881d%40googlegroups.com. >> > 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/95901259-7644-4c9f-ba88-431332b8d903%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/95901259-7644-4c9f-ba88-431332b8d903%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/CA%2BnsWgxn3Ndmmq_utjbaFMt5-oWnK2%2BuVogWMdo%2BHyXsT0hfSw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
