HIGH PERFORMANCE INTELLIGENT VIRTUAL DESKTOP INFRASTRUCTURE USING VOLATILE MEMORY ARRAYS

• US 20150095597A1
• Filed: 09/30/2013
• Published: 04/02/2015
• Est. Priority Date: 09/30/2013
• Status: Abandoned Application

• Current Assignee: AmZetta Technologies, LLC (American Megatrends International, LLC)
• Original Assignee: American Megatrends Incorporated
• Inventors: Ayanam, Varadachari Sudan, Christopher, Samvinesh, Maity, Sanjoy, Parthiban, Baskar, Inbaraj, Joseprabu
• Application Number:
  US14/041,398
• Publication Number:
  US 20150095597A1
• Time in Patent Office: Days
• US Class Current: 711/162
• CPC Class Codes: G06F 11/1453 using de-duplication of the data
• CPC Class Codes: G06F 11/20 using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
• CPC Class Codes: G06F 11/2028 eliminating a faulty processor or activating a spare
• CPC Class Codes: G06F 11/2094 Redundant storage or storage space G06F11/2056 takes precedence
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 2201/815 Virtual middleware or OS functionality using virtual machines to implement generic software techniques for error detection or fault masking G06F11/1484
• CPC Class Codes: G06F 3/0604 Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/0641 De-duplication techniques
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

Certain aspects of the disclosure relate to a system and method for performing intelligent virtual desktop infrastructure (iVDI) using volatile memory arrays. The system has a hypervisor server and a storage server in communication via a file sharing protocol. A random access memory (RAM) disk is launched on a volatile memory array using a RAM disk driver. The RAM disk driver then assigns local and remote storages of the storage server as primary and secondary backup storages for the RAM disk. A group of virtual machine (VM) images is deployed to the RAM disk, and deduplication is performed on the VM images to release some memory space of the RAM disk. The deploying and deduplicating of the VM images continues repeatedly until the RAM disk is almost full. Then, the VM images in the RAM disk are copied to the backup storages as backup copies.

Claims

1. A method for performing intelligent virtual desktop infrastructure (iVDI) using volatile memory arrays, comprising:

launching a random access memory (RAM) disk on a volatile memory array using a RAM disk driver;

assigning a local storage physically located at a storage server as a primary backup storage for the RAM disk, wherein the storage server is connected to a hypervisor server via a file sharing protocol, and the hypervisor server is configured to execute a hypervisor;

deploying a first plurality of virtual machine (VM) images to the RAM disk;

deduplicating the first plurality of VM images in the RAM disk to release a first memory space of the RAM disk;

deploying a second plurality of VM images to the RAM disk and to occupy at least a part of the first memory space;

deduplicating the second plurality of VM images in the RAM disk; and

copying the deduplicated first plurality of VM images and the deduplicated second plurality of VM images from the RAM disk to the primary backup storage.

2. The method as claimed in claim 1, further comprising:

launching, at the hypervisor server, the hypervisor.

3. The method as claimed in claim 1, further comprising:

in response to an accessing command for a requested VM image from a remote computing device connected to the hypervisor server via a network,

sending a request for the requested VM image from the hypervisor server to the storage server;

retrieving, at the storage server, the requested VM image from the RAM disk;

sending the requested VM image from the storage server to the hypervisor server; and

running, at the hypervisor server, the requested VM image on the hypervisor.

4. The method as claimed in claim 1, further comprising:

in response to a writing command of data to the running VM image, simultaneously writing the data to the running VM image at the RAM disk and at the primary backup storage.

5. The method as claimed in claim 4, wherein the simultaneously writing of the data to the running VM image at the RAM disk and at the primary backup storage comprises:

receiving, by the hypervisor, the writing command;

monitoring, by the RAM disk driver, the writing command;

writing, by the hypervisor, the data to the running VM image at the RAM disk according to the writing command; and

simultaneously writing, by the RAM disk driver, the data to the running VM image at the primary backup storage and at the secondary backup storage according to the writing command.

6. The method as claimed in claim 1, wherein the file sharing protocol is a server message block (SMB) protocol.

7. The method as claimed in claim 1, wherein the deduplicating of the first plurality of VM images and the deduplicating of the second plurality of VM images in the RAM disk are performed by a deduplication module, wherein the deduplication module is configured to, when executed at a processor,

compare the VM images to identify at least one repeat data chunk existing for multiple times in the VM images;

store the at least one repeat data chunk in the RAM disk;

store a reference in the VM image pointing to the at least one repeat data chunk stored in the RAM disk; and

remove the at least one repeat data chunk for the VM images.

8. The method as claimed in claim 7, wherein the deduplication module is configured to, when executed at a processor,

identify a reference VM image from the VM images in the RAM disk;

for each VM image, compare the VM image to the reference VM image to identify the at least one repeat data chunk existing in both the VM image and the reference VM image, and a unique data chunk existing only in the VM image;

store a reference in the VM image pointing to the at least one repeat data chunk of the reference VM image; and

remove the at least one repeat data chunk in the VM image.

9. The method as claimed in claim 7, wherein the deduplication module is further configured to, when executed at a processor, periodically deduplicate the VM images stored in the RAM disk and the VM images stored in the primary backup storage.

10. The method as claimed in claim 1, wherein the copying of the deduplicated VM images from the RAM disk to the primary backup storage is performed by a backup module.

11. The method as claimed in claim 10, further comprising:

assigning a remote storage device not located at the storage server as a secondary backup storage for the RAM disk;

copying, by the backup module, the deduplicated VM images from the RAM disk to the secondary backup storage;

in response to the RAM disk being relaunched and the primary backup storage being available, copying the VM images from the primary backup storage to the RAM disk; and

in response to the RAM disk being relaunched and the primary backup storage being unavailable, copying the VM images from the secondary backup storage to the RAM disk.

12. The method as claimed in claim 10, wherein the backup module is further configured to, when executed at a processor, periodically copying the VM images from the RAM disk to the primary backup storage and the secondary backup storage.

13. The method as claimed in claim 1, wherein the RAM disk driver stores configuration settings of the RAM disk, and wherein the configuration settings of the RAM disk comprises a storage type of the RAM disk, partition type of the RAM disk, size of the RAM disk, and information of the assigned primary backup storage.

14. An intelligent virtual desktop infrastructure (iVDI) system, comprising:

a hypervisor server configured to execute a hypervisor;

a storage server in communication to the hypervisor server via a file sharing protocol, wherein the storage server comprises a local storage physically located at the storage server and a remote storage device not located at the storage server, wherein the storage server stores a random access memory (RAM) disk driver; and

a volatile memory array, comprising volatile memory provided on at least one of the hypervisor server and the storage server;

wherein the RAM disk driver comprises computer executable codes, wherein the codes, when executed on the hypervisor at a processor, are configured to

launch a RAM disk on the volatile memory array using the RAM disk driver;

assign the local storage as a primary backup storage for the RAM disk, and the remote storage as a secondary backup storage for the RAM disk;

deploy a first plurality of virtual machine (VM) images to the RAM disk;

deduplicate the first plurality of VM images in the RAM disk to release a first memory space of the RAM disk;

deploy a second plurality of VM images to the RAM disk and to occupy at least a part of the first memory space;

deduplicate the second plurality of VM images in the RAM disk; and

copy the deduplicated first plurality of VM images and the deduplicated second plurality of VM images from the RAM disk to the primary backup storage.

15. The iVDI system as claimed in claim 14, wherein the file sharing protocol is a server message block (SMB) protocol.

16. The iVDI system as claimed in claim 14, further comprising:

at least one remote computing device in communication to the hypervisor server via a network;

wherein in response to an accessing command for a requested VM image from the remote computing device, the codes, when executed on the hypervisor at the processor, are further configured to

send a request for the requested VM image from the hypervisor server to the storage server;

retrieve the requested VM image from the RAM disk;

send the requested VM image from the storage server to the hypervisor server; and

run the requested VM image on the hypervisor;

wherein in response to a writing command of data to the running VM image from the remote computing device, the codes, when executed on the hypervisor at the processor, are further configured to

receive the writing command;

write the data to the running VM image at the RAM disk according to the writing command; and

simultaneously write the data to the running VM image at the primary backup storage and at the secondary backup storage according to the writing command.

17. The iVDI system as claimed in claim 14, wherein the codes comprise a deduplication module and a backup module,

wherein the deduplication module is configured to

compare the VM images to identify at least one repeat data chunk existing for multiple times in the VM images;

store the at least one repeat data chunk in the RAM disk;

store a reference in the VM image pointing to the at least one repeat data chunk stored in the RAM disk; and

remove the at least one repeat data chunk for the VM images; and

wherein the backup module is configured to

copy the deduplicated VM images from the RAM disk to the primary backup storage and the secondary backup storage;

in response to the RAM disk being relaunched and the primary backup storage being available, copy the VM images from the primary backup storage to the RAM disk; and

in response to the RAM disk being relaunched and the primary backup storage being unavailable, copy the VM images from the secondary backup storage to the RAM disk.

18. The iVDI system as claimed in claim 17, wherein the deduplication module is further configured to periodically deduplicate the VM images stored in the RAM disk and the VM images stored in the primary backup storage.

19. The iVDI system as claimed in claim 14, wherein the RAM disk driver further comprises configuration settings of the RAM disk, and wherein the configuration settings of the RAM disk comprises a storage type of the RAM disk, partition type of the RAM disk, size of the RAM disk, and information of the assigned primary backup storage.

20. The iVDI system as claimed in claim 14, further comprising:

a management server in communication with the hypervisor server and the storage server, configured to provide hypervisor management, VM management and thin client management; and

a failover server in communication with the hypervisor server and the storage server, configured to provide failover service in response to at least one of the hypervisor server and the storage server being unavailable.

21. The iVDI system as claimed in claim 20, wherein the management server runs as a service on one of the hypervisor server and the storage server.

22. The iVDI system as claimed in claim 20, wherein the management server is further configured to provide backup schedule configuration and deduplication schedule configuration.

23. The iVDI system as claimed in claim 20, wherein the management server is further configured to store a copy of configuration settings of the RAM disk, and to monitor system events and issue alerts.

24. The iVDI system as claimed in claim 20, wherein the failover service provided by the failover server comprises:

in response to the hypervisor server being unavailable, providing hypervisor service until the hypervisor server becomes available; and

in response to the storage server being unavailable, providing storage service without the RAM disk until the storage server becomes available.

25. A non-transitory computer readable medium storing a RAM disk driver, wherein the RAM disk driver comprises computer executable codes, wherein the codes, when executed at a processor, are configured to:

launch a RAM disk on a volatile memory array using the RAM disk driver;

assign a local storage of a storage server as a primary backup storage for the RAM disk, and a remote storage of the storage server as a secondary backup storage for the RAM disk, wherein the storage server is connected to a hypervisor server via a file sharing protocol, and the hypervisor server is configured to execute a hypervisor;

deploy a first plurality of virtual machine (VM) images to the RAM disk;

deduplicate the first plurality of VM images in the RAM disk to release a first memory space of the RAM disk;

deploy a second plurality of VM images to the RAM disk and to occupy at least a part of the first memory space;

deduplicate the second plurality of VM images in the RAM disk; and

copy the deduplicated first plurality of VM images and the deduplicated second plurality of VM images from the RAM disk to the primary backup storage.

26. The non-transitory computer readable medium as claimed in claim 25, wherein the file sharing protocol is a server message block (SMB) protocol.

27. The non-transitory computer readable medium as claimed in claim 25, wherein

in response to an accessing command for a requested VM image from the remote computing device, the codes are configured to

send a request for the requested VM image from the hypervisor server to the storage server;

retrieve the requested VM image from the RAM disk;

send the requested VM image from the storage server to the hypervisor server; and

run the requested VM image on the hypervisor;

in response to a writing command of data to the running VM image from the remote computing device, the codes are configured to

receive the writing command;

write the data to the running VM image at the RAM disk according to the writing command; and

simultaneously write the data to the running VM image at the primary backup storage and at the secondary backup storage according to the writing command.

28. The non-transitory computer readable medium as claimed in claim 25, wherein the codes comprise a deduplication module and a backup module,

wherein the deduplication module is configured to

compare the VM images to identify at least one repeat data chunk existing for multiple times in the VM images;

store the at least one repeat data chunk in the RAM disk;

store a reference in the VM image pointing to the at least one repeat data chunk stored in the RAM disk; and

remove the at least one repeat data chunk for the VM images; and

wherein the backup module is configured to

copy the deduplicated VM images from the RAM disk to the primary backup storage and the secondary backup storage;

in response to the RAM disk being relaunched and the primary backup storage being available, copy the VM images from the primary backup storage to the RAM disk; and

in response to the RAM disk being relaunched and the primary backup storage being unavailable, copy the VM images from the secondary backup storage to the RAM disk.

29. The non-transitory computer readable medium as claimed in claim 28, wherein the deduplication module is further configured to periodically deduplicate the VM images stored in the RAM disk and the VM images stored in the primary backup storage.

30. The non-transitory computer readable medium as claimed in claim 25, wherein the RAM disk driver comprises configuration settings of the RAM disk, and wherein the configuration settings of the RAM disk comprises a storage type of the RAM disk, partition type of the RAM disk, size of the RAM disk, and information of the assigned primary backup storage.