On Tue, 2012-02-07 at 11:09 +0900, 李泰勲 wrote: > Hi Jiaju > > I am testing about working of booth while investigating booth source code. > > I don't understand ticket grant and revoke process perfectly that is > related to connecting each booth > so I would like to know booth's working that would be matching your > offering source code. > > Could you give me information about booth sequences that would be the > ticket's grant,revoke,lease logic and working of ticket's expiry time.
General speaking, you would want to grant some ticket on certain site initially, which means the corresponding resources can be run at that site. For the lease logic, ticket granting means that site has the ticket lease. The lease has an expiry time, after the expiry time, that lease is expired and the corresponding resources can't be run at that site any longer. If the site which has the original ticket granting is alive, it will renew the lease before the ticket expired, but if that site is broken, when the lease is expired, the lease logic will go into election stage and a new site will get the ticket lease, thus the resources will be able to run at the new site. You can revoke the ticket from the site as well, but in most cases, you may not want to do this. The possible scenario I can think of is when the admin wants to do some maintenance work, or wants to do the ticket management manually. > > when do you think the booth's working is fixed and completed ? Oh, I have not finished it yet;) But I'm still working on it, since I also have some other tasks, maybe the progress is not fast these days;) > > Is there anything to help you about booth's implementation or etc? The framework is finished, but there are still some bugs in it, so the code may not work for you for the time being, I'll be more than happy if anyone can help to fix bugs, or develop new features;) For the short term, I think adding the man pages, documentation and some automation test programs/scripts would be very good. For the long term, I also have something new in my mind, maybe I should add a TODO to document it later. Well, the primary thing for now is to fix current bugs to make it really working, and I myself will spend more time on it these two weeks;) Thanks, Jiaju > > Best Regards, Taihun > > (2011/12/05 15:18), Jiaju Zhang wrote: > > Hello everyone, > > > > I'm happy to announce to the Booth cluster ticket manager, which is part > > of the key feature for pacemaker in 2011 - improving support for > > multi-site clusters. > > > > Multi-site clusters can be considered as “overlay” clusters where each > > cluster site corresponds to a cluster node in a traditional cluster. The > > overlay cluster is managed by the booth mechanism. It guarantees that > > the cluster resources will be highly available across different cluster > > sites takes. This is achieved by using so-called tickets that are > > treated as failover domain between cluster sites, in case a site should > > be down. > > > > Booth is designed to be an add-on of pacemaker, and now it is also > > hosted in ClusterLabs, together with pacemaker. You can find it from: > > > > https://github.com/ClusterLabs/booth > > > > Now, booth is still in heavy development, so it may not work for you for > > the time being;) But I'll be working on it ... > > > > Review and comments are highly appreciated! > > > > Thanks, > > Jiaju > > > > > > _______________________________________________ > > 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
