Difference between revisions of "stoney vm: Requirements"
From stoney cloud
| [unchecked revision] | [unchecked revision] |
(→Requirements) |
|||
| (6 intermediate revisions by one other user not shown) | |||
| Line 3: | Line 3: | ||
== Requirements == | == Requirements == | ||
| − | * A user can start, shut down, power off (was destroy) their own virtual machine(s). | + | * A user can start, shut down, power off (was destroy), reset (new, replicates power off + start but without the need to reconnect via spice) their own virtual machine(s). |
| − | * A user can access their own virtual machine(s) via spice. | + | * A user can access their own virtual machine(s) via spice with one time passwords. |
| + | * Status (running, stopped, ...), CPU(s), Memory size, Disk(s) with corresponding size | ||
| + | |||
| + | * What do we have to do where, to be able to change the ownership (reseller, customer and maybe person) of a virtual machine? | ||
| + | ** The vm-manager could be expanded in a fairly simple way to change the sstBelongsToResellerUID and sstBelongsToCustomerUID of the person. | ||
| + | ** Check, if this has an influence on the current vm-manager. | ||
| + | |||
| + | * Should we try and change the role "Admin Virtualization" to "Virtualization Admin" and "User" to "Virtualization User"? Yes. | ||
== Links == | == Links == | ||
Latest revision as of 10:58, 27 December 2013
Overview
Requirements
- A user can start, shut down, power off (was destroy), reset (new, replicates power off + start but without the need to reconnect via spice) their own virtual machine(s).
- A user can access their own virtual machine(s) via spice with one time passwords.
- Status (running, stopped, ...), CPU(s), Memory size, Disk(s) with corresponding size
- What do we have to do where, to be able to change the ownership (reseller, customer and maybe person) of a virtual machine?
- The vm-manager could be expanded in a fairly simple way to change the sstBelongsToResellerUID and sstBelongsToCustomerUID of the person.
- Check, if this has an influence on the current vm-manager.
- Should we try and change the role "Admin Virtualization" to "Virtualization Admin" and "User" to "Virtualization User"? Yes.
