On May 2, 2013, at 7:53 AM, Alex Glikson <GLIKSON at il.ibm.com<mailto:GLIKSON at il.ibm.com>> wrote: Changbin Liu <changbin.liu at gmail.com<mailto:changbin.liu at gmail.com>> wrote on 02/05/2013 05:32:05 PM: > Subject: Re: [openstack-dev] Nova workflow management update > > Hi Joshua, > > Just to share some thoughts: [...] Using ZK makes a lot of sense.. The problem is that making ZooKeeper a mandatory component to support even basic workflow management might be an issue. So, the approach which seems to make most sense is to define abstract internal interfaces for the various capabilities that ZK can provide (distributed locking, leader election, etc), and then have one or more implementations (one of which might be based on ZK). This is the approach that has been taken for the membership service (service group monitoring APIs) -- introducing the flexibility to use ZK backend, but keeping the default to be DB-backed. +1 Adrian -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130502/4fcca236/attachment.html>