Changes

stoney conductor: VM States

486 bytes added, 09:03, 28 November 2013
| align="center" | (x) <ref name="RestrictionsRequired"/>
| align="center" | (x) <ref name="TechnicalClarificationNeeded"/>| align="center" | x <ref name="InterferencePossible"/>
| align="center" |
| align="center" | -
| align="center" | (x) <ref name="TechnicalClarificationNeeded"/> <ref name="UserCanTakeAction"/>
| align="center" | (x) <ref name="TechnicalClarificationNeeded"/>| align="center" | (x) <ref name="TechnicalClarificationNeeded"/>
| align="center" | (x) <ref name="RestrictionsRequired"/> <ref name="TechnicalClarificationNeeded"/>
| align="center" | (x) <ref name="TechnicalClarificationNeeded"/>| align="center" | x
| align="center" |
| align="left" | Running, migrating
| align="center" | -
| align="center" | (x) <ref name="TechnicalClarificationNeeded"/> <ref name="UserCanTakeAction"/>| align="center" | (x) <ref name="TechnicalClarificationNeeded"/>
| align="center" |
<ref name=RestrictionsRequired>Later. Function can be made available partially. For example: Editing the name, description or even IP of a VM may be always possible, while changing the memory and/or disk size depends heavily on the state of the VM.</ref>
<ref name="UserCanTakeAction">A user connected to the VM can take this action despite it is unavailable in the web-interface.</ref>
<ref name="InterferencePossible">While the action is possible, the result may not be satisfying, most probably due to race conditions.</ref>
</references>
[[Category:stoney conductor]][[Category: Lean Provisioning]]
Bureaucrat, administrator
425
edits