Securely remove and replace virtual machine pools

Abstract

The present disclosure relates to a method and apparatus for reliably erasing and replacing a pool of virtual machines, and in particular, but not exclusively, for reliably erasing and replacing a pool of virtual desktops. The virtual machines of the pool of virtual machines are implemented on a common virtualization layer and managed by a common virtual machine management application. The method includes using the virtual machine management application to create a replacement pool of virtual machines on the common virtualization layer having the same configuration and / or settings as the pool of virtual machines. The method further includes erasing each virtual machine of the pool of virtual machines using an erasure application executable independently of the virtual machine management application, and deleting the pool of virtual machines using the virtual machine management application.

Description

[Technical Field]

[0001] The present disclosure relates to methods and apparatus for reliably deleting and replacing pools of virtual machines, and particularly, but not exclusively, to methods and apparatus for reliably deleting and replacing pools of virtual desktops. [Background technology]

[0002] A virtual machine is a software implementation of a computing environment in which a guest operating system (OS) is installed and runs on physical hardware. A virtual machine typically emulates a physical computing environment, with requests for a central processing unit (CPU), memory, hard disk drive, network interface card, and other hardware resources managed by a virtualization layer that translates these requests to underlying physical hardware, such as the underlying physical hardware of a host machine. Furthermore, it is known to run multiple virtual machines on the same virtualization layer, with the multiple virtual machines sharing some of the same virtualized resources to form a virtual machine pool. In this manner, a virtual machine pool can be thought of as multiple virtual machines, with each virtual machine in the virtual machine pool configured to have the same settings and characteristics as each of the other virtual machines in the virtual machine pool.

[0003] For example, a virtual machine can take the form of a virtual desktop, which is essentially a guest operating system running on top of a virtualization layer that separates the desktop environment and associated application software from the physical host machine used to access it. As those skilled in the art will appreciate, virtual desktops can be used in conjunction with application virtualization and user profile management systems to provide a comprehensive desktop environment management system. Furthermore, it is known to run multiple virtual desktops on the same virtualization layer, with the multiple virtual desktops sharing some of the same virtualization resources to form a virtual desktop pool. In this manner, a virtual desktop pool can be thought of as multiple virtual desktops, each configured with the same settings and characteristics as each of the other virtual desktops in the virtual desktop pool. The virtual desktops in a virtual desktop pool can be collectively managed using a virtual desktop management application or virtual desktop infrastructure (VDI) software such as VMware Horizon® to control resource allocation based on current demand, etc. Pooling virtual desktops in this manner makes it easier to configure desktop settings and centralizes management of the virtual desktops. This allows for the delivery of identical applications to groups of users. It also facilitates automated virtual desktop provisioning. Pooling virtual desktops also makes patching and updating desktops easier, as patches or updates can be applied to all of the virtual desktops in the pool at the same time.

[0004] Each virtual machine in a pool of virtual machines can contain the same types of user-generated data as a non-virtualized machine. Such data may include, for example, sensitive information such as personally identifiable information (PII), confidential messages, trade secrets, etc. A resulting problem with virtual machine pools and virtual desktop pools is that it may be difficult to erase and replace each virtual machine in a virtual machine pool reliably or robustly enough for some applications or to comply with some security standards, or to erase and replace each virtual desktop in a virtual desktop pool reliably or robustly enough for some applications or to comply with some security standards. Summary of the Invention [Means for solving the problem]

[0005] According to one aspect of the present disclosure, there is provided a method for reliably erasing and replacing a pool of virtual machines, the virtual machines of the pool of virtual machines being implemented on a common virtualization layer and managed by a common virtual machine management application, the method comprising: using a virtual machine management application to create a replacement pool of virtual machines on a common virtualization layer having the same configuration and / or settings as the pool of virtual machines; Erasing each virtual machine in the pool of virtual machines using an erasure application that can run independently of the virtual machine management application; and deleting the pool of virtual machines using the virtual machine management application.

[0006] Erasing each virtual machine in the pool of virtual machines using the erasure application may include erasing at least one of the following associated with each virtual machine in the pool of virtual machines: one or more guest operating systems; one or more system files; one or more applications; or stored data.

[0007] Erasing each virtual machine in the pool of virtual machines using the erasure application may include erasing stored data associated with each virtual machine in the pool of virtual machines and further erasing at least one of the following: one or more guest operating systems associated with each virtual machine in the pool of virtual machines; one or more system files associated with each virtual machine in the pool of virtual machines; or one or more applications associated with each virtual machine in the pool of virtual machines.

[0008] Erasing each virtual machine in the pool of virtual machines using an erase application may include completely erasing each virtual machine in the pool of virtual machines.

[0009] Erasing each virtual machine in a pool of virtual machines using an erasure application that can run independently of the virtual machine management application may result in a more complete and / or reliable erasure of each virtual machine in the pool of virtual machines than erasing each virtual machine in the pool of virtual machines using the virtual machine management application itself. This is because erasing each virtual machine in a pool of virtual machines using the virtual machine management application itself may result in the virtual machine management application simply marking files associated with each virtual machine as deleted or hiding deleted or hidden files in the user interface so that they remain recoverable, allowing a user to recover the deleted or hidden files within a certain period of time. Erasing each virtual machine in a pool of virtual machines using an erasure application may result in the erasure application overwriting the contents of files associated with each virtual machine in the pool of virtual machines. Specifically, the erasure application may overwrite virtualized hard disks or storage volumes associated with each virtual machine. Alternatively, or in addition, the erasure application may change the encryption keys of encrypted virtualized hard disks or storage volumes associated with each virtual machine.

[0010] Using the erasure application to erase each virtual machine in the pool of virtual machines may include generating an erasure verification report containing data indicating the extent, scope, and / or successful completion of the erasure of each virtual machine in the pool of virtual machines as the erasure application erases each virtual machine in the pool of virtual machines. Using the erasure application to erase each virtual machine in the pool of virtual machines may enable verification of the erasure. For example, the erasure application may be configured to generate an erasure verification report at the end of the erasure process.

[0011] However, for example, because the erasing application is provided by a third-party supplier, the erasing application may not be supported by or compatible with the virtual machine management application. As a result, using the erasing application to erase each virtual machine in a pool of virtual machines may put the virtual machine pool into an unrecoverable error state that may prevent the virtual machine management application from continuing to manage the pool of virtual machines and / or may prevent the virtual machines in the pool of virtual machines from being used. Therefore, such a method may effectively enable reliable erasure and replacement of each virtual machine in a pool of virtual machines by using the virtual machine management application to create a replacement pool of virtual machines having the same configuration and / or settings as the pool of virtual machines before erasing each virtual machine in the pool of virtual machines using an erasing application that can be executed independently of the virtual machine management application. Thereafter, after the pool of virtual machines has entered an unrecoverable error state, the virtual machine management application can delete the pool of virtual machines. The replacement pool of virtual machines can be easily created by the virtual machine management application. In essence, the method enables the erasure and replacement of a pool of virtual machines in a manner that is not only reliable and robust, but also automatic and seamless to the user. Although erasing a pool of virtual machines using an independently executable erasure application may take longer than using a virtual machine management application, erasure and replacement of the pool of virtual machines can be automated as part of the method.

[0012] Creating a replacement pool of virtual machines on a common virtualization layer using a virtual machine management application may include duplicating the pool of virtual machines on the common virtualization layer using a virtual machine management application, where such a replicated pool of virtual machines may have the same configurations and / or settings as the pool of virtual machines, but may not have the user-generated data that the pool of virtual machines may contain.

[0013] Using a virtual machine management application to create a replacement pool of virtual machines on a common virtualization layer is saving configurations and / or settings of a pool of virtual machines at a first time; At a second time, later than the first time, using the virtual machine management application to create a replacement pool of virtual machines on the common virtualization layer with the same configuration and / or settings as the pool of virtual machines. The method may include disabling or suspending operation of the pool of virtual machines using a virtual machine management application before erasing each virtual machine in the pool of virtual machines using the erase application.

[0014] Disabling or pausing the operation of a pool of virtual machines using a virtual machine management application before erasing each virtual machine in the pool of virtual machines using an erase application may make the method of reliably erasing and replacing a pool of virtual machines more reliable and secure. For example, a user may attempt to log in to a virtual machine while the erase application is erasing the virtual machine. Therefore, by disabling or pausing the operation of a pool of virtual machines using a virtual machine management application before erasing each virtual machine in the pool of virtual machines using an erase application, the possibility of a user attempting to log in to a virtual machine while the erase application is erasing the virtual machine can be prevented. There may also be situations in which the virtual machine management application creates a new virtual machine after the erase application determines which virtual machines exist in the pool of virtual machines. Therefore, by disabling or pausing the operation of a pool of virtual machines using a virtual machine management application before erasing each virtual machine in the pool of virtual machines using an erase application, the virtual machine management application can be prevented from creating a new virtual machine while the erase application is erasing each virtual machine in the pool of virtual machines. This means that the erase application can reliably determine which virtual machines are part of the pool of virtual machines being erased.

[0015] The method may include using the virtual machine management application to disable or suspend operation of the pool of virtual machines before using the virtual machine management application to create a replacement pool of virtual machines on a common virtualization layer.

[0016] Using a virtual machine management application to disable or pause operation of a pool of virtual machines before using a virtual machine management application to create a replacement pool of virtual machines on a common virtualization layer may mean that the virtual machine management application creates the replacement pool of virtual machines on the common virtualization layer in a disabled or paused state.

[0017] The method may include enabling or initiating operation of a replacement pool of virtual machines.

[0018] The method may include enabling or initiating operation of a replacement pool of virtual machines before or after deleting the pool of virtual machines using a virtual machine management application.

[0019] The method may include enabling or initiating operation of a replacement pool of virtual machines before or after erasing the pool of virtual machines using an erasure application.

[0020] The pool of virtual machines may include a pool of virtual desktops, and the virtual machine management application may include a virtual desktop management application or virtual desktop infrastructure (VDI) software.

[0021] The virtual machine management application may include VMware Horizon®.

[0022] The method may be defined by a VMware Orchestrator workflow. An Orchestrator workflow may be thought of as an automated task scripted in a VMware-specific language. The VMware Orchestrator workflow may invoke a virtual machine management application to create a replacement pool of virtual machines on a common virtualization layer. The VMware Orchestrator workflow may invoke an erasure application to erase each virtual machine in the pool of virtual machines.

[0023] The method may be initiated, launched, or operated via the VMware Horizon® graphical user interface.

[0024] The method may include executing the virtual machine management application and the erasure application using the same processing resources or different processing resources.The method may include executing the virtual machine management application and the erasure application using the same computer or different physical computers.

[0025] According to one aspect of the present disclosure, there is provided a computer program that, when executed by processing resources of a data erasure apparatus, causes the data erasure apparatus to perform any of the methods for securely erasing and replacing a pool of virtual machines described above.

[0026] The pool of virtual machines may include a pool of virtual desktops, and the virtual machine management application may include a virtual desktop management application or virtual desktop infrastructure (VDI) software.

[0027] Virtual machine management applications or virtual desktop infrastructure (VDI) software may include VMware Horizon®.

[0028] The computer program may include or be a VMware Orchestrator workflow. An Orchestrator workflow may be thought of as an automated task scripted in a VMware-specific language. The VMware Orchestrator workflow may invoke a virtual machine management application to create a replacement pool of virtual machines on a common virtualization layer. The VMware Orchestrator workflow may invoke an erasure application to erase each virtual machine in the pool of virtual machines.

[0029] The computer program may be initiated, launched, or operated via a graphical user interface associated with VMware Horizon® (VDI) software.

[0030] The virtual machine management application and the erasure application may be executed by a processing resource, for example, the virtual machine management application and the erasure application may be executed by the same computer.

[0031] Alternatively, the virtual machine management application may be executed by a processing resource and the erasure application may be executed by a yet different processing resource, for example, the virtual machine management application and the erasure application may be executed by physically different computers.

[0032] According to one aspect of the present disclosure, there is provided a data erasure apparatus for securely erasing and replacing a pool of virtual machines, the data erasure apparatus being configured to perform any of the methods for securely erasing and replacing a pool of virtual machines described above.

[0033] The data erasure apparatus may include processing resources configured to execute a computer program that causes the data erasure apparatus to perform any of the methods for securely erasing and replacing a pool of virtual machines described above.

[0034] The pool of virtual machines may include a pool of virtual desktops, and the virtual machine management application may include a virtual desktop management application or virtual desktop infrastructure (VDI) software.

[0035] The virtual machine management application may include VMware Horizon®.

[0036] The computer program may include or be a VMware Orchestrator workflow. An Orchestrator workflow may be thought of as an automated task scripted in a VMware-specific language. The VMware Orchestrator workflow may invoke a virtual machine management application to clone a pool of virtual machines. The VMware Orchestrator workflow may invoke an erasure application.

[0037] The computer program may be initiated, launched, or operated via a graphical user interface associated with VMware Horizon® (VDI) software.

[0038] The virtual machine management application and the erasure application may be executed by a processing resource, for example, the virtual machine management application and the erasure application may be executed by the same computer.

[0039] Alternatively, the virtual machine management application may be executed by a processing resource and the erasure application may be executed by a further processing resource, for example, the virtual machine management application and the erasure application may be executed by physically different computers.

[0040] It should be understood that any one or more of the features of any one of the above aspects of the present disclosure may be combined with any one or more of the features of any of the other above aspects of the present disclosure. [Brief explanation of the drawings]

[0041] [Figure 1] FIG. 1 is a schematic diagram of a pool of virtual machines and a data erasure appliance that securely erases and replaces the pool of virtual machines. [Figure 2] FIG. 2 is a flowchart illustrating a method for reliably erasing and replacing a pool of virtual machines. [Figure 3] FIG. 3 is a flow chart illustrating a method for securely removing and replacing a pool of virtual machines in the form of a pool of virtual desktops. [Figure 4] Figure 4 is a screenshot showing the erasure of data from a pool of virtual desktops using the Erase application. [Figure 5] FIG. 5 is a screenshot of the graphical user interface of a virtual machine management application in the form of VMware Horizon® virtual desktop infrastructure (VDI) software after erasing data from a pool of virtual desktops using the erasure application. [Figure 6]Figure 6 is a screenshot of the graphical interface of the VDI software of Figure 5 showing the state of the pool of virtual desktops after erasing data from the pool of virtual desktops using an erasing application, showing an error message indicating that the pool of virtual desktops has entered an unrecoverable error state as a result of erasing data from the pool of virtual desktops using the erasing application. [Figure 7A] FIG. 7A shows a first portion of a list of configurations and settings for a pool of virtual desktops when using VMware Horizon® VDI software. [Figure 7B] FIG. 7B shows a second portion of the list of configurations and settings for a pool of virtual desktops when using VMware Horizon® VDI software. [Figure 7C] FIG. 7C shows a third portion of the list of configurations and settings for a pool of virtual desktops when using VMware Horizon® VDI software. [Figure 7D] FIG. 7D shows a fourth portion of the list of configurations and settings for a pool of virtual desktops when using VMware Horizon® VDI software. DETAILED DESCRIPTION OF THE INVENTION

[0042] A method and data erasure apparatus for securely erasing and replacing a pool of virtual machines will now be described, by way of non-limiting example only, with reference to the accompanying drawings, in which:

[0043] Referring first to FIG. 1 , there is a pool 2 of virtual machines 4, such as virtual desktops, and a data erasure device 6 for securely erasing and replacing the pool 2 of virtual machines 4. The virtual machines 4 in the pool 2 of virtual machines 4 are implemented on a common virtualization layer. Each virtual machine 4 in the pool 2 of virtual machines 4 is hosted on a corresponding physical host machine 10. However, those skilled in the art will understand that this is not a limitation, and that one or more virtual machines 4 in the pool 2 of virtual machines 4 may be hosted on the same physical host machine. As indicated by the dashed lines in FIG. 1 , the data erasure device 6 and the host machine 10 are configured to enable communication between the data erasure device 6 and each host machine 10.

[0044] The data erasure device 6 includes processing resources 20, a memory 22, and a user interface 23. The memory 22 stores a virtual machine management application 24. The erasure application 26 is executable independently of the virtual machine management application 24, in the sense that the processing resources 20 are capable of executing the virtual machine management application 24 and the erasure application 26 independently of each other. However, for example, the virtual machine management application 24 may not support the erasure application 26 or may be incompatible with the use of the erasure application 26 because the erasure application 26 is supplied by a third-party supplier. As a result, using the erasure application 26 to erase each virtual machine 4 in the pool 2 of virtual machines 4 may place the pool 2 of virtual machines 4 in an unrecoverable error state that may prevent the virtual machine management application 24 from continuing to manage the pool 2 of virtual machines 4 and / or may prevent the use of the virtual machines 4 in the pool 2 of virtual machines 4.

[0045] 2 illustrates a first method 30 for securely erasing and replacing a pool 2 of virtual machines 4. Method 30 is manually activated by a user via user interface 23, and once initiated, the steps of method 30 are implemented in software without further user interaction. Once method 30 is initiated, processing resources 20 execute virtual machine management application 24 and erasure application 26, thereby causing data erasure device 6 to perform method 30.

[0046] Specifically, in step 32, the virtual machine management application 24 creates a replacement pool of virtual machines (not shown) on a common virtualization layer that has the same configuration and / or settings as pool 2 of virtual machines 4. Then, in step 34, the erasure application 26 erases each virtual machine 4 in pool 2 of virtual machines 4. Specifically, the erasure application 26 erases at least one of the following associated with each virtual machine 4 in pool 2 of virtual machines 4: one or more guest operating systems; one or more system files; one or more applications; or saved data. For example, the erasure application 26 erases saved data associated with each virtual machine 4 in pool 2 of virtual machines 4, and further erases at least one of the following: one or more guest operating systems associated with each virtual machine 4 in pool 2 of virtual machines 4; one or more system files associated with each virtual machine 4 in pool 2 of virtual machines 4; or one or more applications associated with each virtual machine 4 in pool 2 of virtual machines 4.

[0047] Once Pool 2 of Virtual Machine 4 is deleted, the virtual machine management application 24 deletes Pool 2 of Virtual Machine 4 in step 36 .

[0048] Erasing each virtual machine 4 in pool 2 of virtual machines 4 using an erasure application 26 that can be executed independently of virtual machine management application 24 may result in a more complete and / or more reliable erasure of each virtual machine 4 in pool 2 of virtual machines 4 than erasing each virtual machine 4 in pool 2 of virtual machines 4 using the virtual machine management application 24 itself. However, for example, because the erasure application 26 is supplied by a third-party supplier, the erasure application 26 may not be supported by or compatible with the virtual machine management application 24, and as a result, using the erasure application 26 to erase each virtual machine 4 in pool 2 of virtual machines 4 may place pool 2 of virtual machines 4 in an unrecoverable error state that may prevent the virtual machine management application 24 from continuing to manage pool 2 of virtual machines 4 and / or may prevent the use of the virtual machines 4 in pool 2 of virtual machines 4. Thus, such a method may effectively enable erasure of each virtual machine 4 in pool 2 of virtual machines 4 using an erasure application 26 that can be executed independently of virtual machine management application 24, even if the erasure application 26 is not supported by or incompatible with the virtual machine management application 24.

[0049] In light of the above, those skilled in the art will appreciate that the method 30 described with reference to FIG. 2 not only reliably erases Pool 2 of virtual machines 4, but also creates a replacement pool of virtual machines in place of Pool 2 of virtual machines 4, with the same configuration and / or settings as Pool 2 of virtual machines 4. Method 30 may mean that a user can have confidence that the original Pool 2 of virtual machines 4 can be reliably erased without the risk that the replacement Pool 2 of virtual machines 4 is in an error state. Method 30 may also at least partially reduce the manual effort required to manually create a replacement pool of virtual machines with the same configuration and / or settings as the original Pool 2 of virtual machines 4. Creating a replacement pool of virtual machines may be important in many real-world situations where there is a requirement for the reliably erasing of the original virtual machines, but where the original virtual machines must be replaced with new virtual machines. For example, this may be advantageous for a business that requires each employee to have a new virtual machine in the morning and that requires each used virtual machine to be reliably erased in the evening when the employees return home.

[0050] Figure 3 illustrates a second method 40 for securely removing and replacing a pool 2 of virtual machines 4. In the method 40 of Figure 3, each virtual machine 4 in the pool 2 of virtual machines 4 takes the form of a virtual desktop, and the virtual machine management application 24 takes the form of virtual desktop infrastructure (VDI) software, such as VMware Horizon®.

[0051] Method 40 begins at step 41 with a user manually disabling pool 2 of virtual desktops 4 via a graphical user interface associated with VMware Horizon® VDI software 24. At step 42, the user manually activates a VMware Orchestrator workflow via a graphical user interface associated with VMware Horizon® VDI software 24, the workflow defining steps 42, 44, and 46 of method 40. As one skilled in the art will appreciate, a VMware Orchestrator workflow may be considered an automated task scripted in a VMware-specific language. When the VMware Orchestrator workflow is manually activated by the user at step 42, steps 42, 44, and 46 of method 40 are automatically performed as defined by the VMware Orchestrator workflow, thereby causing processing resources 20 to automatically perform steps 42, 44, and 46 of method 40 without further user interaction. Specifically, when the VMware Orchestrator workflow is manually activated by the user in step 42, the VDI software 24 creates a replacement pool of virtual desktops (not shown) on the common virtualization layer and replicates Pool 2 of virtual desktops 4 such that the replacement pool of virtual desktops has the same configuration and / or settings as Pool 2 of virtual desktops 4. A list of the configuration and / or settings of Pool 2 of virtual desktops 4 when using VMware Horizon® VDI software 24 is shown in Figures 7A-7B. By disabling or suspending operation of Pool 2 of virtual desktops 4 in step 41 before creating the replacement pool of virtual desktops on the common virtualization layer in step 42, the replacement pool of virtual desktops is created on the common virtualization layer with the same configuration and / or settings as Pool 2 of virtual desktops 4, but in a disabled or suspended state.

[0052] Thereafter, in step 44, the VDI software 24 invokes the erasure application 26 to erase each virtual desktop 4 in the pool 2 of virtual desktops 4. Specifically, the erasure application 26 erases at least one of the following associated with each virtual desktop 4 in the pool 2 of virtual desktops 4: one or more guest operating systems; one or more system files; one or more applications; or saved data. For example, the erasure application 26 erases saved data associated with each virtual desktop 4 in the pool 2 of virtual desktops 4, and also erases at least one of the following: one or more guest operating systems associated with each virtual desktop 4 in the pool 2 of virtual desktops 4; one or more system files associated with each virtual desktop 4 in the pool 2 of virtual desktops 4; or one or more applications associated with each virtual desktop 4 in the pool 2 of virtual desktops 4.

[0053] For example, Figure 4 shows the progress of an erasure process performed by a third-party erasure application 26 on two virtual desktops 4 named "Helsinki1" and "Helsinki2" in a pool 2 of virtual desktops 4 named "Helsinki" managed by VDI software 24 in the form of VMware Horizon (registered trademark).

[0054] Referring again to FIG. 3, following the deletion of Pool 2 of Virtual Desktop 4, method 40 continues at step 46 with VDI software 24 deleting Pool 2 of Virtual Desktop 4.

[0055] Since the replacement pool of virtual desktops is created on the common virtualization layer in a disabled or suspended state in step 42, once the VMware Orchestrator workflow ends in step 46, method 40 concludes in step 48 with the user manually enabling the replacement pool of virtual desktops via a graphical user interface associated with the VMware Horizon® VDI software 24.

[0056] Erasing each virtual desktop 4 in pool 2 of virtual desktops 4 using an erasure application 26 that can run independently of the VDI software 24 may result in a more complete and / or more reliable erasure of each virtual desktop 4 in pool 2 of virtual desktops 4 than erasing each virtual machine 4 in pool 2 of virtual desktops 4 using the VDI software 24 itself. However, for example, because the erasure application 26 is supplied by a third-party supplier, the erasure application 26 may not be supported by or compatible with the VDI software 24. As a result, using the erasure application 26 to erase each virtual desktop 4 in pool 2 of virtual desktops 4 may place pool 2 of virtual desktops 4 in an unrecoverable error state that may prevent the VDI software 24 from continuing to manage pool 2 of virtual desktops 4 and / or may prevent the use of the virtual desktops 4 in pool 2 of virtual desktops 4. For example, FIG. 5 shows the VMware Horizon® desktop pool overview panel after the data erasure process is complete, in which a wearing symbol or icon appears adjacent to the icon for the Helsinki pool. 6 also illustrates the Helsinki pool overview panel that appears after clicking or otherwise selecting the Helsinki pool's icon in the VMware Horizon® desktop pool overview panel of FIG. 5. Specifically, FIG. 6 illustrates a detailed error message indicating that the Helsinki pool has entered an unrecoverable error state. Thus, method 40 enables each virtual desktop 4 in pool 2 of virtual desktops 4 to be virtually reliably erased using erasure application 26 that can run independently of VDI software 24, even if erasure application 26 is not supported by or is incompatible with VDI software 24.

[0057] By using the VDI software 24 to disable or suspend operation of the virtual desktops 4 in pool 2 before erasing each virtual desktop 4 in pool 2 of virtual desktops 4 using the erasure application 26, a method for reliably erasing pool 2 of virtual desktops 4 can be made more reliable and secure. For example, a user may attempt to log in to a virtual desktop 4 while the erasure application 26 is erasing the virtual desktop 4. Therefore, by using the VDI software 24 to disable or suspend operation of the virtual desktops 4 in pool 2 before the erasure application 26 erases each virtual desktop 4 in pool 2 of virtual desktops 4, the possibility that a user may attempt to log in to a virtual desktop 4 while the erasure application 26 is erasing the virtual desktop 4 can be avoided. After the erasure application 26 identifies which virtual desktops 4 exist in pool 2 of virtual desktops 4, the VDI software 24 may create a new virtual desktop 4. Therefore, by using the VDI software 24 to disable or suspend operation of Pool 2 of virtual desktops 4 before the erasure application 26 erases each virtual desktop 4 in Pool 2 of virtual desktops 4, the VDI software 24 can be prevented from creating new virtual desktops 4 while the erasure application 26 is erasing each virtual desktop 4 in Pool 2 of virtual desktops 4. This means that the erasure application 26 can reliably identify which virtual desktops 4 are part of Pool 2 of virtual desktops 4 that are being erased.

[0058] In light of the above, those skilled in the art will appreciate that method 40 described with reference to FIGS. 3 through 6 not only securely erases Pool 2 of virtual desktops 4, but also creates a replacement pool of virtual desktops in place of Pool 2 of virtual desktops 4, with the same configuration and / or settings as Pool 2 of virtual desktops 4. Method 40 may mean that a user can have confidence that the original Pool 2 of virtual desktops 4 can be securely erased without the risk of the replacement pool of virtual desktops being in an error state. Method 40 may also at least partially reduce the manual effort required to manually create a replacement pool of virtual desktops with the same configuration and / or settings as the original Pool 2 of virtual desktops 4. Creating a replacement pool of virtual desktops may be important in many real-world situations where there is a requirement for secure erasure of virtual desktops, but where an original virtual desktop must be replaced with a new virtual desktop. For example, this may be advantageous in a business that requires each employee to have a new virtual desktop in the morning and requires each used virtual desktop to be securely erased in the evening when employees return home.

[0059] Those skilled in the art will also appreciate that various modifications can be made to the above method without departing from the scope of the present invention as defined by the appended claims. For example, in step 32 of FIG. 2 , creating a replacement pool of virtual machines on a common virtualization layer using virtual machine management application 24 may include saving the configuration and / or settings of pool 2 of virtual machines 4 at a first time, and creating a replacement pool of virtual machines on the common virtualization layer using virtual machine management application 24 at a second time, later than the first time, with the same configuration and / or settings as pool 2 of virtual machines 4. Similarly, in step 42, replicating pool 2 of virtual desktops 4 on a common virtualization layer using VDI software 24 may include saving the configuration and / or settings of pool 2 of virtual machines 4 at a first time, and replicating pool 2 of virtual desktops 4 on the common virtualization layer with the same configuration and / or settings as pool 2 of virtual machines 4 at a second time, later than the first time.

[0060] Those skilled in the art should understand that although the VDI software 24 and the erasure application 26 are described above as being stored in the memory 22 of the same data erasure device 6 and executed by the processing resources 20 of the same data erasure device 6, the VDI software 24 and the erasure application 26 may be stored in the memory of different devices and / or executed by the processing resources of different devices.

[0061] Each feature disclosed or illustrated herein may be incorporated into any embodiment alone or in any suitable combination with other features disclosed herein and / or illustrated in the accompanying drawings. In particular, those skilled in the art will understand that one or more of the features of any one of the embodiments of the present disclosure described above with reference to the drawings may produce effects or provide advantages when used separately from one or more of the other features of any one of the embodiments of the present disclosure, and that different combinations of features are possible other than the specific combinations of features of the embodiments of the present disclosure described above.

[0062] The use of the term "comprising" in connection with a feature of an embodiment of the present disclosure does not exclude other features or steps of the embodiment of the present disclosure. The use of the term "a" or "an" in connection with a feature of an embodiment of the present disclosure does not exclude the possibility that the embodiment includes a plurality of such features.

Claims

1. A computer-implemented method for reliably erasing and replacing a pool of virtual machines, the virtual machines in the pool of virtual machines being implemented on a common virtualization layer and managed by a common virtual machine management application; by the computer using the virtual machine management application to create a replacement pool of virtual machines on the common virtualization layer having the same configuration and / or settings as the pool of virtual machines; erasing each virtual machine in the pool of virtual machines using an erasure application that can run independently of the virtual machine management application; using the virtual machine management application to delete the pool of virtual machines.

2. The method of claim 1, wherein erasing each virtual machine in the pool of virtual machines using the erasure application executed by the computer includes erasing at least one of the following associated with each virtual machine in the pool of virtual machines: one or more guest operating systems; one or more system files; one or more applications; or stored data.

3. A method as described in claim 1 or 2, characterized in that erasing each virtual machine in the pool of virtual machines using the erasure application executed by the computer includes erasing stored data associated with each virtual machine in the pool of virtual machines and further erasing at least one of the following: one or more guest operating systems associated with each virtual machine in the pool of virtual machines; one or more system files associated with each virtual machine in the pool of virtual machines; and one or more applications associated with each virtual machine in the pool of virtual machines.

4. A method according to any one of claims 1 to 3, characterized in that erasing each virtual machine in the pool of virtual machines using the erasure application executed by the computer includes completely erasing each virtual machine in the pool of virtual machines.

5. A method according to any one of claims 1 to 4, characterized in that erasing each virtual machine in the pool of virtual machines using the erasure application executed by the computer includes generating an erasure verification report upon completion of erasure of each virtual machine in the pool of virtual machines, the erasure verification report including data indicating the extent, scope and / or successful completion of the erasure of each virtual machine in the pool of virtual machines.

6. A method according to any one of claims 1 to 5, characterized in that creating a replacement pool of virtual machines on the common virtualization layer using the virtual machine management application executed by the computer includes replicating the pool of virtual machines on the common virtualization layer using the virtual machine management application.

7. The method of claim 6, wherein creating a replacement pool of virtual machines on the common virtualization layer using the virtual machine management application executed by the computer comprises: saving the configurations and / or settings of the pool of virtual machines at a first time; 6. A method according to claim 1, further comprising: at a second time, later than the first time, using the virtual machine management application to create a replacement pool of virtual machines on the common virtualization layer with the same configuration and / or settings as the pool of virtual machines.

8. A method according to any one of claims 1 to 7, characterized in that the computer uses the virtual machine management application to disable or suspend operation of the pool of virtual machines before using the erasure application to erase each virtual machine in the pool of virtual machines.

9. A method according to any one of claims 1 to 8, characterized in that the computer uses the virtual machine management application to disable or suspend operation of the pool of virtual machines before using the virtual machine management application to create a replacement pool of the virtual machines on the common virtualization layer.

10. A method according to any one of claims 1 to 9, characterized in that the method is performed by the computer to enable or initiate operation of a replacement pool of virtual machines.

11. 11. The method of claim 1, wherein the pool of virtual machines comprises a pool of virtual desktops, and the virtual machine management application comprises a virtual desktop management application or virtual desktop infrastructure (VDI) software.

12. The method of any of claims 1 to 11, wherein the virtual machine management application includes VMware Horizon(R).

13. 13. The method of claim 12, wherein the method is defined by a VMware Orchestrator workflow.

14. 14. The method of claim 13, wherein the VMware Orchestrator workflow invokes the virtual machine management application to create a replacement pool of the virtual machines on the common virtualization layer.

15. 15. The method of claim 13 or 14, wherein the VMware Orchestrator workflow invokes the erase application to erase each virtual machine in the pool of virtual machines.

16. 16. The method according to any of claims 12 to 15, characterized in that the method is initiated, launched or run via a VMware Horizon® graphical user interface.

17. 17. A computer program product, which when executed by processing resources of a data erasure device, causes the data erasure device to perform the method for securely erasing and replacing a pool of virtual machines according to any one of claims 1 to 16.

18. 17. A data erasure apparatus for securely replacing a pool of virtual machines, characterized in that it is configured to perform the method for securely erasing and replacing a pool of virtual machines according to any one of claims 1 to 16.

19. 19. The data erasure apparatus of claim 18, comprising processing resources configured to control the data erasure apparatus to perform the method for securely erasing and replacing a pool of virtual machines of any one of claims 1 to 16.

Images