Bug 1505333 - Put VM libvirt XML to OVF store alongside the OVF configuration
Summary: Put VM libvirt XML to OVF store alongside the OVF configuration
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.2.2
: ---
Assignee: Arik
QA Contact: Artyom
URL:
Whiteboard:
Depends On:
Blocks: 1504606
TreeView+ depends on / blocked
 
Reported: 2017-10-23 11:00 UTC by Martin Sivák
Modified: 2018-03-29 11:08 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-03-29 11:08:15 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: ovirt-4.3+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 86170 0 master MERGED core: make LibvirtVmXmlBuilder a stand-alone utility 2018-01-14 09:00:23 UTC
oVirt gerrit 86171 0 master MERGED core: no CDI for LibvirtVmXmlBuilder 2018-01-14 09:00:27 UTC
oVirt gerrit 86172 0 master MERGED core: store engine xml in ovf_store for hosted-engine 2018-01-16 18:43:22 UTC

Description Martin Sivák 2017-10-23 11:00:31 UTC 
Description of problem:

Hosted engine is currently parsing OVF and preparing VM.conf structure to start the VM. IT would be much better if we could use the new XML format VDSM supports for that.

But we need a way to get it from the host side when the engine VM is down and so a mechanism is needed to generate the XML upon VM edit and store it somewhere accessible from hosts. OVF store seems like a logical place, as we already have it and it is supposed to be a piece of disaster recovery plan.
Comment 1 Allon Mureinik 2017-10-24 06:04:14 UTC 
Is there a usecase to have this XML for any other VM, or just for HE?
Comment 2 Michal Skrivanek 2017-10-24 06:11:31 UTC 
Well, if it's done for all VMs it does open the possibility of being able to run it without the engine, assuming we can replicate the connectStorage state on host as well
Comment 3 Artyom 2018-02-19 22:26:19 UTC 
Verified on rhvm-4.2.2-0.1.el7.noarch
Comment 4 Sandro Bonazzola 2018-03-29 11:08:15 UTC 
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.