While going through the manual i came to know that xend has an http interface which can be used to interact with xen. However searching on the lists and googling only resulted in 3-4 posts on the devel list which still didn''t have any information on the same. Is anyone using it ... ? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Anand a écrit :> While going through the manual i came to know that xend has an http > interface which can be used to interact with xen. However searching on > the lists and googling only resulted in 3-4 posts on the devel list > which still didn''t have any information on the same. > > Is anyone using it ... ?We are using this interface to control the xend daemon. With this interface, you can do quite everything you can with the xm tool. For example to destroy a domain, you can do a HTTP POST request on this url : http://xenserver:8000/xend/domain/domain-name with parameter op=destroy To create a domainU, you can do a POST request on this url : http://xenserver:8000/xend/domain/ with parameter op=create&config=s-expression s-expression is the xen configuration format (you can look at it making a xm list -l for example) To list started domains : http://xenserver:8000/xend/domain/ or http://xenserver:8000/xend/domain/?detail=1 The http server don''t exactly map xm commands however : to boot a new server, you have 2 or 3 operations to do when using the http server : create, wait_for_devices and unpause The xend HTTP interface is accessible via a TCP socket or via an Unix socket (way used by xm in xen-3.0) -- Jean-David Silberzahn ADVISEO http://www.adviseo.fr/ http://www.open-sp.fr/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Dear Jean, Thanks a lot for the help. Is there some kind of documentation for the complete list of commands for http interface ? Alternatively if you have the list and explanation i would very appreciate if you can post it here. On 1/2/06, Jean-David Silberzahn <jds@adviseo.fr> wrote:> > Anand a écrit : > > > While going through the manual i came to know that xend has an http > > interface which can be used to interact with xen. However searching on > > the lists and googling only resulted in 3-4 posts on the devel list > > which still didn''t have any information on the same. > > > > Is anyone using it ... ? > > We are using this interface to control the xend daemon. With this > interface, you can do quite everything you can with the xm tool. > For example to destroy a domain, you can do a HTTP POST request on this > url : > http://xenserver:8000/xend/domain/domain-name > with parameter > op=destroy > To create a domainU, you can do a POST request on this url : > http://xenserver:8000/xend/domain/ > with parameter > op=create&config=s-expression > s-expression is the xen configuration format (you can look at it making > a xm list -l for example) > To list started domains : > http://xenserver:8000/xend/domain/ > or > http://xenserver:8000/xend/domain/?detail=1 > > The http server don''t exactly map xm commands however : to boot a new > server, you have 2 or 3 operations to do when using the http server : > create, wait_for_devices and unpause > > The xend HTTP interface is accessible via a TCP socket or via an Unix > socket (way used by xm in xen-3.0) >regards, Anand _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I''ve not the complete list of commands for http interface, I try to discover them when I need to use it ... If someone has this list or know where to find it, i would appreciate too to get this ... However, the command I already found and use with the HTTP interface are those : GET requests : /xend/domain/ AND /xend/domain/?detail=1 : to get a list of all started nodes (detailed or not) /xend/node : to get informations on the node on which xen runs (free memory, number of cpu, ...) POST requests on /xend/domain : parameters : op=create&config=s-expression : to create a paused domU with his config urlencoded in "s-expression" (s-expr = (domain (memory 128)(device (vbd (dev xvda1)(uname phy:device)(mode w))) ............) POST requests on /xend/domain/domain-name : parameters : op=wait_for_devices : command to wait for the devices of a newly created domU before unpausing it parameters : op=unpause : unpause a domU (xm unpause) parameters : op=pause : pause a domU (xm pause) parameters : op=destroy : destroy a domU (xm destroy) parameters : op=shutdown&reason=(halt|poweroff|reboot) : 3 different ways to shutdown your domU parameters : op=cpu_sedf_set&latency=nnn&slice=nnn&period=nnn&weight=nnn&extratime=n : réglage des paramètres sedf (xm sched-sedf) I think it''s possible to do migrations, save and restore, and many other things, but i have not searched how to use those commands Another think to know when using the HTTP interface is that xend acts differently depending on the headers (especially the Accept: HTTP header) : if you don''t put such a header, it will answer you with s-expression (useful if you are developping something over xen for example) and if you put one, you''ll get an HTML formatted answer (useful to read it, even if the s-expressions mostly contains more informations). regards, -- Jean-David Silberzahn ADVISEO http://www.adviseo.fr/ http://www.open-sp.fr/ Anand a écrit :> Dear Jean, > > Thanks a lot for the help. > > Is there some kind of documentation for the complete list of commands > for http interface ? Alternatively if you have the list and > explanation i would very appreciate if you can post it here. > > On 1/2/06, *Jean-David Silberzahn* <jds@adviseo.fr > <mailto:jds@adviseo.fr>> wrote: > > Anand a écrit : > > > While going through the manual i came to know that xend has an http > > interface which can be used to interact with xen. However > searching on > > the lists and googling only resulted in 3-4 posts on the devel list > > which still didn''t have any information on the same. > > > > Is anyone using it ... ? > > We are using this interface to control the xend daemon. With this > interface, you can do quite everything you can with the xm tool. > For example to destroy a domain, you can do a HTTP POST request on > this > url : > http://xenserver:8000/xend/domain/domain-name > with parameter > op=destroy > To create a domainU, you can do a POST request on this url : > http://xenserver:8000/xend/domain/ > with parameter > op=create&config=s-expression > s-expression is the xen configuration format (you can look at it > making > a xm list -l for example) > To list started domains : > http://xenserver:8000/xend/domain/ > or > http://xenserver:8000/xend/domain/?detail=1 > <http://xenserver:8000/xend/domain/?detail=1> > > The http server don''t exactly map xm commands however : to boot a new > server, you have 2 or 3 operations to do when using the http server : > create, wait_for_devices and unpause > > The xend HTTP interface is accessible via a TCP socket or via an Unix > socket (way used by xm in xen-3.0) > > > > regards, > > Anand > >------------------------------------------------------------------------ > >_______________________________________________ >Xen-users mailing list >Xen-users@lists.xensource.com >http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Jan 02, 2006 at 02:43:05PM +0100, Jean-David Silberzahn wrote:> I''ve not the complete list of commands for http interface, I try to > discover them when I need to use it ... If someone has this list or know > where to find it, i would appreciate too to get this ...+1 The simplest way is probably to read the xend source code to get an exhaustive list, the problem is that as long as it''s not ''officially'' documented, I''m afraid you can have garantee that the interface or its semantic won''t change.> However, the command I already found and use with the HTTP interface are > those : > > GET requests : > /xend/domain/ AND /xend/domain/?detail=1 : to get a list of all started > nodes (detailed or not) > /xend/node : to get informations on the node on which xen runs (free > memory, number of cpu, ...) > > POST requests on /xend/domain : > parameters : op=create&config=s-expression : to create a paused domU > with his config urlencoded in "s-expression" (s-expr = (domain (memory > 128)(device (vbd (dev xvda1)(uname phy:device)(mode w))) ............) > > POST requests on /xend/domain/domain-name : > parameters : op=wait_for_devices : command to wait for the devices of a > newly created domU before unpausing it > parameters : op=unpause : unpause a domU (xm unpause) > parameters : op=pause : pause a domU (xm pause) > parameters : op=destroy : destroy a domU (xm destroy) > parameters : op=shutdown&reason=(halt|poweroff|reboot) : 3 different > ways to shutdown your domU > parameters : > op=cpu_sedf_set&latency=nnn&slice=nnn&period=nnn&weight=nnn&extratime=n > : réglage des paramètres sedf (xm sched-sedf)Thanks for the informations !> I think it''s possible to do migrations, save and restore, and many other > things, but i have not searched how to use those commands > > Another think to know when using the HTTP interface is that xend acts > differently depending on the headers (especially the Accept: HTTP > header) : if you don''t put such a header, it will answer you with > s-expression (useful if you are developping something over xen for > example) and if you put one, you''ll get an HTML formatted answer (useful > to read it, even if the s-expressions mostly contains more informations).Anthony Liguori also suggested last month the possibility to add an XML-RPC interface, which would certainly make it easier to use in a variety of environments (at the expense of slightly more CPU usage I guess) and feel more confident about this being a supported interface. Daniel -- Daniel Veillard | Red Hat http://redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks Jean for the information. I tried the the http://xendomain:8000/xend/domain/?detail=1, it shows me exactly the same as http://xendomain:8000/xend/domain I will appreciate if you can you explain these parameter below ? Are they related to cpu time scheduling for the domain ? op=cpu_sedf_set&latency=nnn &slice=nnn&period=nnn&weight=nnn&extratime=n : réglage des paramètres sedf (xm sched-sedf) On 1/2/06, Jean-David Silberzahn <jds@adviseo.fr> wrote:> > I''ve not the complete list of commands for http interface, I try to > discover them when I need to use it ... If someone has this list or know > where to find it, i would appreciate too to get this ... > However, the command I already found and use with the HTTP interface are > those : > > GET requests : > /xend/domain/ AND /xend/domain/?detail=1 : to get a list of all started > nodes (detailed or not) > /xend/node : to get informations on the node on which xen runs (free > memory, number of cpu, ...) > > POST requests on /xend/domain : > parameters : op=create&config=s-expression : to create a paused domU > with his config urlencoded in "s-expression" (s-expr = (domain (memory > 128)(device (vbd (dev xvda1)(uname phy:device)(mode w))) ............) > > POST requests on /xend/domain/domain-name : > parameters : op=wait_for_devices : command to wait for the devices of a > newly created domU before unpausing it > parameters : op=unpause : unpause a domU (xm unpause) > parameters : op=pause : pause a domU (xm pause) > parameters : op=destroy : destroy a domU (xm destroy) > parameters : op=shutdown&reason=(halt|poweroff|reboot) : 3 different > ways to shutdown your domU > parameters : > op=cpu_sedf_set&latency=nnn&slice=nnn&period=nnn&weight=nnn&extratime=n > : réglage des paramètres sedf (xm sched-sedf) > > I think it''s possible to do migrations, save and restore, and many other > things, but i have not searched how to use those commands > > Another think to know when using the HTTP interface is that xend acts > differently depending on the headers (especially the Accept: HTTP > header) : if you don''t put such a header, it will answer you with > s-expression (useful if you are developping something over xen for > example) and if you put one, you''ll get an HTML formatted answer (useful > to read it, even if the s-expressions mostly contains more informations). > > regards, > -- > Jean-David Silberzahn > > ADVISEO > http://www.adviseo.fr/ > http://www.open-sp.fr/ > > > > Anand a écrit : > > > Dear Jean, > > > > Thanks a lot for the help. > > > > Is there some kind of documentation for the complete list of commands > > for http interface ? Alternatively if you have the list and > > explanation i would very appreciate if you can post it here. > > > > On 1/2/06, *Jean-David Silberzahn* <jds@adviseo.fr > > <mailto:jds@adviseo.fr>> wrote: > > > > Anand a écrit : > > > > > While going through the manual i came to know that xend has an > http > > > interface which can be used to interact with xen. However > > searching on > > > the lists and googling only resulted in 3-4 posts on the devel > list > > > which still didn''t have any information on the same. > > > > > > Is anyone using it ... ? > > > > We are using this interface to control the xend daemon. With this > > interface, you can do quite everything you can with the xm tool. > > For example to destroy a domain, you can do a HTTP POST request on > > this > > url : > > http://xenserver:8000/xend/domain/domain-name > > with parameter > > op=destroy > > To create a domainU, you can do a POST request on this url : > > http://xenserver:8000/xend/domain/ > > with parameter > > op=create&config=s-expression > > s-expression is the xen configuration format (you can look at it > > making > > a xm list -l for example) > > To list started domains : > > http://xenserver:8000/xend/domain/ > > or > > http://xenserver:8000/xend/domain/?detail=1 > > <http://xenserver:8000/xend/domain/?detail=1> > > > > The http server don''t exactly map xm commands however : to boot a > new > > server, you have 2 or 3 operations to do when using the http server > : > > create, wait_for_devices and unpause > > > > The xend HTTP interface is accessible via a TCP socket or via an > Unix > > socket (way used by xm in xen-3.0) > > > > > > > > regards, > > > > Anand > > > >------------------------------------------------------------------------ > > > >_______________________________________________ > >Xen-users mailing list > >Xen-users@lists.xensource.com > >http://lists.xensource.com/xen-users > > > >regards, Anand _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>The simplest way is probably to read the xend source code to get >an exhaustive list, the problem is that as long as it''s not >''officially'' documented, I''m afraid you can have garantee that >the interface or its semantic won''t change.This is what i fear about. If the specs change after i have used them in my application, it would be a disaster. Looks like i would be better off creating my own interface even for that matter, it will take some time, however can gurantee that specs won''t change.> Anthony Liguori also suggested last month the possibility to add an >XML-RPC interface, which would certainly make it easier to use in a >variety of environments (at the expense of slightly more CPU usage I >guess) and feel more confident about this being a supported interface.That would be really nice, ofcourse as you said on the expense of slight cpu power. However for that flexibility many people might consider the cpu power less expensive ;) regards, Anand _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Anand a écrit :> Thanks Jean for the information. > > I tried the the http://xendomain:8000/xend/domain/?detail=1, it shows > me exactly the same as http://xendomain:8000/xend/domainIf you try from a web-browser it''s normal :) try to do it with a simple network client (like telnet) : telnet xenserver 8000 GET /xend/domain HTTP/1.1 will return you a list like this (dom0 domain-name1 domain-name2 ......) AND telnet xenserver 8000 GET /xend/domain/?detail=1 HTTP/1.1 will return you a list like this ((domain (domid 0)(uuid ......) .......)(domain (domid 1)............)) It''s just because your browser puts a header like this : Accept: text/html that makes xend recognize it as a browser and not another client> > I will appreciate if you can you explain these parameter below ? Are > they related to cpu time scheduling for the domain ? > > op=cpu_sedf_set&latency=nnn > &slice=nnn&period=nnn&weight=nnn&extratime=n > : réglage des paramètres sedf (xm sched-sedf)Sorry i wrote it into french, cpu_sedf_set (and get too) is related to cpu time scheduling for the domain and the different parameters are quickly explained on xen wiki : http://wiki.xensource.com/xenwiki/Scheduling (in the section sedf-scheduler) regards, -- Jean-David Silberzahn ADVISEO http://www.adviseo.fr/ http://www.open-sp.fr/> > > On 1/2/06, *Jean-David Silberzahn* <jds@adviseo.fr > <mailto:jds@adviseo.fr>> wrote: > > I''ve not the complete list of commands for http interface, I try to > discover them when I need to use it ... If someone has this list > or know > where to find it, i would appreciate too to get this ... > However, the command I already found and use with the HTTP > interface are > those : > > GET requests : > /xend/domain/ AND /xend/domain/?detail=1 : to get a list of all > started > nodes (detailed or not) > /xend/node : to get informations on the node on which xen runs (free > memory, number of cpu, ...) > > POST requests on /xend/domain : > parameters : op=create&config=s-expression : to create a paused domU > with his config urlencoded in "s-expression" (s-expr = (domain (memory > 128)(device (vbd (dev xvda1)(uname phy:device)(mode w))) ............) > > POST requests on /xend/domain/domain-name : > parameters : op=wait_for_devices : command to wait for the devices > of a > newly created domU before unpausing it > parameters : op=unpause : unpause a domU (xm unpause) > parameters : op=pause : pause a domU (xm pause) > parameters : op=destroy : destroy a domU (xm destroy) > parameters : op=shutdown&reason=(halt|poweroff|reboot) : 3 different > ways to shutdown your domU > parameters : > op=cpu_sedf_set&latency=nnn&slice=nnn&period=nnn&weight=nnn&extratime=n > : réglage des paramètres sedf (xm sched-sedf) > > I think it''s possible to do migrations, save and restore, and many > other > things, but i have not searched how to use those commands > > Another think to know when using the HTTP interface is that xend acts > differently depending on the headers (especially the Accept: HTTP > header) : if you don''t put such a header, it will answer you with > s-expression (useful if you are developping something over xen for > example) and if you put one, you''ll get an HTML formatted answer > (useful > to read it, even if the s-expressions mostly contains more > informations). > > regards, > -- > Jean-David Silberzahn > > ADVISEO > http://www.adviseo.fr/ > http://www.open-sp.fr/ > > > > Anand a écrit : > > > Dear Jean, > > > > Thanks a lot for the help. > > > > Is there some kind of documentation for the complete list of > commands > > for http interface ? Alternatively if you have the list and > > explanation i would very appreciate if you can post it here. > > > > On 1/2/06, *Jean-David Silberzahn* <jds@adviseo.fr > <mailto:jds@adviseo.fr> > > <mailto:jds@adviseo.fr <mailto:jds@adviseo.fr>>> wrote: > > > > Anand a écrit : > > > > > While going through the manual i came to know that xend > has an http > > > interface which can be used to interact with xen. However > > searching on > > > the lists and googling only resulted in 3-4 posts on the > devel list > > > which still didn''t have any information on the same. > > > > > > Is anyone using it ... ? > > > > We are using this interface to control the xend daemon. With > this > > interface, you can do quite everything you can with the xm > tool. > > For example to destroy a domain, you can do a HTTP POST > request on > > this > > url : > > http://xenserver:8000/xend/domain/domain-name > <http://xenserver:8000/xend/domain/domain-name> > > with parameter > > op=destroy > > To create a domainU, you can do a POST request on this url : > > http://xenserver:8000/xend/domain/ > > with parameter > > op=create&config=s-expression > > s-expression is the xen configuration format (you can look at it > > making > > a xm list -l for example) > > To list started domains : > > http://xenserver:8000/xend/domain/ > > or > > http://xenserver:8000/xend/domain/?detail=1 > <http://xenserver:8000/xend/domain/?detail=1> > > <http://xenserver:8000/xend/domain/?detail=1> > > > > The http server don''t exactly map xm commands however : to > boot a new > > server, you have 2 or 3 operations to do when using the http > server : > > create, wait_for_devices and unpause > > > > The xend HTTP interface is accessible via a TCP socket or > via an Unix > > socket (way used by xm in xen-3.0) > > > > > > > > regards, > > > > Anand > > > >------------------------------------------------------------------------ > > > >_______________________________________________ > >Xen-users mailing list > > Xen-users@lists.xensource.com <mailto:Xen-users@lists.xensource.com> > >http://lists.xensource.com/xen-users > > > > > regards, > > Anand_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>If you try from a web-browser it''s normal :) try to do it with a simple >network client (like telnet) : >telnet xenserver 8000 >GET /xend/domain HTTP/1.1>will return you a list like this (dom0 domain-name1 domain-name2 ......) >AND >telnet xenserver 8000 >GET /xend/domain/?detail=1 HTTP/1.1>will return you a list like this >((domain (domid 0)(uuid ......) .......)(domain (domid 1)............)) >It''s just because your browser puts a header like this : Accept: >text/html that makes xend recognize it as a browser and not another clientThanks, worked as you said.> op=cpu_sedf_set&latency=nnn > &slice=nnn&period=nnn&weight=nnn&extratime=n > : réglage des paramètres sedf (xm sched-sedf)> Sorry i wrote it into french, cpu_sedf_set (and get too) is related to > cpu time scheduling for the domain and the different parameters are > quickly explained on xen wiki : > http://wiki.xensource.com/xenwiki/Scheduling (in the section > sedf-scheduler)I tried understanding from the wiki, however didn''t understand, thats why i asked. If its possible for you to explain perhaps with an example, i will really appreciate it. regards, Anand _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Anand a écrit :> >If you try from a web-browser it''s normal :) try to do it with a simple > >network client (like telnet) : > >telnet xenserver 8000 > >GET /xend/domain HTTP/1.1 > > >will return you a list like this (dom0 domain-name1 domain-name2 ......) > >AND > >telnet xenserver 8000 > >GET /xend/domain/?detail=1 HTTP/1.1 > > >will return you a list like this > >((domain (domid 0)(uuid ......) .......)(domain (domid 1)............)) > >It''s just because your browser puts a header like this : Accept: > >text/html that makes xend recognize it as a browser and not another > client > > Thanks, worked as you said. > > > op=cpu_sedf_set&latency=nnn > > &slice=nnn&period=nnn&weight=nnn&extratime=n > > : réglage des paramètres sedf (xm sched-sedf) > > Sorry i wrote it into french, cpu_sedf_set (and get too) is > related to > cpu time scheduling for the domain and the different parameters are > quickly explained on xen wiki : > http://wiki.xensource.com/xenwiki/Scheduling (in the section > sedf-scheduler) > > > I tried understanding from the wiki, however didn''t understand, thats > why i asked. If its possible for you to explain perhaps with an > example, i will really appreciate it. > > regards, > AnandBasically xen''s SEDF Scheduler enables you to be certain that a given domain has slice nanoseconds cpu during period nanoseconds. The domain can use less cpu (if he did not need as much cpu). Typically a domain on which you ran the command xm sched-sedf dom-name 5000000 1000000 0 0 0 : has the right to use 1ms of cpu every 5 ms at most, and if it need it, it is certain to have 1ms every 5ms xm sched-sedf dom-name 5000000 1000000 0 1 0 : dom-name can use 1ms every 5ms at least (if domain needs to be active) and can use more if others domain don''t need the cpu Playing with this scheduler makes you possible - Without ExtraTime : to say that a given domain is active at least x nanoseconds every y nanoseconds where y is the period you specified and x is the minimum between the slice you allow to the domain and the time needed by the domain (not totally certain) - With ExtraTime : to say that a given domain is active at most x nanoseconds every y nanoseconds where x is the minimum between the slice you allow and the time needed by the domain What I don''t know is how this scheduler acts in smp mode (smp domU) ... regards, -- Jean-David Silberzahn ADVISEO http://www.adviseo.fr/ http://www.open-sp.fr/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Anand wrote:> Dear Jean, > > Thanks a lot for the help. > > Is there some kind of documentation for the complete list of commands > for http interface ? Alternatively if you have the list and > explanation i would very appreciate if you can post it here.http://hg.codemonkey.ws/libxend Is pretty close to exhaustive except for scheduler operations and VNET operations. Check out XendClient.py, that''s the closest thing to a full list. Regards, Anthony Liguori> On 1/2/06, *Jean-David Silberzahn* <jds@adviseo.fr > <mailto:jds@adviseo.fr>> wrote: > > Anand a écrit : > > > While going through the manual i came to know that xend has an http > > interface which can be used to interact with xen. However > searching on > > the lists and googling only resulted in 3-4 posts on the devel list > > which still didn''t have any information on the same. > > > > Is anyone using it ... ? > > We are using this interface to control the xend daemon. With this > interface, you can do quite everything you can with the xm tool. > For example to destroy a domain, you can do a HTTP POST request on > this > url : > http://xenserver:8000/xend/domain/domain-name > with parameter > op=destroy > To create a domainU, you can do a POST request on this url : > http://xenserver:8000/xend/domain/ > with parameter > op=create&config=s-expression > s-expression is the xen configuration format (you can look at it > making > a xm list -l for example) > To list started domains : > http://xenserver:8000/xend/domain/ > or > http://xenserver:8000/xend/domain/?detail=1 > <http://xenserver:8000/xend/domain/?detail=1> > > The http server don''t exactly map xm commands however : to boot a new > server, you have 2 or 3 operations to do when using the http server : > create, wait_for_devices and unpause > > The xend HTTP interface is accessible via a TCP socket or via an Unix > socket (way used by xm in xen-3.0) > > > > regards, > > Anand > >------------------------------------------------------------------------ > >_______________________________________________ >Xen-users mailing list >Xen-users@lists.xensource.com >http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks Jean for all the explanation and information. On 1/2/06, Jean-David Silberzahn <jds@adviseo.fr> wrote:> > Basically xen''s SEDF Scheduler enables you to be certain that a given > domain has slice nanoseconds cpu during period nanoseconds. The domain > can use less cpu (if he did not need as much cpu). > > Typically a domain on which you ran the command > xm sched-sedf dom-name 5000000 1000000 0 0 0 : has the right to use 1ms > of cpu every 5 ms at most, and if it need it, it is certain to have 1ms > every 5ms > xm sched-sedf dom-name 5000000 1000000 0 1 0 : dom-name can use 1ms > every 5ms at least (if domain needs to be active) and can use more if > others domain don''t need the cpu > > Playing with this scheduler makes you possible > - Without ExtraTime : to say that a given domain is active at least x > nanoseconds every y nanoseconds > where y is the period you specified > and x is the minimum between the slice you allow to the domain and the > time needed by the domain (not totally certain) > > - With ExtraTime : to say that a given domain is active at most x > nanoseconds every y nanoseconds > where x is the minimum between the slice you allow and the time needed > by the domain > > What I don''t know is how this scheduler acts in smp mode (smp domU) ... >regards, Anand _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Dear Anthony, I looked at http://hg.codemonkey.ws/libxend, looks real nice. Is it complete ? If i may ask what other work you are doing on xen ? I see xenfs there as well. I hope you won''t mind sharing about your work. And thanks for the pointer to XendClient.py. On 1/2/06, Anthony Liguori <aliguori@us.ibm.com> wrote:> > Anand wrote: > > > Dear Jean, > > > > Thanks a lot for the help. > > > > Is there some kind of documentation for the complete list of commands > > for http interface ? Alternatively if you have the list and > > explanation i would very appreciate if you can post it here. > > http://hg.codemonkey.ws/libxend > > Is pretty close to exhaustive except for scheduler operations and VNET > operations. Check out XendClient.py, that''s the closest thing to a full > list. > > Regards, > > Anthony Liguori > > > On 1/2/06, *Jean-David Silberzahn* <jds@adviseo.fr > > <mailto:jds@adviseo.fr>> wrote: > > > > Anand a écrit : > > > > > While going through the manual i came to know that xend has an > http > > > interface which can be used to interact with xen. However > > searching on > > > the lists and googling only resulted in 3-4 posts on the devel > list > > > which still didn''t have any information on the same. > > > > > > Is anyone using it ... ? > > > > We are using this interface to control the xend daemon. With this > > interface, you can do quite everything you can with the xm tool. > > For example to destroy a domain, you can do a HTTP POST request on > > this > > url : > > http://xenserver:8000/xend/domain/domain-name > > with parameter > > op=destroy > > To create a domainU, you can do a POST request on this url : > > http://xenserver:8000/xend/domain/ > > with parameter > > op=create&config=s-expression > > s-expression is the xen configuration format (you can look at it > > making > > a xm list -l for example) > > To list started domains : > > http://xenserver:8000/xend/domain/ > > or > > http://xenserver:8000/xend/domain/?detail=1 > > <http://xenserver:8000/xend/domain/?detail=1> > > > > The http server don''t exactly map xm commands however : to boot a > new > > server, you have 2 or 3 operations to do when using the http server > : > > create, wait_for_devices and unpause > > > > The xend HTTP interface is accessible via a TCP socket or via an > Unix > > socket (way used by xm in xen-3.0) > > > > > > > > regards, > > > > Anand > > > >------------------------------------------------------------------------ > > > >_______________________________________________ > >Xen-users mailing list > >Xen-users@lists.xensource.com > >http://lists.xensource.com/xen-users > > > >-- regards, Anand _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Anand wrote:> Dear Anthony, > > I looked at http://hg.codemonkey.ws/libxend, looks real nice. Is it > complete ?Just missing a few functions to access the VCPU information.. I have no plans to implement an interface to VNET. I''m hoping it can be used as a backend for libvir. If you haven''t checked libvir out, you should.> If i may ask what other work you are doing on xen ? I see xenfs there > as well. I hope you won''t mind sharing about your work.Oh, I''ve got a fair bit of hg repositories there. xenfs is a FUSE filesystem that exposes a /proc like interface for Xen. Regards, Anthony Liguori> And thanks for the pointer to XendClient.py. > > On 1/2/06, *Anthony Liguori* <aliguori@us.ibm.com > <mailto:aliguori@us.ibm.com>> wrote: > > Anand wrote: > > > Dear Jean, > > > > Thanks a lot for the help. > > > > Is there some kind of documentation for the complete list of > commands > > for http interface ? Alternatively if you have the list and > > explanation i would very appreciate if you can post it here. > > http://hg.codemonkey.ws/libxend > > Is pretty close to exhaustive except for scheduler operations and VNET > operations. Check out XendClient.py, that''s the closest thing to > a full > list. > > Regards, > > Anthony Liguori > > > On 1/2/06, *Jean-David Silberzahn* <jds@adviseo.fr > <mailto:jds@adviseo.fr> > > <mailto:jds@adviseo.fr <mailto:jds@adviseo.fr>>> wrote: > > > > Anand a écrit : > > > > > While going through the manual i came to know that xend > has an http > > > interface which can be used to interact with xen. However > > searching on > > > the lists and googling only resulted in 3-4 posts on the > devel list > > > which still didn''t have any information on the same. > > > > > > Is anyone using it ... ? > > > > We are using this interface to control the xend daemon. With > this > > interface, you can do quite everything you can with the xm tool. > > For example to destroy a domain, you can do a HTTP POST > request on > > this > > url : > > http://xenserver:8000/xend/domain/domain-name > > with parameter > > op=destroy > > To create a domainU, you can do a POST request on this url : > > http://xenserver:8000/xend/domain/ > > with parameter > > op=create&config=s-expression > > s-expression is the xen configuration format (you can look > at it > > making > > a xm list -l for example) > > To list started domains : > > http://xenserver:8000/xend/domain/ > > or > > http://xenserver:8000/xend/domain/?detail=1 > > <http://xenserver:8000/xend/domain/?detail=1> > > > > The http server don''t exactly map xm commands however : to > boot a new > > server, you have 2 or 3 operations to do when using the http > server : > > create, wait_for_devices and unpause > > > > The xend HTTP interface is accessible via a TCP socket or > via an Unix > > socket (way used by xm in xen-3.0) > > > > > > > > regards, > > > > Anand > > > >------------------------------------------------------------------------ > > > >_______________________________________________ > >Xen-users mailing list > >Xen-users@lists.xensource.com <mailto:Xen-users@lists.xensource.com> > >http://lists.xensource.com/xen-users > > > > > > > -- > > regards, > > Anand_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users