Jehan-Guillaume de Rorthais <j...@dalibo.com> writes: > > I feel like you guys are talking of a solution that already exists and you > probably already know, eg. "etcd". > > Etcd provides: > > * a cluster wide key/value storage engine > * support quorum > * key locking > * atomic changes > * REST API > * etc... > > However, it requires to open a new TCP port, indeed :/ >
My main inspiration and reasoning is indeed to introduce the same functionality provided by etcd into a corosync-based cluster without having to add a parallel cluster consensus solution. Simply installing etcd means 1) now you have two clusters, 2) etcd doesn't handle 2-node clusters or fencing and doesn't degrade well to a single node, 3) relying on the presence of the KV-store in pacemaker tools is not an option unless pacemaker wants to make etcd a requirement. Cheers, Kristoffer > Moreover, as a RA developer, I am currently messing with attrd weird > behavior[1], so any improvement there is welcomed :) > > Cheers, > > [1] https://github.com/ClusterLabs/PAF/issues/131 > -- // Kristoffer Grönlund // kgronl...@suse.com _______________________________________________ Users mailing list: Users@clusterlabs.org https://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org