This is a great patch, I just want to make sure everyone who has written a tool against xm that is perhaps screen scrapping the output of xm block-list or xm network-list that the interface has changed. You will now have to use --long to get the same S-Expression output. Perhaps this sort of changes should be announced on xen-announce in the future? Is there such a list? Regards, Anthony Liguori _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Fri, Feb 17, 2006 at 03:06:00PM -0600, Anthony Liguori wrote:> This is a great patch, I just want to make sure everyone who has written > a tool against xm that is perhaps screen scrapping the output of xm > block-list or xm network-list that the interface has changed. > > You will now have to use --long to get the same S-Expression output.Your concern is perfectly reasonable. On that note though, could I emphasise a) Screen-scraping xm is a bad idea. There is an interface straight into xend that one can use for integration (the same interface that xm uses). This will avoid such hackery, and make it an awful lot easier to maintain backwards compatibility. xm is for humans to use, not tools. b) There is no guarantee that any interface inside domain 0, be it to the tools, or even to Xen, are fixed. The only interfaces that are fixed at the moment are the interfaces used by guests. Everything else is subject to change at any time. Of course, it''s in everyone''s interests that these interfaces become fixed in the future, but there''s plenty of work that has to go into them yet before we could claim that they are supportable in the long term.> Perhaps this sort of changes should be announced on xen-announce in the > future? Is there such a list?That list is xen-devel, for the moment. I''m not sure there''s any value in having a separate list -- anyone who''s developing products that sit on top of Xen _really_ needs to be reading xen-devel anyway -- the project simply isn''t mature enough for you to get away without doing that. Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ewan Mellor wrote:> Your concern is perfectly reasonable. On that note though, could I > emphasise > > a) Screen-scraping xm is a bad idea. There is an interface straight > into xend that one can use for integration (the same interface that xm > uses). This will avoid such hackery, and make it an awful lot easier > to maintain backwards compatibility. xm is for humans to use, not > tools. >I agree with you completely and will take the time to point out that libvirt uses the S-Expression/HTTP interface so you can just use that :-)> b) There is no guarantee that any interface inside domain 0, be it > to the tools, or even to Xen, are fixed. The only interfaces that are fixed > at the moment are the interfaces used by guests. Everything else is > subject to change at any time. Of course, it''s in everyone''s > interests that these interfaces become fixed in the future, but > there''s plenty of work that has to go into them yet before we could > claim that they are supportable in the long term. >Yup.> That list is xen-devel, for the moment. I''m not sure there''s any value > in having a separate list -- anyone who''s developing products that sit > on top of Xen _really_ needs to be reading xen-devel anyway -- the > project simply isn''t mature enough for you to get away without doing > that. >Ok. Always good to reiterate this occasionally :-) Regards, Anthony Liguori> Ewan. > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ewan Mellor wrote:>>Perhaps this sort of changes should be announced on xen-announce in the >>future? Is there such a list? > > > That list is xen-devel, for the moment. I''m not sure there''s any value > in having a separate list -- anyone who''s developing products that sit > on top of Xen _really_ needs to be reading xen-devel anyway -- the > project simply isn''t mature enough for you to get away without doing > that.Heavily seconded. Please don''t fork mailing lists - it really isn''t warranted, and tends to exaggerate the problem we''re trying to solve (people not seeing the information they need because it''s hidden somewhere)... thanks, Nivedita _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel