
16
5. Based on your selection in part c of step 4, enter the characteristics that define the pool.
For this example, the following figure shows how to create a pool that is a subset of all the
Windows desktops in the Connection Broker. The figure them selects Centers from the Define pool
using drop-down menu, and selects the Red Hat center created in Step 5 to further restrict the
contents of the pool to only the Windows desktop hosted in the Red Hat center.
6. The Logging section allows you to log events when the number of desktops in the pool drops below
a specified threshold. For this example, leave the default values for this section.
7. Click Save.
The Pools page displays a hierarchy of all available pools. For a complete description of pools, see the
“Creating Desktop and Application Pools” chapter in the Connection Broker Administrator’s Guide.
Step 7: Defining Protocol, Power Control, and Release Plans
After you separate your desktops into pools, define the behaviors you want to assign to the desktops in
those pools. To perform this step, ask yourself the following questions.
What display protocols do I want the user to be able to use to connect to their desktops? This
example uses the SPICE protocol.
How do I want to manage the power state of each desktop, for example, should it be turned off
when the user logs out? This example does not modify the desktop’s power state.
How long do I want my user to be able to use a particular desktop, and claim it for their use? For
example, if the user logs out, should they remain assigned to that desktop, or should another user
be able to log into that desktop? This example unassigns the desktop when the user logs out.
The Leostream Connection Broker defines a plan as a set of behaviors that can be applied to any
Komentáře k této Příručce