stoney conductor: VM States

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) <ref name="TechnicalClarificationNeeded"/>	(x) <ref name="RestrictionsRequired"/>	(x) <ref name="TechnicalClarificationNeeded"/>				technically paused
3	Stopped, backing up	(x) <ref name="TechnicalClarificationNeeded"/>			(x) <ref name="TechnicalClarificationNeeded"/>	(x) <ref name="RestrictionsRequired"/>	(x) <ref name="TechnicalClarificationNeeded"/>				Technically merging, retaining or streaming (sstProvisioningMode).
4	Stopped, backing up
5	Stopped, migrating					(x) <ref name="TechnicalClarificationNeeded"/>					Same state for the vm being migrated to a node and away from a node.
6	Starting					(x) <ref name="RestrictionsRequired"/>					Technically changing state from stopped or paused to running.
7	Starting, streaming [5.1 %]					(x) <ref name="RestrictionsRequired"/>
8	Paused, backing up					(x) <ref name="RestrictionsRequired"/>					technically migrating to file
9	Paused, migrating					(x) <ref name="RestrictionsRequired"/>					the vm is being migrated to this node
10	Running					(x) <ref name="RestrictionsRequired"/>
11	Running, backing up	-				(x) <ref name="RestrictionsRequired"/>					Technically merging, retaining or streaming (sstProvisioningMode).
12	Running, streaming [5.1 %]	-	(x) <ref name="TechnicalClarificationNeeded"/> <ref name="UserCanTakeAction"/>			(x) <ref name="RestrictionsRequired"/> <ref name="TechnicalClarificationNeeded"/>
13	Running, migrating	-				(x) <ref name="RestrictionsRequired"/>	(x) <ref name="TechnicalClarificationNeeded"/>	x			The vm is being migrated away from this node.
14	Shutting down	-	-	-	-	(x) <ref name="RestrictionsRequired"/>	-	-
15	Powering off	-	-	-	-	(x) <ref name="RestrictionsRequired"/>	-	-
16	Deleting	-	-	-	-	-	-	-

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

<references> <ref name=LaterTechnicalClarificationNeeded>Later. Should be implementable, but clarification needed on how it works.</ref> <ref name=LaterRestrictionsRequired>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> </references>