Backlog #2412

Ability to lock VM from accidental actions

Added by Andrey Perminov over 7 years ago. Updated almost 4 years ago.

Status:PendingStart date:10/25/2013
Priority:HighDue date:
Assignee:-% Done:

0%

Category:Core & System
Target version:-

Description

It would be nice to have an ability to lock a VM to prevent it from accidential deletion / alternation.

Related issues

Related to Request #2668: No confirmation for VM snapshot Revert/Delete Closed 01/22/2014
Related to Request #2670: confirmation question for onevm delete command Closed 01/22/2014
Related to Backlog #3909: Expose advisory locks for VM, consider them in VM operations Pending 08/03/2015
Duplicated by Request #3682: New state for VM machines -- "LOCKED" Closed 03/16/2015

History

#1 Updated by Ruben S. Montero over 7 years ago

  • Tracker changed from Request to Backlog

Thanks for the suggestion!

#2 Updated by Ruben S. Montero over 7 years ago

  • Priority changed from Low to Normal

#3 Updated by Ruben S. Montero over 7 years ago

Also, as suggested by Ricardo Duarte in the list:

"One feature I would like to see would be a "recycle bin".
Instead of deleting instances and their disks immediately after they terminate you could delay the actual operation to a different time, and allow the user to recover the instance."

Although the implementation is different the goal is the same, do not accidentally lose VMs.

#4 Updated by Andrey Perminov over 7 years ago

I think that locking should lock it from all operations, may be with exception to boot, reboot, poweroff. No alternation, no shutdown, no redeploy.

#5 Updated by Ruben S. Montero over 7 years ago

  • Related to Request #2668: No confirmation for VM snapshot Revert/Delete added

#6 Updated by Ruben S. Montero over 7 years ago

  • Priority changed from Normal to High

Also adding to this request #2668:

No confirmation was asked when VM snapshots is deleted/reverted.

If we lock the VM, also the snapshots would be deleted.

#7 Updated by Ruben S. Montero over 7 years ago

Seems this is being popular lately. A similar request from #2670:

We, FermiCloud have been using onevm delete in a different way
by asking for user's confirmation
since one user accidentally deleted a VM that was not meant to be deleted.
I thought this could be useful to others too.

Adding the issue as related to this one, to keep the discussion here.

#8 Updated by Ruben S. Montero over 7 years ago

  • Related to Request #2670: confirmation question for onevm delete command added

#9 Updated by Carlos Martín over 6 years ago

  • Duplicated by Request #3682: New state for VM machines -- "LOCKED" added

#10 Updated by Carlos Martín over 5 years ago

  • Related to Backlog #3909: Expose advisory locks for VM, consider them in VM operations added

#11 Updated by Sledge Sulaweyo almost 4 years ago

Just wanted to bump this request as i managed to kill an instance accidentally in my environment recently and would love to have an option to make sure this does not happen again. (Obviously my fault but a safety net would be great)

Also available in: Atom PDF