03.07.2013 00:20, Vladislav Bogdanov wrote: ... >>> But tickets currently are quite limited - they have only 4 states, so >>> it is impossible to put f.e. number there. >> >> What are you trying to do with that? > > That is very convenient way to f.e stop dozen of resources in one shot > for some maintenance. I have special RA which creates ticket on a > cluster start and deletes it on a cluster stop. And many resources may > depend on that ticket. If you request resource handled by that RA to > stop, ticket is revoked and all dependent resources stop.
Ah, and in one setup (lustre fs on top of geo-clustered two-layer drbd) I also use ticket revocation to cause a transition abort in a controllable way, so advisory ordering constraints work. Idea is to do a CIB modification after some event, so after that advisory-ordered resources are to be stopped in the same transition, and they are stopped in an order I want. IMHO nice hack ;) _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
