Hi Kurt, There's a thread that John Griffith started about 3rd party storage drivers, where the code lives, how to review, how to ensure quality and maintenance, see http://lists.openstack.org/pipermail/openstack-dev/2013-July/012557.html. It won't answer all your questions but gives you an idea of pluggable architecture and maintenance. Anne On Fri, Aug 23, 2013 at 10:25 AM, Kurt Griffiths < kurt.griffiths at rackspace.com> wrote: > > next in the queue is ZMQ - and it will also sit on top of some > > existing MB - we've plan to use rabbit, proton and other > > technologies as storage backend. > > I'd love to get everyone's thoughts on how many/what kinds of transport > and storage drivers should be part of the project directly vs. maintained > independently as "3rd-party" drivers. How do other projects handle this? > > @kgriffs > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Anne Gentle annegentle at justwriteclick.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130826/4bd45af3/attachment.html>