Cloud computer shares is a collection of cloud computers that lets you manage their configurations collectively. Within a cloud computer shares, the system automatically creates, assigns, and releases cloud computers based on their configuration and end user connections. This improves cloud computer usage efficiency. This topic describes the features, scenarios, limits, scaling policies, and assignment mechanism of cloud computer shares.
Features
You can add multiple end users to a cloud computer shares. When an end user logs on to the client, the system automatically assigns a cloud computer to that user. When the end user disconnects from the cloud computer, the system automatically detaches the cloud computer from the user. This enables automatic scheduling of cloud computers.
The number of cloud computers in a cloud computer shares supports auto-scaling. When you create a cloud computer shares, you can select a billing method and set a corresponding scaling policy. The system then automatically creates or releases cloud computers based on end user connections and the scaling policy. This meets end user demand while improving efficiency and reducing costs.
All cloud computers in a cloud computer shares use the same configuration. You can manage them collectively to improve management efficiency. For example:
Change the specifications for a group of cloud computers simultaneously.
Update the image for a group of cloud computers simultaneously.
Change the security policy for a group of cloud computers simultaneously.
Scenarios
The multi-user shared cloud computer feature is characterized by the following:
All cloud computers use the same template and security policy. Their configuration and usage are identical.
The number of cloud computers is not fixed. The system automatically creates or releases cloud computers based on end user connections and the scaling policy. This means that a cloud computer may not always be available for an end user.
There is no fixed binding between a cloud computer and an end user. The system assigns a cloud computer to an end user only when a connection is requested. After the end user disconnects, the system detaches the cloud computer from the end user after 10 minutes.
Based on these characteristics, cloud computer shares are suitable for temporary use scenarios that require centralized management of cloud computers, where the computers do not have dedicated users and do not need to store personalized data. For example, internet cafes and school computer labs.
Limits
For the pay-as-you-go billing method, the maximum number of cloud computers is 200. For the subscription billing method, the maximum number of cloud computers is 100.
You cannot convert the billing method.
Reset types
The default reset type for a cloud computer shares is "Do not reset". This means that if a cloud computer is retained after a 10-minute disconnection, all data on the cloud computer is also retained.
You can change the reset type as needed. The supported reset types are:
Do not reset.
Reset only the system disk.
Reset only the user disk.
Reset the system disk and the user disk.
Scaling policies
The number of cloud computers in a cloud computer shares changes dynamically. When you create a cloud computer shares, you can set a scaling policy. The system uses this policy to automatically create, assign, and release cloud computers, which enables automatic scheduling.
For the subscription billing method, you must set an initial purchase quantity (S, where S ≥ 1), whether to allow automatic creation of cloud computers, and the maximum number of auto-created cloud computers.
In addition to the initial purchase quantity, you can allow the automatic creation of cloud computers to meet temporary demand. For example, consider a call center with three shifts of 50 customer service representatives each. Sometimes, temporary staff may be added for overtime. To ensure these temporary staff have cloud computers available, you can purchase an initial 50 cloud computers and then enable automatic creation to handle the overflow.
Allow automatic creation of cloud computers. You can set a maximum number of auto-created cloud computers (T).
The system initially creates S cloud computers. It then automatically creates or releases cloud computers based on end user connections. The number of cloud computers scales automatically between S and S + T.
NoteAuto-created cloud computers are billed on a pay-as-you-go basis. They are automatically released 10 minutes after the end user disconnects.
Setting a maximum for auto-created cloud computers helps control the number of computers and avoid unexpected costs.
Do not allow automatic creation of cloud computers.
The system initially creates S cloud computers. No more cloud computers are created later. The number of cloud computers is fixed at S.
ImportantIf you do not allow automatic creation, set the initial purchase quantity carefully based on your needs. This ensures a good user experience and prevents end users from being unable to connect when all resources are in use.
For the pay-as-you-go billing method, you must set a maximum number of cloud computers (M, where M ≥ 1), whether to reserve idle cloud computers, and the number of cloud computers to reserve.
Reserving idle cloud computers means keeping a certain number of cloud computers (N) in an idle state. This reduces connection times for end users. The system attempts to keep N cloud computers idle and unassigned, provided that the maximum number of cloud computers is not exceeded and end user demand is met.
ImportantIf you do not reserve idle cloud computers, the system creates a new cloud computer only when an end user requests a connection. Creating a cloud computer takes time and may fail if resources are out of stock. To ensure a good user experience, we recommend that you reserve idle cloud computers.
Allow reservation of idle cloud computers. You can set the number of cloud computers to reserve (N, where N ≤ M).
The system initially creates N cloud computers. It then automatically creates or releases cloud computers based on end user connections. The number of cloud computers scales automatically between N and M.
Do not allow reservation of idle cloud computers.
No cloud computers are created initially. The system automatically creates or releases cloud computers based on end user connections. The number of cloud computers scales automatically between 0 and M.
Cloud computer assignment mechanism
There is no fixed binding between cloud computers in a cloud computer shares and end users. You can add multiple end users as needed. The system automatically assigns cloud computers to end users based on their connection status. The assignment mechanism for each billing method and scaling policy is as follows:
For the subscription billing method
Scaling policy
End user connection status
On connection request
After disconnection
Allow automatic creation of cloud computers
Number of connected end users ≤ Initial purchase quantity
Assigns an existing subscription cloud computer. Connection time = Cloud computer assignment time.
The user can reconnect to the same cloud computer within 10 minutes. After 10 minutes, the cloud computer is detached from the end user, shut down, and processed according to the reset type.
Maximum number of cloud computers ≥ Number of connected end users > Initial purchase quantity
Assigns an auto-created pay-as-you-go cloud computer. Connection time = Cloud computer creation time + Cloud computer startup time + Cloud computer assignment time.
The user can reconnect to the same cloud computer within 10 minutes. After 10 minutes, the cloud computer is detached from the end user and released.
Number of connected end users > Maximum number of cloud computers
Does not assign a cloud computer. A message indicates that cloud computer resources are insufficient.
Not applicable
Do not allow automatic creation of cloud computers
Number of connected end users ≤ Initial purchase quantity
Assigns an existing subscription cloud computer. Connection time = Cloud computer assignment time.
The user can reconnect to the same cloud computer within 10 minutes. After 10 minutes, the cloud computer is detached from the end user, shut down, and processed according to the reset type.
Number of connected end users > Initial purchase quantity
Does not assign a cloud computer. A message indicates that cloud computer resources are insufficient.
Not applicable
NoteMaximum number of subscription cloud computers = Initial purchase quantity + Maximum number of auto-created cloud computers.
For the pay-as-you-go billing method
Scaling policy
End user connection status
On connection request
After disconnection
Allow reserving active cloud computers
Number of connected end users ≤ Maximum number of cloud computers
Assigns a reserved pay-as-you-go cloud computer. Connection time = Cloud computer assignment time.
The user can reconnect to the same cloud computer within 10 minutes. After 10 minutes, the cloud computer is detached from the end user. Any cloud computers that exceed the number of reserved computers are released.
Number of connected end users > Maximum number of cloud computers
Does not assign a cloud computer. A message indicates that cloud computer resources are insufficient.
Not applicable
Do not allow reservation of idle cloud computers
Number of connected end users ≤ Maximum number of cloud computers
Assigns an auto-created pay-as-you-go cloud computer. Connection time = Cloud computer creation time + Cloud computer startup time + Cloud computer assignment time.
The user can reconnect to the same cloud computer within 10 minutes. After 10 minutes, the cloud computer is detached from the end user and released.
Number of connected end users > Maximum number of cloud computers
Does not assign a cloud computer. A message indicates that cloud computer resources are insufficient.
Not applicable