This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Getting started with Autoscale
Autoscale works at a delivery group level. It proactively power manages machines in a delivery group based on the schedules that you set.
Autoscale applies to all types of delivery groups:
- Single-session static OS
- Single-session random OS
- Multi-session random OS
Note:
Autoscale is enabled by default if you create or upgrade Delivery Groups using MMC-based Studio.
This article describes basic Autoscale-related concepts and provides guidance on how to enable and configure Autoscale for a delivery group.
Basic concepts
Before you start, learn about the following basic concepts in Autoscale:
Schedules
Autoscale powers on and off machines in a delivery group based on a schedule that you set.
A schedule includes the number of active machines for each time slot, with peak and off-peak times defined.
Schedule settings vary with the type of delivery group. For more information, see:
- Multi-session OS delivery groups
- Single-session OS random delivery groups
- Single-session OS static delivery groups
Capacity buffer
Capacity buffer is used to add spare capacity to the current demand to account for dynamic load increases. There are two scenarios to be aware of:
- For multi-session OS delivery groups, the capacity buffer is defined as a percentage of the total capacity of the delivery group in terms of load index.
- For single-session OS delivery groups, the capacity buffer is defined as a percentage of the total number of machines in the delivery group.
Load index
IMPORTANT:
Load index applies only to multi-session delivery groups.
The load index metric determines how likely a machine is to receive user logon requests. It’s calculated using the Citrix Load Management policy settings configured for concurrent logon, session, CPU, disk, and memory use.
The load index ranges from 0 to 10,000. By default, a machine is considered at full load when it’s hosting 250 sessions:
-
The digit “0” indicates an unloaded machine. A machine with a load index value of 0 is at a baseline load.
-
The digit “10,000” indicates a fully loaded machine that can’t run any more sessions.
Enable Autoscale for a delivery group
Autoscale is disabled by default when you create a delivery group. To enable and configure Autoscale for a delivery group using Web Studio, follow these steps:
You can also use PowerShell commands to enable and configure Autoscale for a delivery group. For more information, see Broker PowerShell SDK commands.
-
Select Delivery Groups in the left pane.
-
Select the delivery group that you want to manage and then click Manage Autoscale.
-
On the Manage Autoscale page, select the Enable Autoscale check box to enable Autoscale. After you enable Autoscale, the options on the page are enabled.
-
To change the default settings based on your organization’s needs, complete the following settings:
-
To power off inactive machines more efficiently, use Dynamic session timeouts and User logoff notifications
-
To power manage a subset of machines in the delivery group, use Autoscaling tagged machines
To disable Autoscale, clear the Autoscale check box. The options on the page turn gray to indicate that Autoscale is disabled for the selected delivery group.
Important:
- If you disable Autoscale, all machines managed by Autoscale remain in their states at the time of disabling.
- After you disable Autoscale, the machines in drain state are taken out of drain state. For more information about drain state, see Drain state.
Monitor metrics
After you enable Autoscale for a delivery group, you can monitor the following metrics of Autoscale-managed machines from Director.
-
Machine usage
-
Estimated savings
-
Alert notifications for machines and sessions
-
Machine status
-
Load evaluation trends
Note:
When you initially enable Autoscale for a delivery group, it might take a few minutes to display monitoring data for that delivery group. Monitoring data remains available if Autoscale is enabled and then disabled for the delivery group. Autoscale collects monitoring data at 5-minute intervals.
For more information about the metrics, see Monitor Autoscale-managed machines.
Good to know
Autoscale works at a delivery group level. It’s configured on a per-delivery group basis. It power manages only the machines in the selected delivery group.
Capacity and machine registration
Autoscale includes only machines that are registered with the site when determining the capacity. Powered-on machines that are unregistered can’t accept session requests. As a result, they aren’t included in the overall capacity of the delivery group.
Scaling across multiple machine catalogs
In some sites, multiple machine catalogs might be associated with a single delivery group. Autoscale randomly powers on machines from each catalog to meet schedule or session demand requirements.
For example, a delivery group has two machine catalogs: Catalog A has three machines powered on and Catalog B has one machine powered on. If Autoscale needs to power on an extra machine, it might power on a machine from either Catalog A or Catalog B.
Machine provisioning and session demand
The machine catalog associated with the delivery group must have enough machines to power on and off as demand increases and decreases. If session demand exceeds the total number of registered machines in the delivery group, Autoscale ensures that all registered machines are powered on. However, Autoscale does not provision additional machines.
Instance size considerations
You can optimize your costs if you appropriately size your instances in public clouds. We recommend that you provision smaller instances as long as they match your workload performance and capacity requirements.
Smaller instances host fewer user sessions than larger instances. Therefore, Autoscale puts machines into drain state much faster because it takes less time for the last user session to be logged off. As a result, Autoscale powers off smaller instances sooner, thereby reducing costs.
Drain state
Autoscale attempts to scale down the number of powered-on machines in the delivery group to the configured pool size and capacity buffer.
To achieve this goal, Autoscale puts the excess machines with the fewest sessions into “drain state” and powers them off when all sessions are logged off. This behavior occurs when session demand lessens and the schedule requires fewer machines than are powered on.
Autoscale puts excess machines into “drain state” one by one:
-
If two or more machines have the same number of active sessions, Autoscale drains the machine that has been powered on for the specified power-off delay.
Doing so avoids putting recently powered-on machines into drain state because those machines are more likely to have the fewest sessions.
-
If two or more machines have been powered on for the specified power-off delay, Autoscale drains those machines one by one at random.
Machines in drain state no longer host new session launches and are waiting for the existing sessions to be logged off. A machine becomes a candidate for shutdown only when all sessions are logged off. However, if there are no machines immediately available for session launches, Autoscale prefers directing the session launches to a machine in drain state over powering on a machine.
A machine is taken out of drain state when one of the following conditions is met:
- The machine is powered off.
- Autoscale is disabled for the delivery group to which the machine belongs.
- Autoscale uses the machine to meet schedule or load demand requirements. This case occurs when the schedule (schedule-based scaling) or the current demand (load-based scaling) requires more machines than the number of machines that are currently powered on.
Important:
If no machines are immediately available for session launches, Autoscale prefers directing session launches to a machine in drain state over powering on a machine. A machine in drain state that hosts a session launch remains in drain state.
To find out which machines are in drain state, use the Get-BrokerMachine PowerShell command. For example: Get-BrokerMachine -DrainingUntilShutdown $true. Alternatively, you can use the Manage console. See Display machines in drain state.
Display machines in drain state
Note:
This feature applies only to multi-session machines.
In Web Studio, you can display machines that are in drain state, letting you know which machines are about to shut down. Complete the following steps:
- Navigate to the Search node and then click Columns to Display.
- In the Columns to Display window, select the check box next to Drain State.
- Click Save to exit the Columns to Display window.
The Drain State column can display the following information:
- Draining until shutdown. Appears when machines are in drain state until they’re shut down.
- Not draining. Appears when machines aren’t yet in drain state.
More information
For more information on Autoscale, see Citrix Autoscale in Tech Zone.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.