Open Stack

Hi Russell,

My intent was to create a common code starting point, where others, who are
also interested in bringing OpenStack to FreeBSD could develop the missing
features, have it reviewed and do progress. Those changes are, as Roman
have noticed, a work in progress, however, given the limitations (features
not yet supported) it allows for working with VMs on FreeBSD hosts. We will
gradually add support for the rest of the features.

May I gently ask you what is the rationale behind the approach to wait till
the entire set of features is covered instead of allowing the developers
interested in making progress in bringing support for the FreeBSD to push
their changes incrementally and eventually cover all the necessary features?

Regards,
Michal


On 31 March 2014 19:17, Russell Bryant <rbryant at redhat.com> wrote:

> On 03/31/2014 01:01 PM, Michał Dubiel wrote:
> > Hi All,
> >
> > I have prepared commits I would like to have it reviewed and eventually
> > merged that add initial, limited support for FreeBSD as a host to nova.
> > It includes basic networking via freebsd_net driver (similar to the
> > linux_net) and few addons to libvirt compute driver in order to support
> > the bhyve hypervisor. Intent for those commits is let other play with
> > openstack on FreeBSD and to provide a code base for further development,
> > as the current version comes with many limitations like:
> >
> > - Only FreeBSD guest OSes can be used
> > - No support for the config drive
> > - Only one disk and one Ethernet interface
> > - No pause/resume functionality
> > - No VM migration support
> > - No files injection to VMs filesystem
> > - Only works with bridged networking using nova-network with
> > Flat/FlatDHCP multi-host mode
> >
> > Unit test are included, however, for all that to work on a real system
> > you have to use a slightly patched version of libvirt as not all
> > features has been merged to the official repository yet. My question is
> > if that is applicable to be merged at all, or should I wait for all
> > necessary stuff to be in libvirt official repository at first? I want
> > also mention that there is an active work underway in libvirt community
> > to have all them implemented and included in the libvirt code.
>
> The limitations you mention are pretty severe, so I'm not sure this
> sounds like something we would want to include in that state.
>
> If the gaps were closed, the biggest blocker to considering it for
> merging would be a CI platform that's running Nova in this setup against
> every patch.  We require that for all hypervisor drivers now.
>
> https://wiki.openstack.org/wiki/HypervisorSupportMatrix/DeprecationPlan
>
> --
> 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/20140401/98133898/attachment.html>