[Pacemaker] Alternative communication engine to corosync (etcd/consul/zookeeper/doozerd)

[Andrew Beekhof]

On 29 Jun 2014, at 2:45 pm, Patrick Hemmer <pacemaker at feystorm.net> wrote:

> From: Andrew Beekhof <andrew at beekhof.net>
> Sent: 2014-06-21 21:40:44 EDT
> To: The Pacemaker cluster resource manager <pacemaker at oss.clusterlabs.org>
> Subject: Re: [Pacemaker] Alternative communication engine to corosync (etcd/consul/zookeeper/doozerd)
> 
>> IF someone else implemented such a thing I would be happy to look at including support for it.
>> But knowing what I do about the "joy" that went into writing CPG, there is no way that someone is going to be me.
>> 
>> 
>> 
>>>>> I think pacemaker might be able to use a key/value store natively.
>>>>> 
>>> But I wouldn't even bother with hacking a KVS into something like CPG if it's not needed. I would do it such that the CIB is stored as keys and values natively. I would even think this is more efficient. I'm not sure how the CIB is transmitted between nodes, but I think it easiest to just set a single key when you want to update something like a resource's last-rc-change value.
>>> 
>> CPG is used for a lot more that just keeping the CIB in sync.
>> I did look at some other KVP stores late last year for the CIB, but I was able to get O(2) speedup without it.
>> 
> 
> Does this mean you had something working, even just partially?

No. It was a thought experiment only.  I stopped at the point I realised how invasive it would be.

> If so, do you still have that code around?
> I might be interested in taking a look at this, and having a starting point would be helpful.
> 
> -Patrick
> _______________________________________________
> 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140630/75586a1c/attachment-0003.sig>