RHEV admin teams would benefit from a mechanism that asks for an optional reason when performing administrative actions on VMs: when a VM is shutdown/powered off from the mananger there's an optional "reason" field where the administrator can write a free-form explanation for the maintenance, which would be bought to attention in the logs and when/if someone attempts to power on. There's an equivalent request to do this for hosts in Bug 678977. Both are in addition to the change already implemented in Bug 610501 - this request is about RHEV-M explicitly asking for a reason or displaying a message in response to an action request.
Please mark if this is a requirement for a Genral/DC/Cluster or VM/Host level ? I mean where this should be set ? Once for all application objects In the DC for the whole DC etc.....
Eli, this configuration should be in cluster level as clusters are usually used to divide hosts based on functionality and importance.
My understanding is that the customer behind these requests is interested in the individual objects. This RFE was created as a spin-off of Bug 678977 specifically for VMs (see comment 9 in that BZ).
(In reply to Arthur Berezin from comment #2) > Eli, this configuration should be in cluster level as clusters are usually > used to divide hosts based on functionality and importance. Arthur, I think that the cluster isn't a place to store user configuration. I suggest to have that popup all the time... with a ignore checkbox, that be persisted at browser level. Are you okay with that? Thanks, Gilad
This RFE is asked for keeping reason of production VMs shutdown in events, and to retrieve shutdown reason later on/by another team member. It's not a user configuration. It is common to have production and non-production separation on cluster level (Production clusters, and non-production clusters for testing,qa, etc'), thus it should be configurable to require VM shutdown reason at cluster level, and each VM should be able to override the cluster setting. On new/edit cluster window under general tab should be a checkbox with "require VM shutdown reason", when set every VM should ask for reason upon shutdown.
- Is there any validation for the input? if no, user can simply leave it empty, so what is the point of enforcing/showing it, IMO that's annoying. - Means that the additional column in VM dialog for reason should be removed, VM grid can show only non-reason-ed VMs (already asked that from Ravi).
(In reply to Gilad Chaplik from comment #6) > - Is there any validation for the input? if no, user can simply leave it > empty, so what is the point of enforcing/showing it, IMO that's annoying. > - Means that the additional column in VM dialog for reason should be > removed, VM grid can show only non-reason-ed VMs (already asked that from > Ravi). We can check that it's not blank, Some enterprise have this as an organizational policy to keep record of production servers maintenances. Please elaborate on second bullet, not sure what you mean by that..
(In reply to Arthur Berezin from comment #7) > (In reply to Gilad Chaplik from comment #6) > > - Is there any validation for the input? if no, user can simply leave it > > empty, so what is the point of enforcing/showing it, IMO that's annoying. > > - Means that the additional column in VM dialog for reason should be > > removed, VM grid can show only non-reason-ed VMs (already asked that from > > Ravi). > > We can check that it's not blank, Some enterprise have this as an > organizational policy to keep record of production servers maintenances. = Validation on empty reason field? IMO can be risky and bug prone. > > Please elaborate on second bullet, not sure what you mean by that.. unify Reason column with Comment column in VM grid.
Is OK that only last reason is saved? I suppose it is as it is in vm_dynamic, right?
ok. ovirt-3.5-pre
Yes, only the last reason is saved in vm_dynamic
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-0158.html