When we shut down a host, it gives us the option to Restrict autoscale operations for (hours).
Are we able to do that same task as a scripted action so we can utilize it when provisioning hosts?
When we shut down a host, it gives us the option to Restrict autoscale operations for (hours).
Are we able to do that same task as a scripted action so we can utilize it when provisioning hosts?
Hi Dave. We recently added the ability to deploy newly added hosts in Drain mode. This can be done by manually adding a new host to an existing host pool:
Having an additional Scripted Action to enable or disable Drain mode, would that bring additional use cases?
Thanks, Gido Veekens. I saw that yesterday for manually added hosts, but it doesn't look like it's an option for Auto-Scale provisioned hosts. If it was part of the Host Pool Properties or a scripted action, it would work for our immediate need. However, I see the scripted action being more versatile as we could utilize it in our scripted maintenance tasks.
The challenge with implementing a similar feature for auto-scale provisioned host and deploying them in Drain mode is that it tends to break the expected behavior for the auto-scaling feature when using burst capacity. Let's say you hit a capacity threshold and auto-scale deploys a new session host in Drain mode. The VM will be deployed successfully, but no user is able to take advantage of the new resource capacity, while it does burn money.
Glad you like the Scripted Actions, I agree it gives you more flexibility. I'll add it to our backlog.
Please sign in to leave a comment.
Comments (3 comments)