[Pacemaker] staggered startup

[James Harper]

> 
> On Thu, Sep 6, 2012 at 12:08 AM, James Harper
> <james.harper at bendigoit.com.au> wrote:
> > A power failure tonight indicated that my clustered resources (xen vm's)
> have a dependency requirement like "make sure at least one domain
> controller VM is fully up and running before starting any other windows
> servers". Determining a status of "fully up and running" is probably complex
> so as a minimum I need to say "make sure resource1 has been started for 60
> seconds before starting resource2".
> 
> The RA shouldn't return 'success' until the service really is finished starting
> up.
> Granted that is hard when the service lives inside the VM.
> 

Yes I know how it _should_ happen :)

After a bit more reading I think I can make a resource (or resource group) that is considered started when it is able to ping one of the Domain Controllers (including an offsite DC that requires the router VM being up). Once a DC is pingable it will only be a few seconds away from being fully functional, so it is reasonable to start other VMs. This seems much better than a blind delay.

Thanks

James