Re: [Xen-users] xend future

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Wed, 2012-03-21 at 11:25 +0000, Mario wrote:
> On 03/21/2012 12:16 PM, Ian Campbell wrote:
> > On Wed, 2012-03-21 at 11:08 +0000, Mario wrote:
> >> On 03/21/2012 10:49 AM, Ian Campbell wrote:
> >>> On Tue, 2012-03-20 at 21:58 +0000, Mario wrote:
> >>>> Hey everyone, I was wondering, since xend will finaly be removed in the
> >>>> next major release, what will the future be like for us who use its
> >>>> XML-RPC features? Is there going to be some other way to do it, for
> >>>> example adding xml-rpc support into libxl, or should I simply start
> >>>> porting all my scripts over to libvirt?
> >>>
> >>> The best options for replacing xend here are either libvirt/virtd or
> >>> xapi.
> >>>
> >>> I guess you already know about libvirt.
> >>>
> >>> The XML-RPC interface exposed by xapi is a descendant of that used by
> >>> xend, although I'm not sure how much they have in common nowadays. Might
> >>> potentially make porting somewhat simple I guess (just a guess though).
> >>>
> >>> You can get xapi either via the traditional XCP route or it is also now
> >>> available in Debian and Ubuntu as a result of project Kronos. Project
> >>> Zeus[2] is in progress to add it to Fedora etc.
> >>>
> >>> Ian.
> >>>
> >>> [0] http://wiki.xen.org/wiki/XCP_Introduction
> >>> [1] http://wiki.xen.org/wiki/Project_Kronos
> >>> [2] http://wiki.xen.org/wiki/Project_Zeus_Fedora_Spec
> >>>
> >>>
> >>
> >> Well, I would usualy consider Xapi since it's directly related to Xen,
> >> however, because it is "distro-locked" in such a way that there has to
> >> be a fork per distro doesn't really seem like the right choice to me. I
> >> suppose it has to be like that if its just a hack to make XCP work on
> >> classic distro's? Or am I mistaken?
> >
> > The aim of Kronos and Zeus is to make XAPI available as a proper package
> > on various distros, there is no fork -- only effort to package things
> > for the particular distro packaging formats, which is normal for any
> > software -- or hack involved.
> >
> > Part of Kronos has necessarily involved changes to the xapi side to make
> > it less entangled with XCP and therefore usable in a generic environment
> > (i.e. resolving the "distro-lock" which you refer to), this has
> > obviously made Zeus a fair bit easier.
> >
> > Ian.
> >
> 
> In that case, I am interested in making a package for yet another 
> distribution, and instead of making up yet another name and doing it all 
> from scratch (if its even possible), which of the two would be a better 
> choice to follow? Which of the two is more generic? Does having Zeus 
> project ensure that Kronos will stay active, or is Zeus not dependant on 
> Kronos development, etc etc :-)

Which distro? CCing Mike who has been heavily involved with both Kronos
and Zeus (I'm just an outside observer).

AFAIK the disentanglement aspect arising from both Kronos and Zeus are
resulting in patches which are being committed to the upstream xapi code
base. Unless your distro happens to use .deb (Kronos) or .rpm (Zeus)
packages then probably only this upstream aspect is useful to you,
otherwise the appropriate project could perhaps serve as a starting
point to apply the necessary distro specific policies to.

Ian.

> Any info I can get, would help alot.
> 
> Thanks,
> mario



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users