Open Stack

  Eric Windisch wrote:

> This thread highlights more deeply the problems for the FreeBSD folks.
> First, I still disagree with the recommendation that they contribute to
> libvirt. It's a classic example of creating two or more problems from one.
> Once they have support in libvirt, how long before their code is in a
> version of libvirt acceptable to Nova? When they hit edge-cases or bugs,
> requiring changes in libvirt, how long before those fixes are accepted by
> Nova?

Could you please elaborate why you disagree on the contributing patches
to libvirt approach and what the alternative approach do you propose?

Also, could you please elaborate on what is 'version of libvirt
acceptable to Nova'? Cannot we just say that e.g. Nova requires libvirt
X.Y to be deployed on FreeBSD?

Anyway, speaking about FreeBSD support I assume we actually talking
about Bhyve support. I think it'd be good to break the task and
implement FreeBSD support for libvirt/Qemu first.

Qemu driver of libvirt works fine with FreeBSD for quite some time
already and adding support for that in Nova will allow to do all the
ground work before we could move to the libvirt/bhyve support.

I'm planning to start with adding networking support. Unfortunately, it
seems I got late with the spec for Juno though:

https://review.openstack.org/#/c/95328/

Roman Bogorodskiy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140716/90d45c27/attachment.pgp>