Re: [openstack-dev] FreeBSD/bhyve support for nova with libvirt
On Tue, Apr 01, 2014 at 08:22:37PM +0200, Michał Dubiel wrote: > OK, thanks Russell and Daniel for your suggestions. > > Stackforge sounds reasonable for the time being, though it's not perfect as > it doesn't prevent from occasional conflicts we may hit while pulling > changes from the original Nova repository to our clone. > > An example is code that is not pure additions, but changes to the existing > Nova source code (for instance libvirt vif driver calls directly code from > linux_net module, which should be abstracted out, and proper for the given > platform implementation should be used automatically). This sort of > problems apply to the entire FreeBSD platform regardless which one: bhyve > or qemu is used. If you have a need todo general refactoring like that, then I'd suggest those particular patches could actually be submitted straight to Nova mainline, since they are valid/useful for multiple libvirt platforms, even ignoring bhyve. Just have the stuff that's truly bhyve / FreeBSD specific in your separate tree. That should hopefully reduce the amount of pain you encur. So in this example, you could introduce the abstraction layer for the networking setup APIs into mainline GIT, and update libvirt / linux_net code to work with it. Then just have the bhyve + freebsd networking stuff in your separate repo. > Last question. May we expect review help while the code is in the > Stackforge, or we have to wait until all features are finished and it's > accepted to be reviewed in Nova repo? Given our general code review overload I think it is unlikely you'll get any frequent / detailed code review, except for refactoring bits you submit to nova git directly. As libvirt maintainer though, I'd be happy to take a look at what you are developing and offer advice and high level review to make sure you are heading in a direction that it sensible for the eventual nova merge. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] FreeBSD/bhyve support for nova with libvirt
On 04/01/2014 02:22 PM, Michał Dubiel wrote: > OK, thanks Russell and Daniel for your suggestions. > > Stackforge sounds reasonable for the time being, though it's not perfect > as it doesn't prevent from occasional conflicts we may hit while pulling > changes from the original Nova repository to our clone. > > An example is code that is not pure additions, but changes to the > existing Nova source code (for instance libvirt vif driver calls > directly code from linux_net module, which should be abstracted out, and > proper for the given platform implementation should be used > automatically). This sort of problems apply to the entire FreeBSD > platform regardless which one: bhyve or qemu is used. I think the changes to use proper abstraction are things we could accept now. That's just cleaning up the code and will make it easier for you to maintain your additoins. > Nevertheless, I'll create a repo there, which will act as a codebase for > development of the missing features till the all required for Nova merge > are in place. If you go the route of doing a fork of all of Nova, I would not use stackforge. The workflow on stackforge just isn't going to work when you need to sync with the latest Nova changes. If you go that route, i would just suggest a git repo somewhere else (github or whatever). If you're able to trim things down such that it's just a set of files added to Nova, you could probably use Stackforge. > Last question. May we expect review help while the code is in the > Stackforge, or we have to wait until all features are finished and it's > accepted to be reviewed in Nova repo? Using stackforge is beneficial because you get some increased visibility and you use the same development workflow as all openstack projects. It would at least facilitate getting others involved that are interested in this. As for more "official" Nova review from nova-core, it's unlikely, unless someone takes a specific interest in the code. However, just like we're doing here, I (and others) are happy to help discuss the project's direction and approach to help make sure it ends up in a state that Nova is happy with. -- Russell Bryant ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] FreeBSD/bhyve support for nova with libvirt
OK, thanks Russell and Daniel for your suggestions. Stackforge sounds reasonable for the time being, though it's not perfect as it doesn't prevent from occasional conflicts we may hit while pulling changes from the original Nova repository to our clone. An example is code that is not pure additions, but changes to the existing Nova source code (for instance libvirt vif driver calls directly code from linux_net module, which should be abstracted out, and proper for the given platform implementation should be used automatically). This sort of problems apply to the entire FreeBSD platform regardless which one: bhyve or qemu is used. Nevertheless, I'll create a repo there, which will act as a codebase for development of the missing features till the all required for Nova merge are in place. Last question. May we expect review help while the code is in the Stackforge, or we have to wait until all features are finished and it's accepted to be reviewed in Nova repo? Regards, Michal On 1 April 2014 17:31, Russell Bryant wrote: > On 04/01/2014 09:39 AM, Michał Dubiel wrote: > > We've already started requiring CI for compute drivers. I expect > that > > in the Juno cycle we will formalize a base set of features required > for > > any compute driver in the tree. While we haven't decided on that set > > yet, it sounds like it may be too soon for this platform to meet > those > > requirements. > > > > > > Thanks Russell. Just to clarify. What do you mean by compute driver > > here? An additional option enabling bhyve hypervisor in the existing > > libvirt compute driver also counts as a separate driver? > > It's not a new driver in the technical sense, but it is a new column in > our support matrix, so I was thinking the same testing requirements > should apply. > > https://wiki.openstack.org/wiki/HypervisorSupportMatrix > > -- > Russell Bryant > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] FreeBSD/bhyve support for nova with libvirt
On 04/01/2014 09:39 AM, Michał Dubiel wrote: > We've already started requiring CI for compute drivers. I expect that > in the Juno cycle we will formalize a base set of features required for > any compute driver in the tree. While we haven't decided on that set > yet, it sounds like it may be too soon for this platform to meet those > requirements. > > > Thanks Russell. Just to clarify. What do you mean by compute driver > here? An additional option enabling bhyve hypervisor in the existing > libvirt compute driver also counts as a separate driver? It's not a new driver in the technical sense, but it is a new column in our support matrix, so I was thinking the same testing requirements should apply. https://wiki.openstack.org/wiki/HypervisorSupportMatrix -- Russell Bryant ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] FreeBSD/bhyve support for nova with libvirt
On 04/01/2014 11:16 AM, Daniel P. Berrange wrote: > On Mon, Mar 31, 2014 at 01:17:39PM -0400, Russell Bryant 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. > > Yes, this does sound a little bit premature given that even from the > libvirt POV we're not calling this production ready yet. If you want > to get a headstart on BHyve support in the Nova libvirt driver, then > I'd suggest a short term strategy of maintaining a fork of the Nova > code on github/stackforge, with a clean series of patches for BHyve > changes to libvirt. When we see this is getting to a useful level of > functionality, then it can be submit for review in Nova proper. +1 Thanks for the added info from the libvirt side. -- Russell Bryant ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] FreeBSD/bhyve support for nova with libvirt
On Mon, Mar 31, 2014 at 01:17:39PM -0400, Russell Bryant 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. Yes, this does sound a little bit premature given that even from the libvirt POV we're not calling this production ready yet. If you want to get a headstart on BHyve support in the Nova libvirt driver, then I'd suggest a short term strategy of maintaining a fork of the Nova code on github/stackforge, with a clean series of patches for BHyve changes to libvirt. When we see this is getting to a useful level of functionality, then it can be submit for review in Nova proper. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] FreeBSD/bhyve support for nova with libvirt
> > We've already started requiring CI for compute drivers. I expect that > in the Juno cycle we will formalize a base set of features required for > any compute driver in the tree. While we haven't decided on that set > yet, it sounds like it may be too soon for this platform to meet those > requirements. Thanks Russell. Just to clarify. What do you mean by compute driver here? An additional option enabling bhyve hypervisor in the existing libvirt compute driver also counts as a separate driver? Regards, Michal ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] FreeBSD/bhyve support for nova with libvirt
On 04/01/2014 08:20 AM, Michał Dubiel wrote: > 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? We've been continuously raising the bar on the code that can be in the Nova tree. That helps ensure that Nova is of a very high quality while avoiding unnecessary maintenance burdens. We've already started requiring CI for compute drivers. I expect that in the Juno cycle we will formalize a base set of features required for any compute driver in the tree. While we haven't decided on that set yet, it sounds like it may be too soon for this platform to meet those requirements. An alternative would be to develop your additions in a new repository on stackforge for now. I'm be curious how much patching is needed versus new modules. The patches would be more painful to maintain out of tree. -- Russell Bryant ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] FreeBSD/bhyve support for nova with libvirt
Hi Roman, I agree, I'm going to revive the old blueprint and maybe you're right to have a separate one for the freebsd_net. I wanted to ask at the first place the OpenStack community what do they think, are they going to accept our work at all, etc. Actually the code for the bhyve support is quite trivial, it's all about choosing the correct uri for libvirt connection and similar things. It's just the simplest approach possible, we want to extend it of course that would allow for more features. Code for the freebsd_net is slightly bigger but is also not a big one. As for the qemu, unfortunately, it also needs a slightly modified version of either libvirt or nova as some host related functions like getting list of PCI passthrough devices doesn't work on FreeBSD hosts yet. Regards, Michal On 31 March 2014 19:19, Roman Bogorodskiy wrote: > 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. > > Hi Michal, > > I'd say it would be good to revive the old blueprint about bhyve > support and push the patches. Also, probably freebsd_net itself > deserve a blueprint on its own. And I guess it could be tested > independently of bhyve driver because as you might now qemu driver is > also supported on FreeBSD. > > As for the bhyve, I think it's ok to push it now and mark it WIP for > example. I'd think it's not a small piece of code and will take some > time to review anyway. > > But I think it cannot be merged until libvirt supports all the required > features (otherwise it'd be troublesome to setup gate jobs for bhyve for > I think). > > As for the modifications to libvirt, unfortunately, they'll not get it > into the upcoming 1.2.3 as the freeze started already. > > Roman Bogorodskiy > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] FreeBSD/bhyve support for nova with libvirt
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 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@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] FreeBSD/bhyve support for nova with libvirt
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. Hi Michal, I'd say it would be good to revive the old blueprint about bhyve support and push the patches. Also, probably freebsd_net itself deserve a blueprint on its own. And I guess it could be tested independently of bhyve driver because as you might now qemu driver is also supported on FreeBSD. As for the bhyve, I think it's ok to push it now and mark it WIP for example. I'd think it's not a small piece of code and will take some time to review anyway. But I think it cannot be merged until libvirt supports all the required features (otherwise it'd be troublesome to setup gate jobs for bhyve for I think). As for the modifications to libvirt, unfortunately, they'll not get it into the upcoming 1.2.3 as the freeze started already. Roman Bogorodskiy pgptY0LlVscTq.pgp Description: PGP signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] FreeBSD/bhyve support for nova with libvirt
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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] FreeBSD/bhyve support for nova with libvirt
How do you handle the fact that as it stands bhyve can only run *nix like OS's (specifically FreeBSD and Linux only)? The long term answer seems to be a working kqemu or use something like PetiteCloud ( http://www.petitecloud.org) as a bridge (run OS nested on bhyve under PC) On Mon, Mar 31, 2014 at 1: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. > > Regards, > Michal > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] FreeBSD/bhyve support for nova with libvirt
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. Regards, Michal ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
