Open Stack

On Fri, Sep 20, 2013 at 11:52 AM, Russell Bryant <rbryant at redhat.com> wrote:


> I already put a session on the design summit schedule to discuss the
> future of drivers.  I'm open to alternative approaches for driver
> maintenance, including moving some of them (such as the vmware driver)
> into another tree where the developers focused on it can merge their
> code without waiting for nova-core review.
>
> http://summit.openstack.org/cfp/details/4


That's quite an intriguing proposal.

What criteria would be used to determine which drivers stay in-tree vs.
maintained as forks? E.g. libvirt driver in, everyone else out?
Open-platform drivers (libvirt, xen) in, closed-platform drivers (vmware,
hyperv) out? Drivers for platforms with large (possibly non-OpenStack)
production deployments (libvirt, xen, vmware, hyperv) in, drivers without
(e.g. docker), out?

I'm sure that understanding the rational and philosophy behind such a
proposal would help a lot of people make their decision w.r.t. PTL
candidacies.



>  --
> Russell Bryant
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130920/1aab88d8/attachment.html>