<div dir="ltr">Hello,<br><br>Yes, libvirt's qemu driver works almost fine currently, except the fact that it<br>needs a 'real' bridge driver, so all the networking configuration like filtering rules, NAT, etc<br>
could be done automatically, like for Linux now, instead of making user to perform<br>all the configuration manually.<br><br>I've been planning to get to bhyve driver as well, but probably after finishing with the bridge driver<br>
(but unfortunately, I don't have a full picture what would be the best way to implement that).<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Nov 25, 2013 at 3:50 PM, Daniel P. Berrange <span dir="ltr"><<a href="mailto:berrange@redhat.com" target="_blank">berrange@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Fri, Nov 22, 2013 at 10:46:19AM -0500, Russell Bryant wrote:<br>
> On 11/22/2013 10:43 AM, Rafał Jaworowski wrote:<br>
> > Russell,<br>
> > First, thank you for the whiteboard input regarding the blueprint for<br>
> > FreeBSD hypervisor nova driver:<br>
> > <a href="https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node" target="_blank">https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node</a><br>
> ><br>
> > We were considering libvirt support for bhyve hypervisor as well, only<br>
> > wouldn't want to do this as the first approach for FreeBSD+OpenStack<br>
> > integration. We'd rather bring bhyve bindings for libvirt later as<br>
> > another integration option.<br>
> ><br>
> > For FreeBSD host support a native hypervisor driver is important and<br>
> > desired long-term and we would like to have it anyways. Among things<br>
> > to consider are the following:<br>
> > - libvirt package is additional (non-OpenStack), external dependency<br>
> > (maintained in the 'ports' collection, not included in base system),<br>
> > while native API (via libvmmapi.so library) is integral part of the<br>
> > base system.<br>
> > - libvirt license is LGPL, which might be an important aspect for some users.<br>
><br>
> That's perfectly fine if you want to go that route as a first step.<br>
> However, that doesn't mean it's appropriate for merging into Nova.<br>
> Unless there are strong technical justifications for why this approach<br>
> should be taken, I would probably turn down this driver until you were<br>
> able to go the libvirt route.<br>
<br>
</div>The idea of a FreeBSD bhyve driver for libvirt has been mentioned<br>
a few times. We've already got a FreeBSD port of libvirt being<br>
actively maintained to support QEMU (and possibly Xen, not 100% sure<br>
on that one), and we'd be more than happy to see further contributions<br>
such as a bhyve driver.<br>
<br>
I am of course biased, as libvirt project maintainer, but I do agree<br>
that supporting bhyve via libvirt would make sense, since it opens up<br>
opportunities beyond just OpenStack. There are a bunch of applications<br>
built on libvirt that could be used to manage bhyve, and a fair few<br>
applications which have plugins using libvirt<br>
<br>
Taking on maint work for a new OpenStack driver is a non-trivial amount<br>
of work in itself. If the burden for OpenStack maintainers can be reduced<br>
by, pushing work out to / relying on support from, libvirt, that makes<br>
sense from OpenStack/Nova's POV.<br>
<br>
Regards,<br>
Daniel<br>
<span class="HOEnZb"><font color="#888888">--<br>
|: <a href="http://berrange.com" target="_blank">http://berrange.com</a> -o- <a href="http://www.flickr.com/photos/dberrange/" target="_blank">http://www.flickr.com/photos/dberrange/</a> :|<br>
|: <a href="http://libvirt.org" target="_blank">http://libvirt.org</a> -o- <a href="http://virt-manager.org" target="_blank">http://virt-manager.org</a> :|<br>
|: <a href="http://autobuild.org" target="_blank">http://autobuild.org</a> -o- <a href="http://search.cpan.org/~danberr/" target="_blank">http://search.cpan.org/~danberr/</a> :|<br>
|: <a href="http://entangle-photo.org" target="_blank">http://entangle-photo.org</a> -o- <a href="http://live.gnome.org/gtk-vnc" target="_blank">http://live.gnome.org/gtk-vnc</a> :|<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>