Actions contained in pause and stop buttons in sunstone instances layout
|Assignee:||Guillaume Oberlé||% Done:|
|Target version:||Release 5.0|
Many people in our team are confused about the location of the "stop", "poweroff" and "poweroff --hard" buttons in the current sunstone layout :
- The pause button currently includes "suspend", "poweroff" and "poweroff --hard". The problem is that "poweroff" and "poweroff --hard" does not reflect a pause state as we don't keep the state of the VM.
- The stop button currently includes "stop", "undeploy" and "undeploy --hard". Here, the problem is that "stop" does not reflect a pause state as we keep the state of the VM.
The proposal is to move "stop" in the pause button and "poweroff"/"poweroff --hard" in the stop button.
The logic behind this is that the actions contained in the pause buttons keep the state of the VM (on the host with suspend or in the system datastore with stop), and the action contained in the stop button doesn't keep the state of the VM (on the host with poweroff, poweroff --hard or in the system datastore with undeploy, undeploy --hard).@@
Bug #4498: Actions contained in pause and stop buttons in sunstone instances layout
#3 Updated by Carlos Martín about 5 years ago
I understand how it can be confusing, and we are going to discuss your proposal before 5.0 final.
Meanwhile, the rationale behind it was that poweroff and sunspend are a short-term pause, since the VMs are left allocated in the host. Undeploy and stop are long-term pauses because they free the VM resources, and when you try to resume these VMs the process may take longer, or even not finish if the hosts are full.