Bug 1545980

Summary:	[Docs][RFE][VMM] Document the 'resume behavior' policy options
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Lucy Bopf <lbopf>
Component:	Documentation	Assignee:	Emma Heftman <eheftman>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Tahlia Richardson <trichard>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	4.2.0	CC:	lsurette, michal.skrivanek, mzamazal, rbalakri, srevivo, ykaul
Target Milestone:	ovirt-4.2.2	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	docs-accepted
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-11 15:31:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Docs	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1230788
Bug Blocks:

Description Lucy Bopf 2018-02-16 01:13:56 UTC

Previously, if a VM had been paused due to an IO Error, there was no way to configure what should happen after the storage gets fixed. The only option was "auto resume", which resumed the VM. This feature adds two more options configurable per VM: "Kill" and "Leave Paused".

Now the user can configure 3 resume policies for VMs:
- AUTO_RESUME
- LEAVE_PAUSED
- KILL

These options are available as 'Resume Behavior' in the New/Edit VM window, in the 'High Availability' tab, and must be documented.

The default still appears to be "auto resume".

Comment 1 Lucy Bopf 2018-02-16 01:25:34 UTC

Accepting into Beta 3 program and assigning to Emma for review.

Comment 17 Emma Heftman 2018-03-11 15:31:25 UTC

Updated documentation has been published and is available here:

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2-beta/html-single/virtual_machine_management_guide/#Configuring_a_highly_available_virtual_machine