You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the teardown process of VMs would benefit from an option to shutdown the OpenStack Machine before deleting it. This way it would be possible to benefit from teardown process in the VMs itself. Myself encountered this problem with NVIDIA licensees, which are borrowed on VM startup, but never properly released, because the Service on the VM was never stopped properly and therefore had no chance of releasing the license.
I think on way of implementing this, would be to add something like an waitForShutdown to the OpenStackMachine CRD. It could be defaulted to 0s to keep the old behavior and it would be a single configuration to have the possibility to let the VM properly shutdown and have a timeout for the shutdown, so that it does not hang forever in an error case.
If you are interested in such a feature, I would be happy to help implementing it.
The text was updated successfully, but these errors were encountered:
/kind feature
Describe the solution you'd like
I think the teardown process of VMs would benefit from an option to shutdown the OpenStack Machine before deleting it. This way it would be possible to benefit from teardown process in the VMs itself. Myself encountered this problem with NVIDIA licensees, which are
borrowed
on VM startup, but never properly released, because the Service on the VM was never stopped properly and therefore had no chance of releasing the license.I think on way of implementing this, would be to add something like an
waitForShutdown
to the OpenStackMachine CRD. It could be defaulted to0s
to keep the old behavior and it would be a single configuration to have the possibility to let the VM properly shutdown and have a timeout for the shutdown, so that it does not hang forever in an error case.If you are interested in such a feature, I would be happy to help implementing it.
The text was updated successfully, but these errors were encountered: