Bug #5201
libvirt 2.0 xml metadata
Status: | Pending | Start date: | 06/23/2017 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | Core & System | |||
Target version: | - | |||
Resolution: | Pull request: | |||
Affected Versions: | OpenNebula 5.2 |
Description
Not sure it is important or not
I upgraded node and now metadata section in xml is empty
Centos 7
before upgrade:
virsh dumpxml one-XXX ... <metadata> <system_datastore><![CDATA[/var/lib/one//datastores/XXX/XXX]]></system_datastore> </metadata> ... # virsh version Compiled against library: libvirt 1.2.17 Using library: libvirt 1.2.17 Using API: QEMU 1.2.17 Running hypervisor: QEMU 1.5.3
after upgrade:
# virsh dumpxml one-XXX ... <metadata/> ... # virsh version Compiled against library: libvirt 2.0.0 Using library: libvirt 2.0.0 Using API: QEMU 2.0.0 Running hypervisor: QEMU 2.6.0
History
#1 Updated by Javi Fontan almost 4 years ago
- Category set to Core & System
- Target version deleted (
Release 5.2.1)
A prefix must be added to all the tags in metadata.
#2 Updated by Stefan Kooman over 3 years ago
As discussed with Javi Fontan and Anton Todorov during the ONE EU CONF 2017: There is a clear need for metadata support in libvirt XML's created by OpenNebula. Especially the "NAME" of the virtual machine should be present in the libvirt XML. External tools (for example to do Disaster Recovery) can than make a mapping between ONE-ID and Name. Libvirt allows for Metadata to be added: https://libvirt.org/formatdomain.html#elementsMetadata
A mapping prooposal:
OpenNebula VM "NAME" => libvirt Title
OpenNebula VM Description => libvirt Description
OpenNebula VM Metadata => libvirt Metadata