On Wed, Apr 16, 2008 at 08:34:23AM -0400, Daniel Veillard wrote:
> want to be able to associate textual descriptions of the asset,
or
> define ownership. All of these are higher-level values that don't
> necessarily have any meaning to the v12n technology itself. More
> crucially they can be specific to the management tool, and lack any
> reasonable generalization.
Of course there is a need higher in the stack to associate metadata
with the domain instance, but the fact this can be put in the hypervisor
is a Xen specific as far as I can tell, and I'm reluctant to put this
Then this seems to be an argument for improving the other solutions not
crippling libvirt. Or at the very least providing a mechanism that won't
work on the other implementations, as happens with many libvirt
facilities already.
in the libvirt XML format, because this is not hypervisor domain
data,
and would break portability as far as I can tell.
What do you mean by "break portability" ?
regards
john