Today we are going to discuss a recent customer scenario and what our solution was for them. In this case, the customer had very specific run time requirements, but also wanted to save as much money as possible.
Here were the requirements:
To meet this requirement, we used a combination of the Auto-Scaling and the Scheduler. The auto-scaling for the collection looked like this:
The schedule configuration looked like the following:
The Resources selected for the schedule are all of the session hosts in the collection that must be running during peak time during the week. This schedule setting will make sure all of the session hosts are running prior to the 8:00 am logon storm. Remember that the auto-scaler is not able to keep up with logon storms because it can take up to 10 minutes to start a session host. The other thing to keep in mind is that during the peak time defined within the auto-scaler, it will start VMs as needed, but will not shutdown any VMs. As a result, once VMs are started, the auto-scaler will shut them down at the end of peak time.
I agree that this is a bit of a work around, but the auto-scaler consistently works 7 days a week. Keep in mind, it is collection based. Unlike the auto-scaler, the scheduler is much more granular and can be based on time and specific VMs.
Want Future Best Practices Delivered Right to Your Inbox?