Thanks, I should probably read the whole of that guide :) On 26 September 2014 13:15, Matt Martz <[email protected]> wrote:
> Graham, > > I'll assume that if you have processes running on the system to perform > steps such as installing the cloud monitoring agent, that you probably have > a managed service level offering. > > In which case, you should probably wait until that is complete. There are > docs located at < > http://docs.ansible.com/guide_rax.html#rackconnect-and-managed-cloud> > that will show you how to wait for the automation to complete. > > On Fri, Sep 26, 2014 at 2:25 AM, Graham Hay <[email protected]> wrote: > >> Hi, >> >> This is possibly more of a rackspace question than an ansible one, but >> hey-ho. When we create a new instance using the rax module, we then have a >> post-creation playbook containing steps that need to be run on all servers. >> The creation playbook waits for the instances to have finished building, >> but even so, if we run the post creation playbook straight away it will >> sometimes fail due to the rackspace post install scripts using apt to >> install the monitoring software. >> >> At the moment, I just wait until the instances all have the three green >> dots before running the next step, but obviously this isn't ideal. Is there >> any way to tell that it's safe to proceed? >> >> Thanks, >> >> Graham >> > > > > -- > Matt Martz > @sivel > sivel.net > -- 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/CAGz4Hndmp8w%3DAMbFoZQs%2BBxDA1gwiU9JXbXYu0RchMj0sb%3D6sA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
