Bug 523639 - Feature request: Add a description field to <domain>
Summary: Feature request: Add a description field to <domain>
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: All
OS: All
low
low
Target Milestone: ---
Assignee: Daniel Veillard
QA Contact:
URL: http://libvirt.org/formatdomain.html#...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-16 09:37 UTC by Rubin Simons
Modified: 2010-03-16 17:23 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-11-26 15:15:54 UTC
Embargoed:


Attachments (Terms of Use)

Description Rubin Simons 2009-09-16 09:37:23 UTC
The current iteration of the libvirt XML formats' <domain> element has the following two metadata entries:

<name>
<uuid>

It would be very convenient to add a description metadata entry. This would allow people with a large amount of virtual machines to have a place to write some specifics about the machine like location or type of os, or other user-specific needs. It would look like:

<domain type='xen' id='1'>
        <name>foohost1</name>
        <uuid>4dea22b31d52d8f32516782e98ab3fa0</uuid>
        <description>The first foohost machine, production.</description>
</domain>

Applications like virt-manager could almost directly make use of this (adding it to the listing of VM's, thus making it sortable, making it editable from a VM's detail tab, etc). I also think this is relevant meta-data that currently has no way to be stored nicely within a VM's configuration.

Comment 1 Daniel Veillard 2009-09-30 10:07:16 UTC
Yup, I tend to think it's a good idea, the only problem is that those fields
need to be parsed, preserved and saved, but that's fine, I will look
at this,

Daniel

Comment 2 Daniel Veillard 2009-09-30 13:20:29 UTC
Small patch posted upstream:

https://www.redhat.com/archives/libvir-list/2009-September/msg00911.html

Daniel

Comment 3 Daniel Berrangé 2009-11-26 15:15:54 UTC
Fixed in 0.7.4 release


Note You need to log in before you can comment on or make changes to this bug.