You can look up "wait_for" for basic port open-ness or use a "until" loop in Ansible, so plenty of options if you want to wait until something gets into a particular state.
http://docs.ansible.com/wait_for_module.html http://docs.ansible.com/playbooks_loops.html#do-until-loops On Fri, Mar 21, 2014 at 8:11 AM, Matt Martz <[email protected]> wrote: > Maybe it would be easier instead to have the 'access-config' file be a > template and have a template task that runs on the database server. > > You can see info on accessing data about other hosts at > http://docs.ansible.com/playbooks_variables.html#magic-variables-and-how-to-access-information-about-other-hosts > -- > Matt Martz > [email protected] > > On March 21, 2014 at 12:10:24 AM, Juergen Brendel ([email protected]) > wrote: > > > Hello! > > I have a site.yml file, which includes a 'frontend.yml' and a > 'backend.yml' playbook to configure app servers and database servers. The > frontend.yml playbook is applied to the hosts in the "frontend" group, > while the backend.yml file applies to the hosts in the "backend" group. > > From my app servers, I would like to use "delegate_to" in order to add > their individual IP address to the access-config file of a database > server(s). The database server, however, may not be ready yet, so the > access-config file may not be in place yet. > > Is there a way to ensure that the step specified in 'delegate_to' is only > run on the remote host (the database host), once the remote host is in a > certain state or has finished the setup of a specific step? > > Thank you very much! > > > -- > 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/c04b73ec-d798-47b7-9730-b11adf31ff3f%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/c04b73ec-d798-47b7-9730-b11adf31ff3f%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/etPan.532c2c7b.643c9869.11a12%40mobiletuvix.rackspace.corp<https://groups.google.com/d/msgid/ansible-project/etPan.532c2c7b.643c9869.11a12%40mobiletuvix.rackspace.corp?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/CAEVJ8QNFnsUDk_xnXW561%3D9xTz5Q6acWkiAbq9vmA2gQErsGaQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
