A virtual desktop is a combination of computing resources, such as processor, memory, storage and computer network access, and computer programs running on such resources, which is remotely accessed by a user from a remote device. Such computer programs typically include an operating system, and one or more applications running on the computer that utilize the computer resources as managed by the operating system. The remote device provides an input and output interface between an individual user and the virtual desktop. The remote device communicates inputs to the virtual desktop and receives display information from the virtual desktop for display on the remote device over a computer network. An application is used on the remote device to connect to the virtual desktop.
A service provider can provide virtual desktops as a service to multiple customers, also called tenants. The service provider generally maintains one or more data centers, which is a location that houses multiple server computers on which virtual desktops are implemented. A tenant typically is an enterprise that has multiple users. Each user typically has a set of applications and resources based on a classification of the user. The service provider manages the server computers so as to provision sets of virtual desktops on its server computers for use by the users of each tenant.
Generally speaking, the service provider desires to isolate its customers from selection and management of hardware configurations, i.e., server computers, used to support the virtual desktops, yet can operate more profitably by efficiently allocating resources of its server computers to its tenants. For example, different pools of users may be better supported using different kinds of computer hardware configurations. For example, users with a graphics intensive workload, such as individuals using computer-aided design or three-dimensional animation applications, would be better served by computer hardware incorporating graphics processing units and substantial memory. Other users may use more memory than others, but need not use graphics processors.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is intended neither to identify key or essential features of the claimed subject matter, nor to limit the scope of the claimed subject matter.
A service provider can efficiently allocate server computer resources to tenant users, while isolating tenants from such allocation decisions. A tenant specifies a desktop model to be used for virtual desktops to be provisioned for a pool of users. The service provider has desktop managers for each tenant, each of which manages a homogeneous set of server computers to be used for provisioning virtual desktops for the tenant. Different desktop managers for a tenant are used to manage different sets of server computers to support virtual desktops using different desktop models or desktop models with different resource requirements. A resource manager of the service provider assigns virtual desktops to a desktop manager in a manner that optimizes the utilization of the server computers by using information about the desktop model used by the virtual desktops.
Accordingly, in one aspect, a computer system that supports virtual desktops on server computers for access by remote user computers includes a resource manager that receives a request to provision a plurality of virtual desktops for a pool of users for an enterprise according to a desktop model. In response to the request, the resource manager selects one of the desktop managers for the enterprise according to the specified desktop model. The requested plurality of virtual desktops are provisioned on one or more of the server computers managed by the selected desktop manager, so as to optimize utilization of the server computers by the virtual desktops for the enterprise.
In another aspect, a resource manager receives a request to provision a plurality of virtual desktops for a pool of users for an enterprise according to a desktop model. In response to the request, the resource manager selects one of the desktop managers for the enterprise according to the specified desktop model. The requested plurality of virtual desktops are provisioned on one or more of the server computers managed by the selected desktop manager, so as to optimize utilization of the server computers by the virtual desktops for the enterprise.
In another aspect, an article of manufacture includes a computer readable storage device, with computer program instructions stored on the computer readable storage device, that when read from the computer readable storage device and processed by a processor of a computer, configure the computer to operate as such a resource manager within such a computer system.
Yet another aspect includes a computer-implemented process performed by such a resource manager, and by such a computer system including such a resource manager.
In the following description, reference is made to the accompanying drawings which form a part hereof, and in which are shown, by way of illustration, specific example implementations. Other implementations may be made without departing from the scope of the disclosure.
The following section provides an example implementation of a computer system that supports virtual desktops for multiple tenants with multiple user classes.
As shown in
Two or more desktop managers 120 on the tenant computer network also are established for each tenant. Each desktop manager aggregates services for and information about virtual desktops available on the tenant computer network, and manages session state and allocation of virtual desktops to tenant users. A desktop manager generally is a computer having an architecture such as shown in
A tenant also has access to a tenant access manager computer (125). The tenant access manager computer allows a tenant to request the service provider provision one or more virtual desktops for a pool of users, as described in more detail below. The tenant access manager computer can provide other functionality such as account management, user entitlement, user authentication and authorization, utilization reporting, and the like. After a request from a tenant user to access a virtual desktop provisioned for the user, the tenant access manager contacts the desktop manager for the tenant to obtain information about a virtual desktop to be allocated to the user. The desktop manager provides an indication of a network address and a port through which the virtual desktop can be accessed on one of the server computers for the tenant. A tenant access manager generally is a computer having an architecture such as shown in
In this illustrative example, two tenants each with two different desktop managers are shown. While this example shows different tenants being assigned different server computers, it is possible to have different tenants share resources of a server computer.
A resource manager 130 allows the service provider to configure the server computers 100 to support virtual desktops, but without access to its tenants' computer networks or the virtual desktops. As described in more detail below, the resource manager receives requests, through tenant management computers, to provision virtual desktops for pools of users. These requests indicate a “desktop model” as described in more detail below. Using information about the server computers associated with each desktop manager of the tenant, the resource manager allocates the virtual desktops to the server computers assigned to the tenant so as to optimize the service provider's resource utilization for that tenant. A resource manager generally is a computer having an architecture such as shown in
To allow the service provider to isolate the tenant from allocation decisions that allow the service provider to optimize its resource allocation, the concept of a desktop model is used, along with using multiple desktop managers that manage server computers based on desktop models supported by those server computers. A desktop model represents the resources used to support a virtual desktop, and different users can be assigned different desktop models based on their likely workload.
Additionally, the set of server computers managed by each desktop manager are homogeneous, i.e., each server computer provides the same hardware resources to each virtual desktop as other server computers managed by the same desktop manager. As noted above, a server computer generally has an architecture such as described in
Given a request to provision a set of virtual desktops for a pool of users for a tenant according to a desktop model, the service provider selects a desktop manager that manages a set of server computers that is designed to support the specified desktop model. The resource manager then instructs the server computers of the selected desktop manager to provision the set of virtual desktops.
Each desktop manager can support more than one desktop model with the assumption that the desktop models associated with the same desktop manager have a similar workload profile, i.e. the desktop models have a common ratio of number of processing units to number of units of memory. For example a workload requiring 2 GB RAM and 1 CPU and a workload requiring 4 GB RAM and 2 CPUs can be supported by the same desktop manager since the ratio of CPU to memory is both 2:1.
For each tenant, the system generally maintains a list of users and information associating the user to a desktop model. The information about the desktop model is used by the service provider to select a desktop manager, and in turn a server computer, to provision and manage the virtual desktop that can be used by that user. When the virtual desktops are provisioned, the selection of the server computer to support the virtual desktop can be done in a way that optimizes the use of the service provider's resources while isolating the tenant from such decisions.
Given this description of a general operation and functionality of such a system, a more specific example implementation will now be described.
In this example, various data is stored in data structures in data files in a storage device or memory within the system to maintain the information used to assign users to desktop models, to assign server computers and desktop models to desktop managers, and to provision virtual desktops efficiently on the server computers based on the desktop models assigned to pools of users.
Referring now to
Referring to
Referring to
Referring to
These various data structures can be created, read, updated, written, deleted and stored by the service provider through the resource manager or by the tenant through the tenant desktop manager communicating with the resource manager. Both systems include computers (such as described in
Given a system so configured as described above in connection with
Referring now to
First, the tenant defines 600 the pool of users. This definition can be performed, for example, using an interface in a browser application on the tenant access manager which interfaces with the resource manager. For example, the user can provide a name for the pool, select a list of users to be associated with the pool from among a set of tenant users, and select a desktop model, data center and gold pattern to be associated with the pool (see
The tenant access manager then identifies 608 a desktop manager that manages server computers in the specified data center which can support the desktop model specified for the pool. The desktop manager is selected so as to optimize the fit of the set of virtual desktops for this pool of users to the resources available in the server computers according to selected criteria. In particular, the selected desktop manager is identified as supporting the specified desktop model and having sufficient remaining capacity to support the number of requested virtual desktops.
The optimization that can be performed depends on the criteria used and how desktop models are associated with desktop managers.
In one implementation, each desktop manager is associated with a single desktop model, and the set of server computers managed by the desktop manager is homogeneous with respect to the resources available (e.g., processors and memory) on those server computers. Each server computer managed by a desktop manager has available resources that is an integer number multiple of the resources used by the virtual desktop of the desktop model for that desktop manager. For example, if the desktop model calls for a ratio of two units (e.g., gigabytes) of memory to one processing unit (e.g., a 2:1 resource ratio), then each server computer has an integer multiple of two units of memory and an integer multiple of one processing units.
In another implementation, each desktop manager is associated with two or more similar desktop models. The set of server computers managed by the desktop manager is homogeneous with respect to the resources available (e.g., processors and memory) on those server computers. Desktop models are similar if the resource ratios (e.g., units of memory to number of processing units) are the same. For example, one desktop model can use four units of memory and two processors, while another desktop model can use two units of memory and one processor. Both of these desktop models, if otherwise using the same resources, can be managed by the same desktop manager.
Other implementations using more complex optimization algorithms can be used if the resource ratios of different desktop models are different, yet the resources used by those desktop models are otherwise the same, which would allow the same set of homogeneous server computers to be used by the same desktop manager for the different desktop models. The optimization is intended to avoid a situation for the service provider where either the memory or processing units of the server computer are underutilized due to the other resource (memory or processing units) being fully utilized. Such optimization also can take into consideration that a server computer may also be partitioned for use by the service provider for multiple tenants.
Given a selected desktop manager, the tenant access manager can check 604 to ensure that the requested virtual desktops would not exceed the quota for that desktop manager, and can signal 606 that the quota is exceeded. This check also can be performed interactively at the time the request is being formulated through the interface used to define the request. If this desktop manager would exceed its quota, a different desktop manager can be selected. If no desktop manager is available, then such a condition can be signaled as indicated at 608.
After desktop manager that has sufficient capacity for the selected pool of users has been identified, the tenant user instructs the tenant access manager computer to send 610 a request to the resource manager computer to provision a set of virtual desktops for the specified pool of users, according to the information provided for the pool. In turn, the resource manager provisions the virtual desktops on the server computers managed by that desktop manager using the specified gold pattern for that pool of users. After the virtual desktops are provisioned, users can access and use the virtual desktops through the access manager.
Referring now to
The tenant access manager 702 authenticates the user. Errors are signaled if the user is not properly authenticated. Using the examples described above, given a user identifier, the pool to which the user is assigned is identified. In turn, the data center and desktop model for that user are identified.
The tenant access manager contacts 704 the desktop manager in the data center associated with the desktop model for the user pool, to request an identifier for a virtual desktop running on one of the server computers associated with the desktop manager. It is possible that the virtual desktops for the user pool are underprovisioned, i.e., there are fewer virtual desktops than users in the pool. If all of the virtual desktops are being used, then the tenant access manager rejects the request for access from the user. Otherwise, a virtual desktop is assigned 706 to the user and an identifier for a virtual desktop in this class is returned to the user 708.
The resource manager and desktop managers as described above allow a service provider to optimize utilization of its server computers based on the desktop models specified by a tenant for each pool of users for the tenant, while isolating the tenant from decisions regarding allocation of its virtual desktops within the service provider's infrastructure.
With reference to
A computer storage medium is any medium in which data can be stored in and retrieved from addressable physical storage locations by the computer. Computer storage media includes volatile and nonvolatile, removable and non-removable media. Memory 804, removable storage 808 and non-removable storage 810 are all examples of computer storage media. Some examples of computer storage media are RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optically or magneto-optically recorded storage device, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Computer storage media and communication media are mutually exclusive categories of media.
The computer 800 also may include communications connection(s) 812 that allow the computer to communicate with other devices over a communication medium. Communication media typically transmit computer program instructions, data structures, program modules or other data over a wired or wireless substance by propagating a modulated data signal such as a carrier wave or other transport mechanism over the substance. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal, thereby changing the configuration or state of the receiving device of the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Communications connections 812 are devices, such as a network interface or radio transmitter, that interface with the communication media to transmit data over and receive data from communication media.
Computing machine 800 may have various input device(s) 814 such as a keyboard, mouse, pen, camera, touch input device, and so on. Output device(s) 816 such as a display, speakers, a printer, and so on may also be included. All of these devices are well known in the art and need not be discussed at length here.
The various components in
Each component of the system as described herein which operates using a computer can be implemented by a computer that is configured by one or more computer programs being processed by one or more processing units in the computer. A computer program includes computer-executable instructions and/or computer-interpreted instructions, such as program modules, which instructions are processed by one or more processing units in the computer. Generally, such instructions define routines, programs, objects, components, data structures, and so on, that, when processed by a processing unit, instruct the processing unit to perform operations on data or configure the computer to include various devices or data structures. This computer system may be practiced in distributed computing environments where tasks are performed by remote computers that are linked through a communications network. In a distributed computing environment, computer programs may be located in both local and remote computer storage media. The computer can be made highly available using conventional techniques in which computer hardware may be duplicated and includes fail over operations.
It should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific implementations described above. The specific implementations described above are disclosed as examples only.
Number | Name | Date | Kind |
---|---|---|---|
5063500 | Shorter | Nov 1991 | A |
5564016 | Korenshtein | Oct 1996 | A |
5774878 | Marshall | Jun 1998 | A |
6055563 | Endo | Apr 2000 | A |
6067545 | Wolff | May 2000 | A |
6070142 | McDonough et al. | May 2000 | A |
6341303 | Rhee | Jan 2002 | B1 |
6615253 | Bowman-Amuah | Sep 2003 | B1 |
6799209 | Hayton | Sep 2004 | B1 |
7299033 | Kjellberg | Nov 2007 | B2 |
7340522 | Basu et al. | Mar 2008 | B1 |
7373451 | Lam et al. | May 2008 | B2 |
7398349 | Birrell et al. | Jul 2008 | B2 |
7526300 | Choi | Apr 2009 | B2 |
7587352 | Arnott | Sep 2009 | B2 |
7802248 | Broquere et al. | Sep 2010 | B2 |
7917450 | Musuvathy | Mar 2011 | B1 |
7941801 | Williams | May 2011 | B2 |
8065676 | Sahai | Nov 2011 | B1 |
8166475 | Scales et al. | Apr 2012 | B1 |
8364802 | Keagy | Jan 2013 | B1 |
8380853 | Kudo | Feb 2013 | B2 |
8387132 | Frank et al. | Feb 2013 | B2 |
8423998 | Isci | Apr 2013 | B2 |
8549513 | Vinberg et al. | Oct 2013 | B2 |
8560671 | Yahalom et al. | Oct 2013 | B1 |
8938775 | Roth | Jan 2015 | B1 |
20010056494 | Trabelsi | Dec 2001 | A1 |
20020069102 | Vellante | Jun 2002 | A1 |
20020091697 | Huang et al. | Jul 2002 | A1 |
20020129126 | Chu | Sep 2002 | A1 |
20020152094 | Fahraeus | Oct 2002 | A1 |
20030006988 | Alford | Jan 2003 | A1 |
20030055666 | Roddy et al. | Mar 2003 | A1 |
20030149567 | Schmitz et al. | Aug 2003 | A1 |
20040003087 | Chambliss | Jan 2004 | A1 |
20040024627 | Keener | Feb 2004 | A1 |
20040054786 | Kjellberg | Mar 2004 | A1 |
20040054787 | Kjellberg | Mar 2004 | A1 |
20040093247 | Baken | May 2004 | A1 |
20050108709 | Sciandra et al. | May 2005 | A1 |
20050198130 | Bosloy | Sep 2005 | A1 |
20050198303 | Knauerhase et al. | Sep 2005 | A1 |
20050273568 | Blandy | Dec 2005 | A1 |
20050273862 | Benaloh et al. | Dec 2005 | A1 |
20060070077 | Erlandson | Mar 2006 | A1 |
20060143417 | Poisner et al. | Jun 2006 | A1 |
20060143617 | Knauerhase | Jun 2006 | A1 |
20060253848 | Mathieu | Nov 2006 | A1 |
20060276174 | Katz et al. | Dec 2006 | A1 |
20060294238 | Naik | Dec 2006 | A1 |
20070016432 | Piggott et al. | Jan 2007 | A1 |
20070043861 | Baron | Feb 2007 | A1 |
20070083630 | Roth | Apr 2007 | A1 |
20070106798 | Masumitsu et al. | May 2007 | A1 |
20070157309 | Bin et al. | Jul 2007 | A1 |
20070180448 | Low | Aug 2007 | A1 |
20070214455 | Williams et al. | Sep 2007 | A1 |
20070250833 | Araujo et al. | Oct 2007 | A1 |
20070260723 | Cohen | Nov 2007 | A1 |
20080005398 | Huffman | Jan 2008 | A1 |
20080080552 | Gates | Apr 2008 | A1 |
20080147671 | Simon | Jun 2008 | A1 |
20080184225 | Fitzgerald | Jul 2008 | A1 |
20080301674 | Faus | Dec 2008 | A1 |
20090199177 | Edwards et al. | Aug 2009 | A1 |
20100031270 | Wu | Feb 2010 | A1 |
20100088699 | Sasaki | Apr 2010 | A1 |
20100161879 | Nation | Jun 2010 | A1 |
20110102443 | Dror | May 2011 | A1 |
20110252135 | Kudo | Oct 2011 | A1 |
20110302578 | Isci | Dec 2011 | A1 |
20120110574 | Kumar | May 2012 | A1 |
20120159648 | Park | Jun 2012 | A1 |
20130235874 | Ringdahl | Sep 2013 | A1 |
20130263131 | Beda, III | Oct 2013 | A1 |
20140189109 | Jang | Jul 2014 | A1 |
20140214922 | Kim | Jul 2014 | A1 |
20150040121 | Barabash | Feb 2015 | A1 |
Entry |
---|
First office action in U.S. Appl. No. 11/875,297, dated Oct. 5, 2009. |
Second office action in U.S. Appl. No. 11/875,297, dated Apr. 2, 2010. |
Third office action in U.S. Appl. No. 11/875,297, dated May 11, 2012. |
Fourth office action in U.S. Appl. No. 11/875,297, dated Mar. 3, 2013. |
Notice of Allowability in U.S. Appl. No. 11/875,297, dated Jan. 2, 2014. |
First office action in U.S. Appl. No. 11/875,375, dated Sep. 28, 2010. |
Second office action in U.S. Appl. No. 11/875,375, dated Mar. 8, 2011. |
Third office action in U.S. Appl. No. 11/875,375, dated Apr. 20, 2012. |
Notice of Allowability in U.S. Appl. No. 11/875,375, dated Nov. 30, 2012. |
First office action in U.S. Appl. No. 13/716,289, dated Jul. 3, 2014. |
Second office action in U.S. Appl. No. 13/716,289, dated Dec. 19, 2014. |
Number | Date | Country | |
---|---|---|---|
20150256474 A1 | Sep 2015 | US |