openstack team mailing list archive

[Cristian Tomoiaga <ctomoiaga@xxxxxxxxx>]

Hi Jim,

Thank you! I'll check libvirt in more detail to make sure nothing I need is
missing.
With xend it should work. I'm planning ahead and want to deploy on Libxl
but for the sake of argument I will probably use both KVM (Daniel is to
blame here :) ) and Xen with libxl while I test out everything. It's a good
thing to see interest in libvirt. For some reason I though that libvirt
will move slower with new features (granted libxl has changed from 4.1 to
4.2). Also being bugged by this: https://wiki.openstack.org/wiki/LibvirtAPI
I also plan on local storage (will have to code that since I need
performance and stability) so migration will not be used much (offline
maybe and this should work I believe).
Other than that I wish for a cow, like ZFS's zvol, maybe in 10 years or so.



On Fri, Apr 19, 2013 at 7:27 PM, Jim Fehlig <jfehlig@xxxxxxxx> wrote:

> Daniel P. Berrange wrote:
> > On Fri, Apr 19, 2013 at 01:43:23PM +0300, Cristian Tomoiaga wrote:
> >
> >> As for the compute part, I may need to work with libvirt but I want to
> >> avoid that if possible. Libxl was meant for stacks right ? Again, this
> may
> >> not be acceptable and I would like to know.
> >>
> >
> > Nova already has two drivers which support Xen, one using XenAPI and
> > the other using libvirt. Libvirt itself will either use the legacy
> > XenD/XenStore APIs, or on new enough Xen will use libxl.
> >
> > libxl is a pretty low level interface, not really targetted for direct
> > application usage, but rather for building management APIs like libvirt
> > or XCP. IMHO it would not really be appropriate for OpenStack to directly
> > use libxl. Given that Nova already has two virt drivers which can work
> > with Xen, I also don't really think there's a need to add a 3rd using
> > libxl.
> >
>
> Absolutely agreed, we do not want a libxl nova virt driver :).
>
> FYI, I have not tried the libvirt libxl driver on Xen compute nodes -
> all of my nodes are running the legacy xend toolstack and thus using the
> legacy libvirt xen driver.  (I plan to switch these nodes to the new
> toolstack in the Xen 4.3 timeframe.)  That said, the libxl driver should
> work on a Xen compute node running the libxl stack.  I still haven't
> finished the migration patch for the libvirt libxl driver, so migration
> between "libxl" Xen compute nodes is not possible.
>
> Regards,
> Jim
>
>


-- 
Regards,
Cristian Tomoiaga