Skip to content

Commit 931e02b

Browse files
sipastaksipastak
committed
create a scaling plan steps
1 parent 016bd26 commit 931e02b

File tree

1 file changed

+100
-108
lines changed

1 file changed

+100
-108
lines changed

‎articles/virtual-desktop/autoscale-scaling-plan.md

Lines changed: 100 additions & 108 deletions
Original file line numberDiff line numberDiff line change
@@ -71,125 +71,117 @@ Now that you've assigned the *Desktop Virtualization Power On Off Contributor* r
7171
>- Though an exclusion tag will exclude the tagged VM from power management scaling operations, tagged VMs will still be considered as part of the calculation of the minimum percentage of hosts.
7272
>- Make sure not to include any sensitive information in the exclusion tags such as user principal names or other personally identifiable information.
7373
74-
1. Select **Next**, which should take you to the **Schedules** tab.
74+
1. Select **Next**, which should take you to the **Schedules** tab. Schedules let you define when autoscale turns VMs on and off throughout the day. The schedule parameters are different based on the **Host pool type** you chose for the scaling plan.
7575

76-
## Configure a schedule
76+
#### [Pooled host pools](#tab/pooled-autoscale)
7777

78-
Schedules let you define when autoscale turns VMs on and off throughout the day. The schedule parameters are different based on the **Host pool type** you chose for the scaling plan.
79-
80-
#### [Pooled host pools](#tab/pooled-autoscale)
81-
82-
In each phase of the schedule, autoscale only turns off VMs when in doing so the used host pool capacity won't exceed the capacity threshold. The default values you'll see when you try to create a schedule are the suggested values for weekdays, but you can change them as needed.
83-
84-
To create or change a schedule:
85-
86-
1. In the **Schedules** tab, select **Add schedule**.
87-
88-
1. Enter a name for your schedule into the **Schedule name** field.
89-
90-
1. In the **Repeat on** field, select which days your schedule will repeat on.
91-
92-
1. In the **Ramp up** tab, fill out the following fields:
93-
94-
- For **Start time**, select a time from the drop-down menu to start preparing VMs for peak business hours.
95-
96-
- For **Load balancing algorithm**, we recommend selecting **breadth-first algorithm**. Breadth-first load balancing will distribute users across existing VMs to keep access times fast.
78+
In each phase of the schedule, autoscale only turns off VMs when in doing so the used host pool capacity won't exceed the capacity threshold. The default values you'll see when you try to create a schedule are the suggested values for weekdays, but you can change them as needed.
79+
80+
To create or change a schedule:
81+
82+
1. In the **Schedules** tab, select **Add schedule**.
83+
84+
1. Enter a name for your schedule into the **Schedule name** field.
85+
86+
1. In the **Repeat on** field, select which days your schedule will repeat on.
87+
88+
1. In the **Ramp up** tab, fill out the following fields:
89+
90+
- For **Start time**, select a time from the drop-down menu to start preparing VMs for peak business hours.
91+
92+
- For **Load balancing algorithm**, we recommend selecting **breadth-first algorithm**. Breadth-first load balancing will distribute users across existing VMs to keep access times fast.
93+
94+
>[!NOTE]
95+
>The load balancing preference you select here will override the one you selected for your original host pool settings.
96+
97+
- For **Minimum percentage of hosts**, enter the percentage of session hosts you want to always remain on in this phase. If the percentage you enter isn't a whole number, it's rounded up to the nearest whole number. For example, in a host pool of seven session hosts, if you set the minimum percentage of hosts during ramp-up hours to **10%**, one VM will always stay on during ramp-up hours, and it won't be turned off by autoscale.
9798

98-
>[!NOTE]
99-
>The load balancing preference you select here will override the one you selected for your original host pool settings.
100-
101-
- For **Minimum percentage of hosts**, enter the percentage of session hosts you want to always remain on in this phase. If the percentage you enter isn't a whole number, it's rounded up to the nearest whole number. For example, in a host pool of seven session hosts, if you set the minimum percentage of hosts during ramp-up hours to **10%**, one VM will always stay on during ramp-up hours, and it won't be turned off by autoscale.
99+
- For **Capacity threshold**, enter the percentage of available host pool capacity that will trigger a scaling action to take place. For example, if two session hosts in the host pool with a max session limit of 20 are turned on, the available host pool capacity is 40. If you set the capacity threshold to **75%** and the session hosts have more than 30 user sessions, autoscale will turn on a third session host. This will then change the available host pool capacity from 40 to 60.
102100

103-
- For **Capacity threshold**, enter the percentage of available host pool capacity that will trigger a scaling action to take place. For example, if two session hosts in the host pool with a max session limit of 20 are turned on, the available host pool capacity is 40. If you set the capacity threshold to **75%** and the session hosts have more than 30 user sessions, autoscale will turn on a third session host. This will then change the available host pool capacity from 40 to 60.
104-
105-
1. In the **Peak hours** tab, fill out the following fields:
106-
107-
- For **Start time**, enter a start time for when your usage rate is highest during the day. Make sure the time is in the same time zone you specified for your scaling plan. This time is also the end time for the ramp-up phase.
108-
109-
- For **Load balancing**, you can select either breadth-first or depth-first load balancing. Breadth-first load balancing distributes new user sessions across all available session hosts in the host pool. Depth-first load balancing distributes new sessions to any available session host with the highest number of connections that hasn't reached its session limit yet. For more information about load-balancing types, see [Configure the Azure Virtual Desktop load-balancing method](configure-host-pool-load-balancing.md).
110-
111-
> [!NOTE]
112-
> You can't change the capacity threshold here. Instead, the setting you entered in **Ramp-up** will carry over to this setting.
113-
114-
- For **Ramp-down**, you'll enter values into similar fields to **Ramp-up**, but this time it will be for when your host pool usage drops off. This will include the following fields:
115-
116-
- Start time
117-
- Load-balancing algorithm
118-
- Minimum percentage of hosts (%)
119-
- Capacity threshold (%)
120-
- Force logoff users
121-
122-
> [!IMPORTANT]
123-
> - If you've enabled autoscale to force users to sign out during ramp-down, the feature will choose the session host with the lowest number of user sessions to shut down. Autoscale will put the session host in drain mode, send all active user sessions a notification telling them they'll be signed out, and then sign out all users after the specified wait time is over. After autoscale signs out all user sessions, it then deallocates the VM. If you haven't enabled forced sign out during ramp-down, session hosts with no active or disconnected sessions will be deallocated.
124-
> - During ramp-down, autoscale will only shut down VMs if all existing user sessions in the host pool can be consolidated to fewer VMs without exceeding the capacity threshold.
125-
126-
- Likewise, **Off-peak hours** works the same way as **Peak hours**:
127-
128-
- Start time, which is also the end of the ramp-down period.
129-
- Load-balancing algorithm. We recommend choosing **depth-first** to gradually reduce the number of session hosts based on sessions on each VM.
130-
- Just like peak hours, you can't configure the capacity threshold here. Instead, the value you entered in **Ramp-down** will carry over.
131-
132-
#### [Personal host pools](#tab/personal-autoscale)
133-
134-
In each phase of the schedule, define whether VMs should be deallocated based on the user session state.
135-
136-
To create or change a schedule:
137-
138-
1. In the **Schedules** tab, select **Add schedule**.
139-
140-
1. Enter a name for your schedule into the **Schedule name** field.
141-
142-
1. In the **Repeat on** field, select which days your schedule will repeat on.
143-
144-
1. In the **Ramp up** tab, fill out the following fields:
145-
146-
- For **Start time**, select the time you want the ramp-up phase to start from the drop-down menu.
101+
1. In the **Peak hours** tab, fill out the following fields:
147102

148-
- For **Start VM on Connect**, select whether you want Start VM on Connect to be enabled during ramp up.
149-
150-
- For **VMs to start**, select whether you want only personal desktops that have a user assigned to them at the start time to be started, you want all personal desktops in the host pool (regardless of user assignment) to be started, or you want no personal desktops in the pool to be started.
151-
152-
> [!NOTE]
153-
> We highly recommend that you enable Start VM on Connect if you choose not to start your VMs during the ramp-up phase.
154-
155-
- For **When disconnected for**, specify the number of minutes a user session has to be disconnected before performing a specific action. This number can be anywhere between 0 and 360.
156-
157-
- For **Perform**, specify what action the service should take after a user session has been disconnected for the specified time. The options are to either deallocate (shut down) the VMs, hibernate the personal desktop, or do nothing.
158-
159-
- For **When logged off for**, specify the number of minutes a user session has to be logged off before performing a specific action. This number can be anywhere between 0 and 360.
160-
161-
- For **Perform**, specify what action the service should take after a user session has been logged off for the specified time. The options are to either deallocate (shut down) the VMs, hibernate the personal desktop, or do nothing.
162-
163-
1. In the **Peak hours**, **Ramp-down**, and **Off-peak hours** tabs, fill out the following fields:
164-
165-
- For **Start time**, enter a start time for each phase. This time is also the end time for the previous phase.
103+
- For **Start time**, enter a start time for when your usage rate is highest during the day. Make sure the time is in the same time zone you specified for your scaling plan. This time is also the end time for the ramp-up phase.
166104

167-
- For **Start VM on Connect**, select whether you want to enable Start VM on Connect to be enabled during that phase.
168-
169-
- For **When disconnected for**, specify the number of minutes a user session has to be disconnected before performing a specific action. This number can be anywhere between 0 and 360.
170-
171-
- For **Perform**, specify what action should be performed after a user session has been disconnected for the specified time. The options are to either deallocate (shut down) the VMs, hibernate the personal desktop, or do nothing.
172-
173-
- For **When logged off for**, specify the number of minutes a user session has to be logged off before performing a specific action. This number can be anywhere between 0 and 360.
174-
175-
- For **Perform**, specify what action should be performed after a user session has been logged off for the specified time. The options are to either deallocate (shut down) the VMs, hibernate the personal desktop, or do nothing.
176-
---
177-
178-
## Assign host pools
179-
180-
Now that you've set up your scaling plan, it's time to assign the plan to your host pools. Select the check box next to each host pool you want to include. If you don't want to enable autoscale, unselect all check boxes. You can always return to this setting later and change it. You can only assign the scaling plan to host pools that match the host pool type specified in the plan.
105+
- For **Load balancing**, you can select either breadth-first or depth-first load balancing. Breadth-first load balancing distributes new user sessions across all available session hosts in the host pool. Depth-first load balancing distributes new sessions to any available session host with the highest number of connections that hasn't reached its session limit yet. For more information about load-balancing types, see [Configure the Azure Virtual Desktop load-balancing method](configure-host-pool-load-balancing.md).
106+
107+
> [!NOTE]
108+
> You can't change the capacity threshold here. Instead, the setting you entered in **Ramp-up** will carry over to this setting.
109+
110+
- For **Ramp-down**, you'll enter values into similar fields to **Ramp-up**, but this time it will be for when your host pool usage drops off. This will include the following fields:
111+
112+
- Start time
113+
- Load-balancing algorithm
114+
- Minimum percentage of hosts (%)
115+
- Capacity threshold (%)
116+
- Force logoff users
117+
118+
> [!IMPORTANT]
119+
> - If you've enabled autoscale to force users to sign out during ramp-down, the feature will choose the session host with the lowest number of user sessions to shut down. Autoscale will put the session host in drain mode, send all active user sessions a notification telling them they'll be signed out, and then sign out all users after the specified wait time is over. After autoscale signs out all user sessions, it then deallocates the VM. If you haven't enabled forced sign out during ramp-down, session hosts with no active or disconnected sessions will be deallocated.
120+
> - During ramp-down, autoscale will only shut down VMs if all existing user sessions in the host pool can be consolidated to fewer VMs without exceeding the capacity threshold.
121+
122+
- Likewise, **Off-peak hours** works the same way as **Peak hours**:
123+
124+
- Start time, which is also the end of the ramp-down period.
125+
- Load-balancing algorithm. We recommend choosing **depth-first** to gradually reduce the number of session hosts based on sessions on each VM.
126+
- Just like peak hours, you can't configure the capacity threshold here. Instead, the value you entered in **Ramp-down** will carry over.
127+
128+
#### [Personal host pools](#tab/personal-autoscale)
129+
130+
In each phase of the schedule, define whether VMs should be deallocated based on the user session state.
131+
132+
To create or change a schedule:
133+
134+
1. In the **Schedules** tab, select **Add schedule**.
135+
136+
1. Enter a name for your schedule into the **Schedule name** field.
137+
138+
1. In the **Repeat on** field, select which days your schedule will repeat on.
139+
140+
1. In the **Ramp up** tab, fill out the following fields:
141+
142+
- For **Start time**, select the time you want the ramp-up phase to start from the drop-down menu.
143+
144+
- For **Start VM on Connect**, select whether you want Start VM on Connect to be enabled during ramp up.
145+
146+
- For **VMs to start**, select whether you want only personal desktops that have a user assigned to them at the start time to be started, you want all personal desktops in the host pool (regardless of user assignment) to be started, or you want no personal desktops in the pool to be started.
147+
148+
> [!NOTE]
149+
> We highly recommend that you enable Start VM on Connect if you choose not to start your VMs during the ramp-up phase.
150+
151+
- For **When disconnected for**, specify the number of minutes a user session has to be disconnected before performing a specific action. This number can be anywhere between 0 and 360.
152+
153+
- For **Perform**, specify what action the service should take after a user session has been disconnected for the specified time. The options are to either deallocate (shut down) the VMs, hibernate the personal desktop, or do nothing.
154+
155+
- For **When logged off for**, specify the number of minutes a user session has to be logged off before performing a specific action. This number can be anywhere between 0 and 360.
156+
157+
- For **Perform**, specify what action the service should take after a user session has been logged off for the specified time. The options are to either deallocate (shut down) the VMs, hibernate the personal desktop, or do nothing.
158+
159+
1. In the **Peak hours**, **Ramp-down**, and **Off-peak hours** tabs, fill out the following fields:
160+
161+
- For **Start time**, enter a start time for each phase. This time is also the end time for the previous phase.
162+
163+
- For **Start VM on Connect**, select whether you want to enable Start VM on Connect to be enabled during that phase.
164+
165+
- For **When disconnected for**, specify the number of minutes a user session has to be disconnected before performing a specific action. This number can be anywhere between 0 and 360.
166+
167+
- For **Perform**, specify what action should be performed after a user session has been disconnected for the specified time. The options are to either deallocate (shut down) the VMs, hibernate the personal desktop, or do nothing.
168+
169+
- For **When logged off for**, specify the number of minutes a user session has to be logged off before performing a specific action. This number can be anywhere between 0 and 360.
170+
171+
- For **Perform**, specify what action should be performed after a user session has been logged off for the specified time. The options are to either deallocate (shut down) the VMs, hibernate the personal desktop, or do nothing.
172+
---
181173

182-
> [!NOTE]
183-
> - When you create or update a scaling plan that's already assigned to host pools, its changes will be applied immediately.
174+
1. Select **Next** to take you to the **Host pool assignments** tab. Select the check box next to each host pool you want to include. If you don't want to enable autoscale, unselect all check boxes. You can always return to this setting later and change it. You can only assign the scaling plan to host pools that match the host pool type specified in the plan.
184175

185-
## Add tags
176+
> [!NOTE]
177+
> - When you create or update a scaling plan that's already assigned to host pools, its changes will be applied immediately.
186178
187-
After that, you'll need to enter tags. Tags are name and value pairs that categorize resources for consolidated billing. You can apply the same tag to multiple resources and resource groups. To learn more about tagging resources, see [Use tags to organize your Azure resources](../azure-resource-manager/management/tag-resources.md).
179+
1. After that, you'll need to enter **tags**. Tags are name and value pairs that categorize resources for consolidated billing. You can apply the same tag to multiple resources and resource groups. To learn more about tagging resources, see [Use tags to organize your Azure resources](../azure-resource-manager/management/tag-resources.md).
188180

189-
> [!NOTE]
190-
> If you change resource settings on other tabs after creating tags, your tags will be automatically updated.
181+
> [!NOTE]
182+
> If you change resource settings on other tabs after creating tags, your tags will be automatically updated.
191183
192-
Once you're done, go to the **Review + create** tab and select **Create** to deploy your host pool.
184+
1. Once you're done, go to the **Review + create** tab and select **Create** to deploy your host pool.
193185

194186
## Edit an existing scaling plan
195187

0 commit comments

Comments
 (0)