Hi Daniel,
With the new LDoms release (LDoms 1.1), we plan to provide a more
generic XML format which will be using the OVF (Open Virtual Machine
Format) spec:
http://www.vmware.com/pdf/ovf_spec_draft.pdf
Even though the OVF spec is still in the Draft stage, it can be
the hypervisor independent XML format for virtual machines.
I am wondering if it is in your radar or have any plan to move
forward to using more generic XML format.
For LDoms Manager, we will support the backward compatibility with
the current LDoms XML format since other tools/applications are still
using the current XML format. But, for the ldoms libvirt patch, would it
be the acceptable format if we use the OVF-style XML format?
Thanks,
Eunice
Daniel Veillard wrote:
On Thu, Apr 10, 2008 at 04:10:02PM -0500, Eunice Moon wrote:
Hi,
As John mentioned, the LDoms Manager (ldm) XML interface has been
used by a different set of software such as SNMP MIB, BUI, and other
tools/applications (before the libvirt), so we can't really change
the ldm XML formats.
I understood the existing format comes from other legacy uses,
no problem for me, looking at the second XML example made that clear :-)
But, I will look into the way (conversion between the LDoms XML
and libvirt XML formats) to make it compatible with the official
libvirt.
I can give an hand, it's probably also a good opportunity to refactor
a lot of the XML handling code coming from the patch since we will have
to change the way things are done. The hardest for me is understand the
semantic of the current document, we need this anyway to find how to best
map things onto the libvirt XML format (and back). Then for the revamp of
the conversion code i can probably do part of it, and probably faster than
you considering expertise on libxml2 ;-)
But I really need a good description of the current XML format,
Daniel
--
Libvir-list mailing list
Libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list