Open Stack

On 03/18/2017 07:48 PM, Mike Perez wrote:
> On 12:35 Mar 14, Jay Pipes wrote:
>> On 03/14/2017 08:57 AM, Julien Danjou wrote:
>>> On Tue, Mar 14 2017, Davanum Srinivas wrote:
>>>
>>>> Let's do it!! (etcd v2-v3 in tooz)
>>>
>>> Hehe. I'll move that higher in my priority list, I swear. But anyone is
>>> free to beat me to it in the meantime. ;)
>>
>> A weekend experiment:
>>
>> https://github.com/jaypipes/os-lively
>>
>> Not tooz, because I'm not interested in a DLM nor leader election library
>> (that's what the underlying etcd3 cluster handles for me), only a fast
>> service liveness/healthcheck system, but it shows usage of etcd3 and Google
>> Protocol Buffers implementing a simple API for liveness checking and host
>> maintenance reporting.
>>
>> My plan is to push some proof-of-concept patches that replace Nova's
>> servicegroup API with os-lively and eliminate Nova's use of an RDBMS for
>> service liveness checking, which should dramatically reduce the amount of
>> both DB traffic as well as conductor/MQ service update traffic.
>
> As Monty has mentioned, I'd love for us to decide on one thing. As being
> a moderator of that discussion I was trying not to be one-sided.
>
> Whether or not a decision was made 1.5 years ago, the community that was
> present at that time of the decision at the summit decided on an abstraction
> layer to have options. Forcing an option on the community without gathering
> feedback of what the community currently looks like is not a good idea.
>
> I'd recommend if you want to make this base service, start the discussions in
> somewhere other than the dev list, like the Forum.

Mike, it was an experiment :)

But, yes, happy to participate in a discussion at the forum.

Best,
-jay