Bug 523639
| Summary: | Feature request: Add a description field to <domain> | ||
|---|---|---|---|
| Product: | [Community] Virtualization Tools | Reporter: | Rubin Simons <me> |
| Component: | libvirt | Assignee: | Daniel Veillard <veillard> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | unspecified | CC: | berrange, crobinso, xen-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://libvirt.org/formatdomain.html#elements | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-11-26 15:15:54 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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 Small patch posted upstream: https://www.redhat.com/archives/libvir-list/2009-September/msg00911.html Daniel Fixed in 0.7.4 release |
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.