On 02/05/2013, at 6:39 PM, Michael Schwartzkopff <mi...@clusterbau.com> wrote:
> Am Donnerstag, 2. Mai 2013, 08:32:19 schrieb James Harper: > > Currently I am using a ping resource to ensure that other windows VM's don't > > start up until the domain controllers are started. This helps prevent > > things like Exchange not starting properly because they can't find a domain > > controller. > > > > On a complete network shutdown (eg a long power failure), windows domain > > controllers can take quite a while to start servicing active directory > > requests if there are no other domain controllers on the network, in the > > order of 5-20 minutes, but they do respond to pings (depending on firewall > > rules) so my other VM's start up too early. > > > > Has anyone else solved this problem? I'm thinking that I'll simply have a > > resource that does an nslookup for the active directory domain name on the > > selected domain controllers, like ping does, (dns won't service active > > directory related requests until domain services are active), but maybe > > someone else has done it better? > > > > Thanks > > > > James > > Hi, > > the VirtualDomain resource agent provides the parameter monitor_scripts. Newer versions of Pacemaker also support the more generic container concept that allows you to represent resources running inside other resources. In this case, you could define a nagios resource (for your other VMs to depend on) which only shows as "started" when the domain controller becomes active. Yan authored that particular feature, he should be able to provide more detail if needed. > This hook is a space separated list of your scripts that monitors the virtual > machine. You can take some inspriration the nagios check scripts to monitor > your domain controller. > > Be sure to make the timeout of the start operation long enough. > > Greetings, > > -- > Dr. Michael Schwartzkopff > Guardinistr. 63 > 81375 München > > Tel: (0163) 172 50 98 > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
