[Pacemaker] [ANNOUNCE] The Booth Cluster Ticket Manager - part of multi-site support in pacemaker

[李泰勲]

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.

when do you think the booth's working is fixed and completed ?

Is there anything to help you about booth's implementation or etc?

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 at 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
>
>