Request #3682
New state for VM machines -- "LOCKED"
| Status: | Closed | Start date: | 03/16/2015 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | - | |||
| Pull request: |
Description
Would it be possible to include a new state "LOCKED" for Virtual Machine instances? This state would allow administrators (== members of the 'oneadmin' group) to temporarily prevent ordinary users from performing any actions on their virtual machine instances. It should cover all possible actions and state transitions available in OpenNebula, including scheduled actions. Administrators would still have the right to perform all available actions and state transitions, including LOCKing and unLOCKing virtual machine instances.
This feature would be useful for VM maintenance and cluster re-balancing tools/external schedulers moving VMs around without manual intervention.
Do you see this as something useful? Something you would consider implementing?
Thanks!
Related issues
History
#1
Updated by Carlos Martín over 6 years ago
- Status changed from Pending to Closed
Hi,
Yes it makes sense. But I will this one because we already have #2412.
Although I think it would be easier to have an absolute lock for everyone, instead of locking regular users only. The scheduler runs as the 'oneadmin' user, so it would be allowed to run the scheduled actions anyway...
#2
Updated by Carlos Martín over 6 years ago
- Duplicates Backlog #2412: Ability to lock VM from accidental actions added