Bug 1032930

Summary: [RFE] Add checkbox to "Power off and delete running VM immediatelly" to the web interface
Product: Red Hat Enterprise Virtualization Manager Reporter: Petr Spacek <pspacek>
Component: ovirt-engine-webadmin-portalAssignee: Nobody <nobody>
Status: CLOSED WONTFIX QA Contact: Pavel Stehlik <pstehlik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, ecohen, iheim, michal.skrivanek, pspacek, Rhev-m-bugs, sherold, yeylon
Target Milestone: ---Keywords: FutureFeature, Improvement
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-26 15:18:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1213937    
Attachments:
Description Flags
screenshot from web admin with the new checkbox none

Description Petr Spacek 2013-11-21 09:24:06 UTC
Created attachment 827090 [details]
screenshot from web admin with the new checkbox

Hello,

our team uses RHEV-M heavily for development and testing purposes so we create and delete a lot of VMs every day. The usual work flow is to create VM and start it immediately, so some experiments with it and then kill the VM and delete it forever.

There is some latency between click to "Power off" in list of VMs and the state "Down" (with red square icon) when the VM can be removed - this is very annoying.

I propose to add new check box to the "Remove Virtual Machine" dialog. The checkbox would allow you to power off and delete running VM as soon as possible, without waiting for "red square" icon. Waiting is especially painful on links with higher latency, like Brno<->Boston.

I'm attaching modified screenshot. Of course, the text from me is just random garbage, it could be whatever :-) 

Thank you and have a nice day.

Comment 1 Itamar Heim 2013-11-21 23:01:41 UTC
if you know you are launching a through away instance, common approach is to configure it with shutdown behavior of terminate/auto-delete, so when you shut it down, the engine will auto-delete it.

Comment 2 Itamar Heim 2013-11-21 23:02:33 UTC
note: related to bug 1032913 for "launch instance"

Comment 3 Petr Spacek 2013-11-22 08:58:03 UTC
(In reply to Itamar Heim from comment #1)
> if you know you are launching a through away instance, common approach is to
> configure it with shutdown behavior of terminate/auto-delete, so when you
> shut it down, the engine will auto-delete it.

That is interesting. Is it supported in RHEV 3.2.x? I can't find such check box in Web admin.

Comment 4 Itamar Heim 2013-11-22 09:13:32 UTC
I was commenting on the common approach for implementing this. didn't mean to imply it already exist.

Comment 5 Petr Spacek 2013-11-22 13:33:06 UTC
I thought about it a bit more and I think that the ability to ad-hoc "kill & remove" running VM from Web UI is still valuable.

The reason is that sometimes you don't know from the beginning if the VM will be long-lived or short-lived. E.g. if the throw-away property depends on some action inside running VM etc.

Real live example from yesterday:
I'm trying to reproduce a bug in an installer. So I create new VM from template, start it, run yum etc. and do installation with some magical parameters. The bug did appear so I need to remove the whole VM and start again.

On the other hand, if I managed to reproduce the bug, I don't want to delete the VM...

I hope that this explains the use case.

(May be that there is some better way how to implement my workflow :-)

Comment 6 Michal Skrivanek 2013-11-25 08:01:26 UTC
(In reply to Petr Spacek from comment #5)
> (May be that there is some better way how to implement my workflow :-)

Wouldn't it be better to use snapshots for this (just trying to think about your usecase)? You have a base OS with your app, you take a snapshot, try to reproduce the bug, didn't succeed -> revert, try in some different way, etc.

Otherwise I'd find it too dangerous to have such an option. Agree with the shutdown behavior if that's what you're doing all the time. Even inherit that from template so all VMs from that template would be deleted upon shutdown by default…but for your case of testing snapshots make most sense...

Comment 7 Petr Spacek 2013-11-25 08:44:24 UTC
May be :-) I will try it next time if I figure out the right workflow.

Thank you for your time!