INDEPENDENT ACCESS TO VIRTUAL MACHINE DESKTOP CONTENT

• US 20160179566A1
• Filed: 02/29/2016
• Published: 06/23/2016
• Est. Priority Date: 01/27/2010
• Status: Active Grant

• Current Assignee: Vmware LLC (Broadcom, Inc.)
• Original Assignee: VMware, Inc. (Broadcom, Inc.)
• Inventors: Chawla, Puneet, Chamcham, Jad
• Granted Patent: US 9,864,625 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 2009/45591 Monitoring or debugging support
• CPC Class Codes: G06F 2009/45595 Network integration; Enabling network access in virtual machine instances
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

Methods, systems, and techniques for facilitating access to content stored remotely, for example, as part of a virtual machine infrastructure or elsewhere in a networked environment, using a uniform mechanism are provided. Example embodiments provide an Enhanced Virtual Desktop Management Server/System with a Content Abstraction Layer which enables users to access their data stored as part of a virtual machine environment, or replicated otherwise on a network, using a generic API. The API can be incorporated into a web browser or other third party interface to provide access to the users'"'"' data without needing to remote a bitmap representation of a virtual desktop display. Accordingly, users can access their data, applications, and settings regardless of the type of access device and regardless of whether the corresponding virtual desktop is running in the data center, provisioned in the datacenter but running on a client device, or not running at all.

Claims

1. (canceled)

2. A system comprising:

one or more computing devices including one or more memories and one or more computer processors configured to perform operations comprising;

receiving a client application request from a client device for user data stored in a remote location from the client device in a centralized datastore; and

determining the remote location of the stored user data being requested;

determining that the remote location of the requested user data is on a virtual disk that is associated with a virtual desktop of a first virtual machine assigned to the user that is not currently running;

in response to a determination that the first virtual machine is not currently running determining whether the first virtual machine is a checked-out virtual machine;

in response to a determination that the first virtual machine is a checked-out virtual machine;

identifying one or more hypervisors that have access to the virtual disk stored in the centralized datastore;

selecting a control virtual machine that is running on one of the one or more hypervisors, wherein the control virtual machine is distinct from the first virtual machine assigned to the user, and wherein the control virtual machine, when instantiated on a particular hypervisor, provides on demand access to user content for a plurality of users located on respective virtual disks accessible by the particular hypervisor when a corresponding virtual machines are not running;

causing the control virtual machine to access the requested user data; and

providing requested user data.

3. The system of claim 2, wherein causing the control virtual machine to access the requested user data includes:

causing the control virtual machine to mount the virtual disk to access the user data.

4. The system of claim 2, wherein providing the user data include generating a client view based on a detected form factor.

5. The system of claim 2, wherein the connection to the control virtual machine and accessing the requested data occurs while the virtual disk is not accessible through the associated non-running virtual machine assigned to the user.

6. The system of claim 2, wherein the centralized datastore is a part of an enterprise virtualization infrastructure.

7. The system of claim 2, comprising:

prior to causing the control virtual machine to access the user data, verifying that the user has authority to access the user data.

8. The system of claim 2, comprising:

using a policy database that stores rules defining which users have access to which data to determine whether the identified user has legitimate access to the requested user data before causing the control virtual machine to access the user data.

9. The system of claim 2, comprising:

tracking accesses to user data; and

tracking the request for the user data before causing the control virtual machine to access the user data.

10. The system of claim 2, wherein the checked-out virtual machine is a virtual machine that is temporarily running on a client-side.

11. A method comprising:

receiving a client application request from a client device for user data stored in a remote location from the client device in a centralized datastore; and

determining the remote location of the stored user data being requested;

determining that the remote location of the requested user data is on a virtual disk that is associated with a virtual desktop of a first virtual machine assigned to the user that is not currently running;

in response to a determination that the first virtual machine is not currently running determining whether the first virtual machine is a checked-out virtual machine;

in response to a determination that the first virtual machine is a checked-out virtual machine;

identifying one or more hypervisors that have access to the virtual disk stored in the centralized datastore;

selecting a control virtual machine that is running on one of the one or more hypervisors, wherein the control virtual machine is distinct from the first virtual machine assigned to the user, and wherein the control virtual machine, when instantiated on a particular hypervisor, provides on demand access to user content for a plurality of users located on respective virtual disks accessible by the particular hypervisor when a corresponding virtual machines are not running;

causing the control virtual machine to access the requested user data; and

providing requested user data.

12. The method of claim 11, wherein causing the control virtual machine to access the requested user data includes:

causing the control virtual machine to mount the virtual disk to access the user data.

13. The method of claim 11, wherein providing the user data include generating a client view based on a detected form factor.

14. The method of claim 11, wherein the connection to the control virtual machine and accessing the requested data occurs while the virtual disk is not accessible through the associated non-running virtual machine assigned to the user.

15. The method of claim 11, wherein the centralized datastore is a part of an enterprise virtualization infrastructure.

16. The method of claim 11, comprising:

prior to causing the control virtual machine to access the user data, verifying that the user has authority to access the user data.

17. The method of claim 11, comprising:

using a policy database that stores rules defining which users have access to which data to determine whether the identified user has legitimate access to the requested user data before causing the control virtual machine to access the user data.

18. The method of claim 11, comprising:

tracking accesses to user data; and

tracking the request for the user data before causing the control virtual machine to access the user data.

19. The method of claim 11, wherein the checked-out virtual machine is a virtual machine that is temporarily running on a client-side.

20. A non-transitory computer-readable storage medium containing instructions that control a computer processor in a computing system to perform a method comprising:

receiving a client application request from a client device for user data stored in a remote location from the client device in a centralized datastore; and

determining the remote location of the stored user data being requested;

determining that the remote location of the requested user data is on a virtual disk that is associated with a virtual desktop of a first virtual machine assigned to the user that is not currently running;

in response to a determination that the first virtual machine is not currently running determining whether the first virtual machine is a checked-out virtual machine;

in response to a determination that the first virtual machine is a checked-out virtual machine;

identifying one or more hypervisors that have access to the virtual disk stored in the centralized datastore;

selecting a control virtual machine that is running on one of the one or more hypervisors, wherein the control virtual machine is distinct from the first virtual machine assigned to the user, and wherein the control virtual machine, when instantiated on a particular hypervisor, provides on demand access to user content for a plurality of users located on respective virtual disks accessible by the particular hypervisor when a corresponding virtual machines are not running;

causing the control virtual machine to access the requested user data; and

providing requested user data.