Re: [Libvir] [RFC]OpenVZ XML def

On Tue, Mar 13, 2007 at 10:57:23PM +0530, Shuveb Hussain wrote: Hi, Excellent news ! as fixed in second mail In general I expect we will need to do some exchanges over the format, first to try to get as much as possible something similar to the existing XML instances for the other engines like Xen and QEmu, and second to understand the ways in which OpenVZ is sufficiently different that it requires a change in markup. There are things a bit surprising: - vpsid: I assume it's an identifier for that domain, not as permanent as the UUID but which should be sufficient to designate a running domain, right ? If yes make it an id attribute in the top element domain as in the example at http://libvirt.org/format.html - profile: what is this ? shouldn't the associated informations actually be in the XML and not in some kind of config files (libvirt is being extended to be network aware, referencing a remote description would be a problem) - os: that's probably one place where OpenVZ may be quite different from Xen and QEmu, still what does the string 'slackware-10.2-i386-minimal' mean ? Is that a pointer to a file ? If yes shouldn't the associated content be in the XML instead For the networking <network> looks more like what Mark did in the last week, I would rather keep the same interfaces, however I'm suprized that you're not listing any device in the format, not even one for the network interface. So as-is the format is really too different from what I would expect, also the XML must be sufficient to fully describe a domain instance, so this will probably require some discussion to find out what is really needed in it :-) Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard(a)redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/