Feature #718
Users should not be able to manually deploy VMs
| Status: | Closed | Start date: | 07/13/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Carlos Martín | % Done: | 100% | |
| Category: | Core & System | |||
| Target version: | Release 3.0 | |||
| Resolution: | fixed | Pull request: |
Description
Right now, the scheduler decides to deploy a VM in a Host for which the owner User has USE rights.
This makes possible for the user to issue a 'onevm deploy' and bypass the scheduler.
We may have to come up with another authorization request, or even create a new DEPLOY action.
Associated revisions
Feature #718: Add new DEPLOY authorization operation in core
Feature #718: Add new DEPLOY operation in Ruby OCA and CLI
Feature #718: Add new DEPLOY operation in Java OCA
feature #718: Changed column name for deploy 'd'->'Y'
feature #718: Change operation for deploy and migrate actions to DEPLOY
History
#1
Updated by Ruben S. Montero almost 10 years ago
- Tracker changed from Bug to Feature
#2
Updated by Ruben S. Montero almost 10 years ago
- Status changed from New to Assigned
- Target version set to Release 3.0
This issue needs to update:
- OpenNebula core to handle the new auth operation
- ACL command to include the new DEPLOY action (tables, command output, auth strings...)
- Ozones server when VDCs are created
- Sunstone ACL plugin to include the new op.
#3
Updated by Carlos Martín almost 10 years ago
- % Done changed from 0 to 80
We still need to update the documentation and sunstone
#4
Updated by Carlos Martín almost 10 years ago
- % Done changed from 80 to 100
#5
Updated by Carlos Martín almost 10 years ago
- Status changed from Assigned to Closed
- Resolution set to fixed