Hi Feri I agree that it should be necessary but for some reason it works well the way it is and everything starts in the correct order. Maybe someone on the dev list can explain a little bit better why this is working. It may have something to do with the fact that it's a clone instead of a primitive.
Tom On Thu 05 Sep 2013 04:48:40 AM EDT, Ferenc Wagner wrote: > Tom Parker <tpar...@cbnco.com> writes: > >> I have attached my original crm config with 201 primitives to this e-mail. > > Hi, > > Sorry to sidetrack this thread, but I really wonder why you only have > order constraints for your Xen resources, without any colocation > constraints. After all, they can only start after the *local* storage > clone has started... For example, you have this: > >> primitive abrazotedb ocf:heartbeat:Xen [...] >> order abrazotedb-after-storage-clone : storage-clone abrazotedb > > and I miss (besides the already mentioned inf above) something like: > > colocation abrazotedb-with-storage-clone inf: abratozedb storage-clone > > Or is this really unnecessary for some reason? Please enlighten me. _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
