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? Thanks in advance, mario
Hello For some personal experiences, I need to get the CPU idle time of my processor.However, while using this function ( get_cpu_idle_time (CPU-id) ) in the sedf scheduler, I''m unable to boot my computer. Is there a special operation to do? Futhermore, this function is called after being sure that my computer is up! Cheers - MAYAP Christine IRIT/ENSEEIHT 2 rue Charles Camichel - BP 7122 31071 Toulouse cedex 7
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
Hello Thanks for reply. Attached a diff file between my new sedf scheduler and the default one. Cheers On 21/03/2012 10:43, Dario Faggioli wrote:> On Wed, 2012-03-21 at 10:33 +0100, Christine MAYAP wrote: > >> Hello >> >> > Hi, > > >> For some personal experiences, I need to get the CPU idle time of my >> processor.However, while using this function ( get_cpu_idle_time >> (CPU-id) ) in the sedf scheduler, I''m unable to boot my computer. >> Is there a special operation to do? >> >> > May I ask where and how you put the call to that function? I mean, can I > see some sort of patch or anything like that? > > >> Futhermore, this function is called after being sure that my computer >> is up! >> >> > I see and I confirm that seeing the code/patch would be of great help in > trying to help you. > > Thanks and Regards, > Dario > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users-- MAYAP Christine IRIT/ENSEEIHT 2 rue Charles Camichel - BP 7122 31071 Toulouse cedex 7 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
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? mario
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.
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 :-) Any info I can get, would help alot. Thanks, mario
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
On 03/21/2012 12:32 PM, Ian Campbell wrote:> 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 > >Distro in question is Slackware, I already maintain a script for building a Xen package for it, so it would make sense to try and hammer this one in aswell if at all possible. Slackware can install rpm, and there is also a tool for converting deb packages, but it would be much better if I could do it from clean sources, instead of repackaging another distros cruft. Is there a place for "vanilla" xapi source I could download and try building?
Hello Attached, the generated file! Cheers On 21/03/2012 19:03, Dario Faggioli wrote:> diff -Nru old_stuff your_new_stuff >-- MAYAP Christine IRIT/ENSEEIHT 2 rue Charles Camichel - BP 7122 31071 Toulouse cedex 7 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On 21/03/12 11:25, Mario wrote:> On 03/21/2012 12:16 PM, Ian Campbell wrote: >> 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. >><snip>>> 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 :-) > Any info I can get, would help alot. > > Thanks, > marioHi Mario, Glad to hear that you''re interested in packaging Xapi! Just to clarify, Zeus isn''t "starting from scratch," but instead is taking the work that we did with Kronos and building packages that will work on Fedora and CentOS. To get Xapi working on Debian, we mostly had to patch Xapi so that it works with upstream Linux and Xen. We''re going to be upstreaming as many of those patches as possible, so the difference between Xapi on Debian and Xapi on XCP will go down over time. If you want to build Xapi for Slackware, you should take a look at the Xapi source code on GitHub. In each of the source repositories that Xapi depends on, there is a debian branch, which contains all the patches we wrote to get Xapi and it''s dependencies running. Zeus will make use of these patches too. Hope that helps! Mike https://github.com/xen-org/xen-api
On 03/22/2012 01:02 PM, Mike McClurg wrote:> On 21/03/12 11:25, Mario wrote: >> On 03/21/2012 12:16 PM, Ian Campbell wrote: >>> 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. >>> > <snip> >>> 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 :-) >> Any info I can get, would help alot. >> >> Thanks, >> mario > > Hi Mario, > > Glad to hear that you''re interested in packaging Xapi! Just to clarify, > Zeus isn''t "starting from scratch," but instead is taking the work that > we did with Kronos and building packages that will work on Fedora and > CentOS. To get Xapi working on Debian, we mostly had to patch Xapi so > that it works with upstream Linux and Xen. We''re going to be upstreaming > as many of those patches as possible, so the difference between Xapi on > Debian and Xapi on XCP will go down over time. > > If you want to build Xapi for Slackware, you should take a look at the > Xapi source code on GitHub. In each of the source repositories that Xapi > depends on, there is a debian branch, which contains all the patches we > wrote to get Xapi and it''s dependencies running. Zeus will make use of > these patches too. > > Hope that helps! > > Mike > > https://github.com/xen-org/xen-apiOk thanks, unfortunatly some of the ocaml dependancies only come with unstable xen (for example xenctrl), so I probably can''t use this in production untill the next major release. Along the way I have noticed that another ocaml dependancy "type-conv" is not being installed as such, instead it installs as "type_conv" (notice the underscore) under /usr/lib*/ocaml tree. I am unsure if this is how its supposed to be, or if its a bug, but for now I have it symlinked, type_conv to type-conv. Is there a preffered way to report issues to, a mailing list or irc channel for example? mario