Bug 1505333

Summary:	Put VM libvirt XML to OVF store alongside the OVF configuration
Product:	[oVirt] ovirt-engine	Reporter:	Martin Sivák <msivak>
Component:	BLL.Virt	Assignee:	Arik <ahadas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Artyom <alukiano>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	ahadas, amureini, bugs, mlipchuk, tjelinek, tnisan
Target Milestone:	ovirt-4.2.2	Keywords:	Triaged
Target Release:	---	Flags:	rule-engine: ovirt-4.2+ rule-engine: ovirt-4.3+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-29 11:08:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1504606

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.