Difference between revisions of "stoney conductor: VM States"
From stoney cloud
| [unchecked revision] | [unchecked revision] |
(→Virtual Machines) |
(→References) |
||
| Line 617: | Line 617: | ||
<ref name=TechnicalClarificationNeeded>Later. Should be implementable, but clarification needed on how it works.</ref> | <ref name=TechnicalClarificationNeeded>Later. Should be implementable, but clarification needed on how it works.</ref> | ||
<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=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 | + | <ref name="UserCanTakeAction">A user connected to the VM can take this action despite being 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> | <ref name="InterferencePossible">While the action is possible, the result may not be satisfying, most probably due to race conditions.</ref> | ||
</references> | </references> | ||
[[Category:stoney conductor]][[Category: Lean Provisioning]] | [[Category:stoney conductor]][[Category: Lean Provisioning]] | ||
Revision as of 09:50, 27 December 2013
Naming of VM states (the second state is only needed for special cases).
Virtual Machines
Naming of VM states (the second state is only needed for special cases), valid for VMs:
| No. | Status | Run Action | Action | Explanation | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Start | Shutdown | Power off | Migrate | Edit | Delete | Use | Users | Groups | |||
| 1 | Stopped | x | - | - | x | x | x | - | x | x | |
| 2 | Stopped, streaming [5.1 %] | x | - | - | (x) [1] | (x) [2] | (x) [1] | - | x | x | technically paused |
| 3 | Stopped, backing up | (x) [1] | - | - | (x) [1] | (x) [2] | (x) [1] | - | x | x | Technically merging, retaining or streaming (sstProvisioningMode). |
| 4 | Stopped, backing up | x | x | ||||||||
| 5 | Stopped, migrating | (x) [1] | - | - | - | (x) [1] | - | - | x | x | Same state for the vm being migrated to a node and away from a node. |
| 6 | Starting | - | - | - | - | (x) [2] | - | - | x | x | Technically changing state from stopped or paused to running. |
| 7 | Starting, streaming [5.1 %] | - | - | - | - | (x) [2] | - | - | x | x | |
| 8 | Paused, backing up | - | - | - | - | (x) [2] | - | - | x | x | technically migrating to file |
| 9 | Paused, migrating | - | - | - | - | (x) [2] | - | - | x | x | the vm is being migrated to this node |
| 10 | Running | - | x | x | x | (x) [2] | - | x | x | x | |
| 11 | Running, backing up | - | (x) [1] [3] | (x) [1] | (x) [1] | (x) [2] | (x) [1] | (x) [4] | x | x | Technically merging, retaining or streaming (sstProvisioningMode). |
| 12 | Running, streaming [5.1 %] | - | (x) [1] [3] | (x) [1] | (x) [1] | (x) [2] [1] | (x) [1] | x | x | x | |
| 13 | Running, migrating | - | (x) [1] [3] | (x) [1] | - | (x) [2] | (x) [1] | x | x | x | The vm is being migrated away from this node. |
| 14 | Shutting down | - | - | - | - | (x) [2] | - | - | x | x | |
| 15 | Powering off | - | - | - | - | (x) [2] | - | - | x | x | |
| 16 | Deleting | - | - | - | - | - | - | - | x | x | |
Possible future states:
- Crashed (when vm should be running, but there isn't a QEMU process around)
- Frozen or Non responding (requires QEMU guest agent or a watch dog)
Future editing:
- Certain values like disk, cpu and memory will be able to be changed, even if the vm is running.
Tool-Tips:
- "stopped, streaming (without the percent status)": Show streaming information with vm-name(s) and percent status.
- Save text of Tool-Tips in language files.
VM Templates
Naming of VM states (the second state is only needed for special cases), valid for VM Templates:
| No. | Status | Run Action | Action | Explanation | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| start | shutdown | destroy | migrate | edit | delete | toggle | use | persistent | dynamic | |||
| 1 | Stopped | x | x | x | x | x | x | x | ||||
| 2 | Stopped, streaming | After clicking "+" a list of all the vms (sstDisplayName) should appear with [5.1 %]. | ||||||||||
| 3 | Stopped, backing up | |||||||||||
| 4 | Stopped, migrating | Same state for the vm being migrated to a node and away from a node. | ||||||||||
| 5 | Stopped, first installation | If sstVirtualMachineMode is set to first installation. | ||||||||||
| 6 | Stopped, maintenance mode | If sstVirtualMachineMode is set to maintenance mode. | ||||||||||
| 7 | Starting | Technically changing state from stopped to running. | ||||||||||
| 8 | Paused, backing up | Technically migrating to file. | ||||||||||
| 9 | Paused, migrating | The vm is being migrated to this node. | ||||||||||
| 10 | Running | |||||||||||
| 11 | Running, backing up | Technically merging, retaining, streaming. | ||||||||||
| 12 | Running, migrating | The vm is being migrated away from this node. | ||||||||||
| 13 | Running, first installation | If sstVirtualMachineMode is set to first installation. | ||||||||||
| 14 | Running, maintenance mode | If sstVirtualMachineMode is set to maintenance mode. | ||||||||||
| 15 | Shutting down | |||||||||||
| 16 | Powering off | |||||||||||
| 17 | Deleting | |||||||||||
| 18 | Do not use | If sstVirtualMachineMode does not exist. | ||||||||||
References
- ↑ 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 1.18 Later. Should be implementable, but clarification needed on how it works.
- ↑ 2.00 2.01 2.02 2.03 2.04 2.05 2.06 2.07 2.08 2.09 2.10 2.11 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.
- ↑ 3.0 3.1 3.2 A user connected to the VM can take this action despite being unavailable in the web-interface.
- ↑ While the action is possible, the result may not be satisfying, most probably due to race conditions.
