Extend Datalab Duration After Deployed

[msteffes]

is there a way to extend the time for a datalab after it is deployed. Lets say we deployed it for 4 hours and we decide we want to use it for another 4 hours is there a way in VAO, powershell or API we can extend the original time?

[Oleg Patrakov]

Hi Michael
There's no way to extend it. You can only shut it down and start with a different "Test and keep powered on" value.

[msteffes]

Can that be added as a feature request? I wouldn't think I would be the only one who would find this useful. Most of the time it is fine unless we are doing a actual DR test. It involves others setting up custom in house applications that isn't currently automated. If we run into snags and want to trouble shoot a little longer we will loose everything we has setup if it expires.

[Oleg Patrakov]

Michael, we'll consider it as a feature request. There hasn't been much ask for this particular one, but we'll investigate and see if it can fit the next release cycle.

[msteffes]

Thank you. Another option I was thinking about that would be helpful is having a way to run a script on the VAO server when the datalab is shutting down. We have a use case where we just change network adapters to the datalab network and reboot on a few machines at the DR to use in a DR test. We would like to automate switching the network adapters back to the production network when the datalab is powering off. The VMs are already at the DR location ready to go in a DR event we just need them in the datalab when doing a DR test and found it worked better to just switch the network adapters instead of using a clone.

[Alec King]

Hi Michael, Custom scripts during lab power-off is an interesting idea. We can add a 'post-lab' section in the UI, where you could add your own reconfiguration and clean-up scripts.
We'll take that into consideration for a future version.

Thanks for the feedback in Datalabs in VAO, we're always looking for new use cases for this functionality!