Custom states and operations for instances about squest HOT 4 CLOSED

Hi,
Sorry but an instance state is not related to the state of the backend object.
Even if stopped, in your case, the VM is still provisioned. So the instance is available.

States are part of a state machine which is hard coded by design. It's not possible to add or update state.

from squest.

I close this one.
You need to use day 2 operations and set your custom state in the instance specs.
You can also add a custom link in your instance that would propose to "start" or "stop" the VM.

Have fun with Squest !

from squest.

Hey,
By saying "custom states", do you refer to the edit menu of an instance and choosing an other state ?
According to your previous message, these states can't be edited and an instance state can't be updated with the Squest API, is that what you mean ?
Lastly, what do you mean by "custom link in your instance" ? Do you refer to the customizable support button ?

from squest.

No the "custom state" would be just a data placed into the instance spec. Nothing related to the real "Squest instance state" like "AVAILABLE".

Custom link doc here

Those links are then shown in the instance details page.
So you could have a button that show the current "custom state" of your VM like "Powered off". And the URL behind this button could point to a day 2 operations that power on the VM.

You could have one button named "Power on" with a when condition set to spec['vm_state'] == 'off' and another button named "Stop VM" with a when condition set to spec['vm_state'] == 'on'

from squest.