On 01/24/2012 07:18 AM, Daniel Veillard wrote: > The idea is that currently we have only the domain name usable as > a description for the domain. It is not really a good human readable > identifier, as the kind of string allowed is limited (no space for > example). The idea would then be to extend the existing <description> > field in the domain XML to keep 40 or less character string to describe > a domain and provide that information later for example in an extended > virsh list command or for other interfaces. > While the idea is simple, see attached patch for this, it becomes more > complex when one tries to make accessors to set/get that title for a > domain, since it's mutable and possibly could be coming from the > hypervisor itself (is there anything like this in VMWare or VirtualBox?) > it should to be implemented down at the driver level. Is that worth the > effort ? If we go that route should we do this for other objects > (network, storage, etc ...) too in the end ? > > here is a basic patch for just the XML side to give an idea, but > adding APIs is far more work. > > Opinions ? Looks like this is more or less identical to Peter's proposal to add a <title> element: https://www.redhat.com/archives/libvir-list/2012-January/msg00710.html so I'm all for the idea (not sure whether your patch or Peter's is better for the idea). As far as I know, the title is _not_ coming from the hypervisor itself, nor is it guest-visible; it is merely metadata from the host's perspective. -- Eric Blake eblake@xxxxxxxxxx +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list