Problem
We use the Stopped OS disk type functionality in our auto-scale configurations to reduce storage costs while session hosts are stopped. In our case, stopped hosts use Standard HDD and running hosts use Premium SSD.
When running a script against a host pool, Nerdio automatically powers on stopped hosts so the script can be executed. However, these hosts are started using their current stopped disk type. The configured Running OS disk type is not applied because the power-on is part of the script job rather than an auto-scale action.
As a result, scripts can take significantly longer to complete on hosts that are started using a lower-performance stopped disk type.
Description
It would be useful if Nerdio could optionally apply the configured Running OS disk type when a stopped host is powered on for a scripted action or other management task.
This would allow customers to continue using a cheaper disk type for stopped hosts without affecting the performance of maintenance tasks that require Nerdio to temporarily start those hosts.
Vision
When starting a stopped host as part of a script job, Nerdio could check the auto-scale configuration for the host pool.
If a Running OS disk type is configured, Nerdio could:
1. Change the OS disk to the configured Running OS disk type.
2. Start the session host.
3. Run the requested script.
4. Stop the host again when required by the job.
5. Return the OS disk to the configured Stopped OS disk type.
Alternatively, an option could be added to the Run script dialog, for example: ‘Apply configured Running OS disk type before starting stopped hosts’
This could be optional so existing behavior remains available for customers who do not need the disk conversion.
Ideally, the same logic could also apply to other Nerdio management actions that temporarily power on a stopped session host outside of the normal auto-scale process.
Comments (0 comments)