On Tuesday, October 21, 2014, Roman Bogorodskiy <rbogorods...@mirantis.com> wrote:
> On Mon, Oct 20, 2014 at 10:19 PM, Joe Gordon <joe.gord...@gmail.com > <javascript:;>> wrote: > > On Sat, Oct 18, 2014 at 10:04 AM, Roman Bogorodskiy < > rbogorods...@mirantis.com <javascript:;>> wrote: > [snip] > >> High level overview of what needs to be done: > >> > >> - Nova > >> * linux_net needs to be re-factored to allow to plug in FreeBSD > >> support (that's what the spec linked above is about) > >> * nova.virt.disk.mount needs to be extended to support FreeBSD's > >> mdconfig(8) in a similar way to Linux's losetup > [snip] > > What about neutron? We are in the process of trying to deprecate > nova-network, so any new thing needs to support neutron. > > > AFAIK, there's no defined migration plan yet, unless I missed that. > Anyway, I don't see any blockers regarding an implementation of a driver > similar to linuxbridge that'd work on FreeBSD. > > Also, Semihalf guys are working on OpenContail/FreeBSD and > Neutron/OpenContrial support, so that's an option as well. I have no problem with supporting FreeBSD as a hypervisor operating system, especially if there is a solid team on the FreeBSD side that will commit to maintaining the changes required and adding the necessary CI (especially ensuring that when it breaks it gets fixed). However, I see Neutron support as a firm requirement. We've spent a large amount of time getting closer and closer to deprecating nova-network. Despite opening it up for limited development again, I don't think we should be making the transition plan harder by introducing new features that don't work with Neutron. Michael -- Rackspace Australia
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
