Method and system for managing virtual and real machines

• US 8,171,485 B2
• Filed: 09/21/2007
• Issued: 05/01/2012
• Est. Priority Date: 03/26/2007
• Status: Active Grant

• Current Assignee: Vmware LLC (Broadcom, Inc.)
• Original Assignee: Credit Suisse Securities Limited (Credit Suisse)
• Inventors: Muller, Leslie
• Primary Examiner(s): Puente, Emerson
• Assistant Examiner(s): Swift, Charles
• Application Number:
  US11/903,374
• Publication Number:
  US 20080244579A1
• Time in Patent Office: 1,684 Days
• Field of Search: 718/100, 718/104, 718/105, 718/1, 709/223, 709/226
• US Class Current: 718/104
• CPC Class Codes: G06F 2009/45562 Creating, deleting, cloning virtual machine instances
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 2009/45575 Starting, stopping, suspending or resuming virtual machine instances
• CPC Class Codes: G06F 2009/45583 Memory management, e.g. access or allocation
• CPC Class Codes: G06F 2009/45587 Isolation or security of virtual machine instances
• 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 2209/508 Monitor
• CPC Class Codes: G06F 9/455 Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/48 Program initiating; Program switching, e.g. by interrupt
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system
• CPC Class Codes: G06F 9/485 Task life-cycle, e.g. stopping, restarting, resuming execution G06F9/4881 takes precedence
• CPC Class Codes: G06F 9/50 Allocation of resources, e.g. of the central processing unit [CPU]
• CPC Class Codes: G06F 9/5005 to service a request
• CPC Class Codes: G06F 9/5011 the resources being hardware resources other than CPUs, Servers and Terminals
• CPC Class Codes: G06F 9/5016 the resource being the memory
• CPC Class Codes: G06F 9/5022 Mechanisms to release resources
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• CPC Class Codes: G06F 9/5055 : considering software capabilities, i.e. software resources associated or available to the machine
• CPC Class Codes: G06F 9/5077 : Logical partitioning of resources; Management or configuration of virtualized resources specific details on emulation or internal functioning of virtual machines G06F9/455
• CPC Class Codes: G06F 9/5088 : involving task migration

Abstract

Managing virtual and real machines through a provisioning system. The provisioning system allows a user to create and manage machines through a “self-service” approach. The provisioning system interacts with one or more agents that manage the lifecycle of a machine. The system may provide templates that enable a user to readily create a virtual machine. The system may also include interfaces for administrators to manage virtual and real machine resources.

Claims

1. A system for managing virtual computer resources, comprising:

a provisioning module operable to receive a request to act on a virtual resource, automatically generate instructions to implement the request, and dynamically monitor the virtual resource;

a lifecycle workflow engine logically connected to the provisioning module and operable to generate a lifecycle workflow of the virtual resource based on the request, the lifecycle workflow including provisioning, expiring, tombstoning, and disposing the virtual resource;

a plurality of physical hosts each comprising one or more virtual resources and each associated with one of a plurality of agents, at least one of the agents being logically connected to the provisioning module and operable to receive the instructions, act on the virtual resource in response to the request, and dynamically provide a status of the virtual resource.

2. The system of claim 1 wherein

the lifecycle workflow engine is further operable to generate the lifecycle workflow according to workflow states and activities available for selection based on a particular role among a group of user roles,

the lifecycle workflow defines respective timings for each of the provisioning, expiring, tombstoning, and disposing, and

the lifecycle workflow further comprises instructions for the at least one of the agents to act on the virtual resource.

3. The system of claim 2 further comprising a security module logically connected to the provisioning module and the lifecycle workflow engine and operable to restrict an available selection of templates of virtual resources and the workflow states and activities based on access permissions associated with the particular role.

4. The system of claim 2, wherein

in response to instructions received in association with an administrator role of the group of user roles, the lifecycle workflow engine is further configured to modify the selection of workflow states and activities available for selection by the particular role.

5. The system of claim 2, wherein

in response to instructions received in association with an administrator role of the group of user roles, the lifecycle workflow engine is further configured to modify workflow states and timings of all lifecycle workflows associated with the particular role.

6. The system of claim 2, wherein

in response to instructions received in association with an administrator role of the group of user roles, the lifecycle workflow engine is further configured to modify workflow states and timings of the lifecycle workflow of the virtual resource, and

the at least one of the agents is further operable to receive instructions based on the modified workflow states and timings.

7. The system of claim 2, wherein

in response to a status request received in association with an enterprise role of the group of user roles, the plurality of agents are further configured provide a status of each virtual resource operating on the plurality of physical hosts with reference to the lifecycle workflow.

8. The system of claim 1 further comprising a client module logically connected to the provisioning module and operable to allow an end user to submit the request to the provisioning module.

9. The system of claim 1 further comprising an image store comprising images of virtual resources logically connected to the agents, wherein the at least one of the agents retrieves an image associated with the virtual resource and copies the image onto one or more of the physical hosts.

10. The system of claim 1 wherein

each of the plurality of agents resides on a proxy and controls one of the plurality of physical hosts remotely, and

the at least one of the agents is further operable to provide a notification that an expiration time of the virtual resource is approaching based on the lifecycle workflow.

11. The system of claim 1, wherein the received request corresponds to one or more templates of virtual resources.

12. The system of claim 11 wherein the request specifies the one or more templates of virtual resources each including an allocation of physical resources associated with the plurality of physical hosts.

13. The system of claim 1 wherein the provisioning module is further operable to dynamically determine states of a plurality of virtual resources based on a status provided by the plurality of agents, wherein the determination comprises a measure of physical resources used on the plurality of physical hosts.

14. A system for managing virtual computer resources, comprising:

a provisioning module operable to receive a request to act on a virtual resource and automatically generate instructions to implement the request;

a workflow engine logically connected to the provisioning module and operable to instantiate a lifecycle workflow of the virtual resource based on the request, the lifecycle workflow including provisioning, expiring, tombstoning, and disposing the virtual resource;

one or more templates each comprising a configuration for a virtual resource including an allocation of physical resources associated with at least one physical host, the received request corresponding to a template of the one or more templates; and

the plurality of physical hosts each comprising one or more virtual resources and each associated with one of a plurality of agents, at least one of the agents being logically connected to the provisioning module and operable to receive the instructions and to act on the virtual resource in response to the request.

15. The system of claim 14, wherein

the workflow engine is further operable to instantiate the lifecycle workflow according to a selection of workflow states and activities available for selection based on a particular role among a group of user roles,

the lifecycle workflow defines respective timings for each of the provisioning, expiring, tombstoning, and disposing, and

the system further comprises a security module logically connected to the provisioning module and the workflow engine and operable to restrict an available selection of templates of virtual resources and the workflow states and activities based on access permissions associated with the particular role.

16. The system of claim 14 further comprising a client module logically connected to the provisioning module and operable to allow an end user to submit the request to the provisioning module.

17. The system of claim 14 further comprising an image store comprising images of virtual resources logically connected to the agents, wherein the at least one of the agents retrieves an image associated with the virtual resource and copies the image onto one or more of the physical hosts.

18. The system of claim 14 wherein each of the plurality of agents resides on a proxy and controls one of the plurality of physical hosts remotely.

19. The system of claim 14 wherein the provisioning module is further operable to dynamically determine states of a plurality of virtual resources based on a status provided by the plurality of agents, wherein the determination comprises a measure of physical resources used on the plurality of physical hosts.

20. A method for controlling computer resources comprising the steps of:

presenting, by at least one computer, a user interface to an end user comprising one or more controls for submitting requests for actions on a computer resource;

receiving, by the at least one computer, a request for an action on a computer resource;

generating, by the at least one computer, a lifecycle workflow of the computer resource based on the request, the lifecycle workflow including provisioning, expiring, tombstoning, and disposing the computer resource;

automatically instructing, by the at least one computer, an agent associated with one of a plurality of physical hosts according to an instruction in response to receiving the request, the instruction comprising an action associated with the request; and

receiving, by the at least one computer, status information on the computer resource.

21. The method of claim 20 wherein

the step of generating a lifecycle workflow further comprises generating, by the at least one computer, the lifecycle workflow according to a selection of workflow states and activities available for selection based on a particular role among a group of user roles,

the lifecycle workflow defines respective timings for each of the provisioning, expiring, tombstoning, and disposing,

the computer resource comprises a virtual resource and one of the one or more controls comprises a control to request that a virtual resource be created, and

the method further comprises restricting, by the at least one computer, an available selection of the one or more controls based on access permissions associated with the particular role.

22. The method of claim 20 further comprising the step of automatically instructing, by the at least one computer, an agent associated with one of a plurality of physical hosts via a second instruction, wherein the second instruction comprises an action not in response to the request.

23. The method of claim 22 further comprising providing a notification, by the at least one computer, that an expiration time of the computer resource is approaching based on the lifecycle workflow.

24. The method of claim 22 wherein the request is associated with one or more templates each specifying a respective allocation of physical resources associated with the plurality of physical hosts.

25. A system for managing computer resources, comprising:

a provisioning module operable to receive a request to act on a computer resource, automatically generate instructions to implement the request, and dynamically monitor the computer resource;

a lifecycle workflow engine logically connected to the provisioning module and operable to generate a lifecycle workflow of the computer resource based on the request, the lifecycle workflow including provisioning, expiring, tombstoning, and disposing the computer resource;

a plurality of agents each associated with a physical host, at least one of the agents being logically connected to the provisioning module and operable to receive the instructions, act on the computer resource in response to the request, and dynamically provide a status of the computer resource.

26. The system of claim 25 wherein

the lifecycle workflow engine is further operable to generate the lifecycle workflow according to a selection of workflow states and activities available for selection based on a particular role among a group of user roles,

the lifecycle workflow defines respective timings for each of the provisioning, expiring, tombstoning, and disposing,

the lifecycle workflow further includes instructions for the at least one of the agents to act on the computer resource, and

the system further comprises a security module logically connected to the provisioning module and the workflow engine and operable to restrict a nature of the request and the workflow states and activities available for selection based on access permissions associated with the particular role.

27. The system of claim 26 wherein the computer resource comprises a computer storage resource.

28. The system of claim 26 wherein the computer resource comprises a computer network connection resource.

29. A computer system-implemented method for managing a lifecycle of a virtual machine comprising:

receiving, by at least one computer, a request for a virtual machine;

providing, by the at least one computer, a listing of virtual machine templates and lifecycle workflows available for selection;

obtaining, by the at least one computer, a selection of a virtual machine template and a lifecycle workflow;

instantiating, by the at least one computer, a provisioning workflow associated with the selected virtual machine template based on the selected lifecycle workflow, the provisioning workflow including provisioning, expiring, tombstoning, and disposing the virtual machine;

provisioning, by the at least one computer, the virtual machine on a physical host; and

activating, by the at least one computer, the virtual machine according to a timing specified by the provisioning workflow.

30. The method of claim 29, wherein the step of instantiating a provisioning workflow further comprises instantiating, by the at least one computer, the provisioning workflow according to a selection of workflow states and activities available for selection based on a particular role among a group of user roles, the group of user roles including support, end user, group administrator, and enterprise administrator roles.

31. The method of claim 30, further comprising restricting, by the at least one computer, the listing of virtual machine templates and lifecycle workflows available for selection based on access permissions associated with the particular role.

32. The method of claim 29, wherein

the virtual machine is unavailable during the tombstoning, and

the tombstoning occurs for a predefined period of time before the disposing and the after the expiring, and

the method further comprises receiving, by the at least one computer, a command to reactivate the virtual machine during the predefined period of time;

and

reactivating the virtual machine in response to the command.