US20130247033A1

US20130247033A1 - System and method for managing virtual machine configurations

Info

Publication number: US20130247033A1
Application number: US12/636,414
Authority: US
Inventors: Harvinder Singh Sawhney; Suman Saraf; Rosen Sharma
Original assignee: Individual
Current assignee: JPMorgan Chase Bank NA
Priority date: 2008-12-11
Filing date: 2009-12-11
Publication date: 2013-09-19
Also published as: US8544003B1

Abstract

A method in one example implementation includes receiving a plurality of command messages through a control channel and reconstructing the command messages to determine an intended command for one or more virtual machines on a server device. The command messages include one or more criteria and the intended command corresponds to an operation defined in a policy database. The method also includes determining whether the corresponding operation is permitted by comparing one or more policies associated with the operation to the one or more criteria. The method further includes sending the command messages to the server device if the operation is permitted. In more specific embodiments, the operation may include one of creating, cloning, deleting, starting, stopping, and modifying the one or more virtual machines.

Description

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of priority under 35 U.S.C. §119(e) of U.S. Provisional Application No. 61/201,699, filed Dec. 11, 2008, by Sharma et al., entitled “VM CHANGE ENFORCEMENT,” which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

This disclosure relates in general to the field of security and, more particularly, to managing virtual machine configurations in a virtual environment.

BACKGROUND

The field of network security has become increasingly important in today's society. In particular, the ability to effectively maintain secure and stable computers and systems presents a significant obstacle for component manufacturers, system designers, and network operators. This obstacle is made even more complicated due to the increased ease with which network systems may be manipulated, particularly in a virtualized environment. Virtualization is a software technology allowing an operating system (OS) to run in an isolated virtual environment (typically referred to as a virtual machine), where a platform's physical characteristics and behaviors are reproduced. More specifically, a virtual machine can represent an isolated, virtual environment running its own operating system and applications and being equipped with virtual hardware (processor, memory, disks, network interfaces, etc.). Commonly, the virtual machine is managed by a virtualization product. A virtual machine monitor (VMM) is the virtualization software layer that manages hardware requests from a guest OS (e.g., simulating answers from real hardware). A hypervisor is computer software/hardware platform virtualization software that may run on bare hardware and allows multiple operating systems to run on a host computer concurrently. ESX and ESXi by VMware, Inc. of Palo Alto, Calif., Xen by Citrix Systems, Inc. of Ft. Lauderdale, Fla., and Hyper-V by Microsoft Corp. of Redmond, Wash., represent forms of VMMs and these VMMs can be managed to better protect computers and systems from authorized and unauthorized manipulations that may affect system stability and security.

BRIEF DESCRIPTION OF THE DRAWINGS

To provide a more complete understanding of the present disclosure and features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying figures, wherein like reference numerals represent like parts, in which:

FIG. 1 is a pictorial representation of one embodiment of a network environment in which a system and method for managing virtual machine configurations may be implemented;

FIG. 2 is a simplified block diagram of one embodiment of a system and method for managing virtual machine configurations, which may be implemented as a control proxy;

FIG. 3 is a simplified block diagram illustrating one example implementation of a server in a system and method for managing virtual machine configurations;

FIG. 4 is a simplified block diagram of one example embodiment of a system and method for managing virtual machine configurations; and

FIG. 5 is a simplified flowchart illustrating a series of example steps associated with a system and method for managing virtual machine configurations in accordance with one embodiment.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

Overview

A method in one example implementation includes receiving a plurality of command messages through a control channel. The plurality of command messages may have one or more criteria. The method also includes reconstructing the plurality of command messages to determine an intended command for configuring one or more virtual machines on a server device. The intended command has a corresponding operation in a policy database and the operation may have one or more associated policies. The method further includes determining if the operation is permitted by comparing one or more policies associated with the operation to the one or more criteria. The method also includes sending the plurality of command messages to the server device if the operation is permitted. In more specific embodiments, the operation may include one of creating, cloning, deleting, starting, stopping, and modifying the one or more virtual machines. In other more specific embodiments, the server device is adapted to perform the operation only if a control proxy sends the plurality of command messages to the server device, and the control proxy is adapted to receive only the plurality of command messages through the control channel.

Example Embodiments

FIG. 1 is a simplified block diagram of a network environment 100 in which a system for managing virtual machine configurations may be implemented. Network environment 100 may include a server 300 accessed by different clients through a communication link provided by network 130. The different clients may include client devices 110 a and 110 b, which represent users having administrative privileges to configure server 300, and end user devices 120 a and 120 b, which represent end users who access applications or services provided by server 300. In one embodiment, server 300 may be configured to host one or more virtual machines. A control proxy 200 may be operably connected to client devices 110 a and 110 b for receiving configuration commands through a control channel. Control proxy 200 may also be operably connected to server 300, for sending permitted configuration commands received from client devices 110 a and 110 b to server 300. Server 300 may send and receive data messages across a data channel for communicating with end user devices 120 a and 120 b.
In example embodiments, a system and method for managing virtual machine configurations may be implemented in network environment 100, providing control proxy 200 for intercepting command messages being sent from a user of client device 110 a or 110 b to configure virtual machines in server 300. Control proxy 200 interprets the particular protocol command messages to determine which command was intended by the user. Control proxy 200 then checks selected criteria of the command messages against predefined policies to determine whether an operation corresponding to the intended command is permitted. If the operation is permitted, then control proxy 200 sends the command messages to server 300. For purposes of illustrating the techniques of such a system, it is important to understand the activities occurring within a given virtual environment. The following foundational information may be viewed as a basis from which the present disclosure may be properly explained. Such information is offered earnestly for purposes of explanation only and, accordingly, should not be construed in any way to limit the broad scope of the present disclosure and its potential applications.
Protecting a virtual computer environment presents certain complexities that are not associated with a purely physical computer environment. When physical computers are initially configured within a network, physical wires may be connected to the computers, wiring arrangements to appropriate physical components may be configured, memory components may be added, external devices may be added, and the like. Appropriate security may also be included. For example, firewalls may be configured in both hardware and software, proxy servers may be configured between computers, and any other desired security mechanism may be implemented. Modifications to the physical computer may require adding or removing physical components and adding, removing, or rerouting wiring. Thus, such procedures may be labor intensive and consequently, may be performed only as time and manual labor allows. Such changes in a physical environment may necessitate planning and deliberation. For example, in many business environments, implementations and modifications to physical systems are often scheduled during off-hours or work downtime, so as not to interfere with daily business transactions. Even if changes must be made during working hours, end users are typically notified of the impending work and any expected downtime.
In a virtual environment, however, a hypervisor or virtual machine monitor may control the operation of one or more virtual machines, each having an associated operating system and one or more associated applications. The hypervisor is the basic abstraction layer of software that may sit directly on the hardware of a virtual machine host below operating systems. It is responsible for central processing unit (CPU) scheduling and memory partitioning of the various virtual machines running on a hardware device. The hypervisor not only abstracts the hardware for the virtual machines, but also controls the execution of virtual machines as they share the common processing environment.
The initial configuration and any subsequent modifications of a virtual machine may occur by simply sending electronic commands to a virtual machine host. Such commands may be issued by anyone with appropriate privileges who can access the virtual machine host. Thus, virtual machines may be configured (e.g., created, cloned, deleted, started, stopped, modified, etc.) simply by an authorized user typing in commands, which are received and performed on the virtual machine host. Such configurations may be accomplished with greater speed and frequency than in a physical environment. In addition, because of the transparency and ease with which such configuration commands may be issued, multiple individuals with appropriate privileges could actually issue conflicting commands, thereby potentially causing frequent and perhaps undesirable changes to the virtual machines. Moreover, these changes could occur anytime, such as during peak working hours, without warning to end users and possibly resulting in undesirable affects on end users and any associated business activities. Virtual machines may also incur substantial damage if a security hacker or other unauthorized user penetrates the virtual environment, at least in part because the hacker may have access to multiple operating systems and applications.
While the isolation provided by a virtual environment may offer more security from attacks by malicious code and abnormal process ends from an application or operating system, virtual machines may, on the other hand, be more easily manipulated by network administrators and other authorized users than in a purely physical environment. For example, in virtual machine environments such as VMware ESX or VMware ESXi, any individual, such as a network administrator, with appropriate privileges may be allowed to simply type in commands to edit hardware configurations for any of the virtual machines on a host server. A virtual machine may be created, cloned, or deleted, or any virtual machine hardware configurations (e.g., processors, CD/DVD drives, floppy drives, memory, SCSI devices, network adapters, parallel ports, serial ports, etc.) may be added, removed or modified. Moreover, such configuration commands may be issued at any time, from any device so long as the user is authorized (e.g., has a valid password). Thus, without proper controls, the potential for such commands to be issued during a time that disrupts business activities is great. In addition, because configuration commands may be issued from various locations, authorized users could issue conflicting commands that cause problems for the end users and disruptions to associated business activities.
In one example scenario, many companies or organizations that conduct their businesses using large network systems may outsource their information technology (IT) support to a separate IT organization. Once the IT organization is given access and administrative privileges to the company's network, the company may have limited control over the activities undertaken by the IT organization to configure the virtual machines used by the company. Even well-intentioned configuration changes have the potential to disrupt business activities when performed during working hours without prior approval from and notice to the network owner. Thus, many companies in this scenario would benefit from a way to define policies that control the IT support organization's ability to modify virtual machine configurations within the network.
Hackers or other unauthorized users may also present problems in the virtual environment. Such individuals may attempt to gain administrative privileges on a virtual machine host server, such as, by acquiring an appropriate password and access to the network. If successful, the hacker or other unauthorized user may cause irreparable damage by issuing configuration commands and thereby adding, removing, or modifying the virtual machines and any associated virtual hardware. Thus, it has become very important to control or manage access to virtual machines based on configuration commands and defined policies associated with such configuration commands.
A system for managing virtual machine configurations, as outlined in FIG. 1, can resolve many of these issues. In accordance with one example implementation, a company or other organization that provides applications or services on network servers configured as virtual machine hosts can define policies that determine, for example, when and by whom particular configuration commands may be sent to the servers. These policies may be defined and evaluated in a control proxy that receives the configuration commands through a control channel from client devices. Also, the servers may be disabled from performing operations in response to configuration commands unless the commands are received from the control proxy. Thus, such a system would give companies or other organizations control over when and how their servers could be configured by network administrators and other users with administrative privileges.
Generally, virtual machine monitors (e.g., VMware ESX, VMware ESXi, Xen, Hyper-V, etc.) are hypervisors that can be employed to manage virtual machines and guest operating system (OS) instances. As used herein in this Specification, the term ‘virtual machine monitor’ is meant to include any such hypervisors, or other devices that can operate to manage one or more virtual machines.
Turning to the infrastructure of FIG. 1, a system for managing virtual machine configurations may be implemented in network environment 100, which may include additional servers, client devices, control proxies, and other devices not shown. Network environment 100 may be configured in any form including, but not limited to, local area networks (LANs), intranets, and wide area networks (WANs) such as the Internet. In one embodiment, client devices 110 a and 110 b and end user devices 120 a and 120 b may be operably coupled to network 130 (e.g., the Internet) by an Internet Service Provider (ISP) or through an Internet Server with dedicated bandwidth. In this embodiment, connections to network 130 may include any appropriate medium such as, for example, digital subscriber lines (DSL), telephone lines, T1 lines, T3 lines, wireless, satellite, fiber optics, cable, Ethernet, etc. or any combination thereof. In addition, gateways, routers, and the like may be used to facilitate electronic communication between client devices 110 a and 110 b and control proxy 200 and between end user devices 120 a and 120 b and server 300. Also, appropriate firewalls may be provided between network 130 and control proxy 200 and server 300. In another embodiment network 130 may represent a LAN to which client devices 110 a and 110 b are operably connected to communicate with control proxy 200 and to which end user devices 120 a and 120 b are operably connected to communicate with server 300. Network 130 may, in further embodiments, be implemented as a number of different combinations of networks, including for example, client device 110 a and end user device 120 a connected through a LAN and client device 110 b and end user device 120 b connected through the Internet.
Control proxy 200 and server 300 are operably connected to network 130. Logically, network 130 may be connected to control proxy 200 through the control channel for sending configuration command messages to control proxy 200 from client devices 110 a and 110 b. Network 130 may also be logically connected to server 300 through the data channel for sending data messages between end user devices 120 a and 120 b and server 300. In one embodiment, control proxy 200 does not receive data messages from client devices 110 a and 110 b or end user devices 120 a and 120 b. Rather, control proxy 200 is configured to only receive messages through the control channel, which include configuration command messages. One example embodiment includes network 130 supporting Simple Object Access Protocol (i.e., SOAP) messaging framework. SOAP is a protocol that may combine remote procedure calls (i.e., RPC) and Hypertext Transport Protocol (i.e., HTTP), allowing HTTP to be used as the transport for RPC messages. Although SOAP messages may be used in this example implementation, it will be apparent that the broad scope of the present disclosure could also be applied using other protocols.
In one example embodiment, control proxy 200 and server 300 may be implemented in an IT Headquarters of an organization or a data center, with client devices 110 a and 110 b being computers operated by individual users having network administrator privileges (e.g., authorization to configure and maintain computers, servers, and any other devices within a computer network). In this embodiment, end user devices 120 a and 120 b may be computers operated by users without administrative privileges, who remotely or locally access applications or services provided by server 300. Server 300 may provide applications or services only to end users within the organization that controls server 300 (e.g., employees) or it may provide applications or services to end users outside the organization (e.g., customers, Internet surfers, other businesses). Client devices 110 a and 110 b may include computers such as desktops, laptops, or any other computing device or console capable of sending configuration command messages to control proxy 200, using, for example the SOAP protocol. End user devices 120 a and 120 b may include computers such as desktops, laptops, or mobile or handheld computing devices (e.g., personal digital assistants (PDAs) or mobile phones) or any other computing device capable of receiving and sending data messages to server 300 through network 130. It should be noted that the network configurations and interconnections shown and described herein are for illustrative purposes only. One of ordinary skill in the art will appreciate that FIG. 1 is intended as an example and should not be construed to imply architectural limitations in the present disclosure.
Turning to FIG. 2, a simplified block diagram illustrates one embodiment of control proxy 200 that may be implemented in accordance with the present disclosure. Control proxy 200 may include hardware elements such as a memory element 210 and a processor 220 suitably configured to provide a platform for associated modules of control proxy 200. In addition, a suitable operating system (not shown) may be configured in control proxy 200 to appropriately manage the operation of hardware components therein. Control proxy 200 may include a protocol message module 230 for receiving configuration command messages. Protocol message module 230 understands the particular protocol (e.g., SOAP, etc.) of the command messages and determines the intended command of a user sending the command messages. Also included in control proxy 200 could be a policy database 240, a policy module 250 and an administration module 260. Policy database 240 may include entries corresponding to operations capable of being performed in server 300 and also may include entries corresponding to predefined policies associated with the operations. A management console 270 may be operably coupled to control proxy 200 for creating and/or updating policy database 240 with administration module 260. In one embodiment, management console 270 may be a McAfee ePolicy Orchestrator®.
Turning to FIG. 3, a simplified block diagram illustrates a server 300 that may be implemented in accordance with the present disclosure. Server 300 may be configured with, for example, VMware ESX or ESXi, SAP or other web services. In one example embodiment shown in FIG. 3, server 300 may include a virtual machine 310 and a virtual machine 320, which have respective operating systems 314 and 324 running respective applications 312 and 322. Server 300 may also include a virtual machine monitor (VMM) 330, which is, in one embodiment, a hypervisor that runs on hardware and which provides the capability of running multiple instances of operating systems 314 and 324 and associated applications 312 and 322, concurrently, by dynamically allocating the hardware resources to the operating systems 314 and 324 and applications 312 and 322 as needed. In this arrangement, applications 312 and 322 are logically run on top of respective operating systems 314 and 324, which are associated with respective virtual machines 310 and 320, and are provided with virtual hardware (e.g., processors, CD/DVD drives, floppy drives, memory, SCSI devices, network adapters, parallel ports, serial ports, etc.). Hardware components 340 beneath virtual machine monitor 330 may include a memory element 342 and a processor 344. Hardware components 340 may also include additional components such as, for example, network interface cards and disk drives. The entire configuration may be provided in a server (or some other network appliance). This implementation is only representing one possible example to which the present disclosure can apply. Any number of additional hypervisors or virtual elements could similarly benefit from the broad teachings discussed herein.
Typically, in server virtualization an authorized user is provided with an interface to manage a complete setup of virtual machines and the associated applications, operating systems, and virtual hardware. This management includes the hypervisor configuration and virtual machine configuration, including creation, deletion, modification, shutdown, startup, etc. In accordance with one embodiment of the present disclosure, server 300 is configured in “local access lockdown” such that even authorized users cannot successfully issue configuration commands directly to server 300. Instead, only configuration commands received from control proxy 200 will be performed. Thus, even if a user with administrative privileges bypasses control proxy 200 and connects directly to server 300, any configuration commands attempted by the user will not be executed because only configuration commands received in messages from control proxy 200 will be executed by server 300.
Not shown in FIGS. 2 and 3 is additional hardware that may be suitably coupled to control proxy processor 220 and server processor 344. Additional hardware may be in the form of memory management units (MMU), additional symmetric multiprocessing (SMP) elements, physical memory, Ethernet, peripheral component interconnect (PCI) bus and corresponding bridges, small computer system interface (SCSI)/integrated drive electronics (IDE) elements, etc.
Turning to FIG. 4, FIG. 4 is a simplified block diagram illustrating one implementation of a system 400 for managing virtual machine configurations in accordance with the present disclosure. In the example implementation, a VMware Infrastructure Client (i.e., VI client) 410 may be suitably coupled to a control proxy 420 for sending and receiving SOAP messages as previously described herein. Control proxy 420 may be operably connected to a VMware ESXi server 430 for sending permitted configuration command messages, received from VI client 410, to ESXi server 430. By way of example, a policy database 440 is shown with enumerated operations 442 (i.e., create, clone, delete, start, stop, modify, etc.) and policies 444 (i.e., user, time of day, date, host, etc.).
VI client 410 may allow an authorized user to select virtual machine configuration commands that correspond to operations for ESXi server 430, such as, for example, creating, cloning, starting, stopping, deleting, and modifying virtual machines, which includes any associated virtual hardware. Once the user has selected a command, VI client 410 may create SOAP messages to communicate the selected commands to ESXi server 430. Multiple SOAP messages may be sent for each command selected by the user, with the SOAP messages having a plurality of criteria such as user, host address, date, time of day, etc. embedded therein. Control proxy 420 intercepts the SOAP messages and reconstructs the messages to determine which configuration command was intended. One of the operations 442 in policy database 440 may then be identified as corresponding to the intended command. Once the configuration command and its corresponding operation from policy database 440 have been determined, policies 444 associated with the corresponding operation may be compared to any of the plurality of criteria from the SOAP messages to determine whether the corresponding operation is permitted. Control proxy 420 may then send the SOAP messages to ESXi server 430 if the corresponding operation is permitted. If the corresponding operation is not permitted, however, the control proxy 420 may send an error message back to the VI client 410.
Turning to FIG. 5, a simplified flowchart 500 is depicted illustrating a process associated with one implementation for managing virtual machine configurations. The process involves intercepting messages between client devices and a server, determining what configuration commands have been issued in the messages, and determining whether operations corresponding to the intended commands are permissible based on predefined policies. The process may be implemented in control proxy 200 as shown in FIGS. 1 and 2, which may be implemented in any suitable architecture as described herein.
The process may begin at step 510, where control proxy 200 receives configuration command messages from one of the client devices 110 a or 110 b. Because the configuration command options may be provided on client device 110 a or 110 b at a user-understandable level, typically, one user action will result in many messages being sent. Therefore, flow passes to step 520 to reconstruct the plurality of configuration command messages to determine what command the user intended, and to determine an operation in policy database 240 corresponding to the intended command. Once the configuration command messages have been reconstructed and the corresponding operation in policy database 240 has been determined, flow passes to step 530 to determine if the operation corresponding to the intended command is permitted by associated policies in the policy database 240. In this step, policies associated with the corresponding operation in policy database 240 may be compared to selected criteria from the configuration command messages. If the associated policies do not permit the corresponding operation to be performed, based on the selected criteria, flow passes to step 540 and an error message may be sent to the particular client device 110 a or 110 b that sent the configuration command messages. However, if the corresponding operation is permitted, then flow passes to step 550 and the configuration command messages are sent to server 300.
In one example implementation, a policy (“Policy T”) may be defined in policy database 240 as not allowing particular operations to be performed by any users from any client devices or hosts during a specified time of day, such as normal business hours (e.g., 9 am-5 pm). By way of example, Policy T may then be mapped to operations “delete”, “stop”, and “modify” in policy database 240 for all authorized users and all authorized hosts. If an authorized user initiates a command on client device 110 a or 110 b at 12 pm to modify the memory of virtual machine 310 or 320 in server 300, configuration command messages would be intercepted by control proxy 200. Control proxy 200 would determine the intended command from the configuration command messages and would then determine that the intended command corresponds to the “modify” operation in the policy database 240. The time of day (i.e., 12 pm) the command messages were issued would be determined from the plurality of criteria embedded in the command messages. When the time of day (i.e., 12 pm) is compared to Policy T, which is mapped to the “modify” operation in policy database 240, it would be determined that the modify operation is not permitted and, therefore, the configuration command messages would not be sent to server 300. Instead, an error message may be sent to the appropriate client device 110 a or 110 b. However, if the same authorized user initiated the same command at 6 pm, then, when the time of day (i.e., 6 pm) is compared to Policy T, it would be determined that the modify operation is permitted and therefore, the configuration command messages would be sent to server 300. It will be apparent that this is just one example scenario, and that many other selected criteria, such as, for example, the host, the date, the user, etc., may be evaluated and that the control proxy would determine whether the operation corresponding to the intended command is permitted or not permitted based on the particular policies associated with the operation.
Software for managing virtual machine configurations can be provided at various locations (e.g., within policy module 250, administration module 260, protocol message module 230). In one example implementation, this software is resident in a computer sought to be protected from a security attack (or protected from unwanted or unauthorized manipulations of a writable memory area). In other embodiments, software could be received or downloaded from a web server (e.g., in the context of purchasing individual end-user licenses for separate devices, separate control proxies, separate virtual machines, hypervisors, servers, etc.) in order to provide this system for managing virtual machine configurations.
In other examples, the system and method for managing virtual machine configurations could involve a proprietary element (e.g., as part of an antivirus solution), which could be provided in (or be proximate to) these identified elements, or be provided in any other device, server, network appliance, console, firewall, switch, information technology (IT) device, etc., or be provided as a complementary solution (e.g., in conjunction with a firewall), or provisioned somewhere in the network. As used herein in this Specification, the term ‘computer’ is meant to encompass these possible elements (VMMs, hypervisors, virtual devices, network appliances, routers, switches, gateway, processors, servers, loadbalancers, firewalls, or any other suitable device, component, element, or object) operable to affect or process electronic information in a security environment. Moreover, this computer may include any suitable hardware, software, components, modules, interfaces, or objects that facilitate the operations thereof. This may be inclusive of appropriate algorithms and communication protocols that allow for the effective management of virtual machine configurations. In addition, the system functions can be consolidated in any suitable manner. Along similar design alternatives, any of the illustrated modules and components of FIGS. 1-4 may be combined in various possible configurations: all of which are clearly within the broad scope of this Specification.
In certain example implementations, the functions of managing virtual machine configurations outlined herein may be implemented by logic encoded in one or more tangible media (e.g., embedded logic provided in an application specific integrated circuit (ASIC), digital signal processor (DSP) instructions, software (potentially inclusive of object code and source code) to be executed by a processor, or other similar machine, etc.). In some of these instances, a memory element (as shown in FIGS. 2 and 3) can store data used for the operations described herein. This includes the memory element being able to store software, logic, code, or processor instructions that are executed to carry out the activities described in this Specification. A processor can execute any type of instructions to achieve the operations detailed herein in this Specification. In one example, the processors (as shown in the FIGURES) could transform an element or an article (e.g., data) from one state or thing to another state or thing. In another example, the activities outlined herein may be implemented with fixed logic or programmable logic (e.g., software/computer instructions executed by a processor) and the elements identified herein could be some type of a programmable processor, programmable digital logic (e.g., a field programmable gate array (FPGA), an erasable programmable read only memory (EPROM), an electrically erasable programmable ROM (EEPROM)) or an ASIC that includes digital logic, software, code, electronic instructions, or any suitable combination thereof.
Any of these elements (e.g., a computer, a server, a control proxy, a network appliance, a firewall, a virtual machine monitor, any other type of virtual element, etc.) can include memory elements for storing information to be used in achieving the management of virtual machine configurations as outlined herein. Additionally, each of these devices may include a processor that can execute software or an algorithm to perform the management of virtual machine configurations activities as discussed in this Specification. These devices may further keep information in any suitable memory element (random access memory (RAM), ROM, EPROM, EEPROM, ASIC, etc.), software, hardware, or in any other suitable component, device, element, or object where appropriate and based on particular needs. Any of the memory items discussed herein (e.g., policy database, etc.) should be construed as being encompassed within the broad term ‘memory element.’ Similarly, any of the potential processing elements, modules, and machines described in this Specification should be construed as being encompassed within the broad term ‘processor.’ Each of the computers, network appliances, virtual elements, etc. can also include suitable interfaces for receiving, transmitting, and/or otherwise communicating data or information in a secure environment.
Note that with the examples provided herein, interaction may be described in terms of two, three, four, or more network elements. However, this has been done for purposes of clarity and example only. In certain cases, it may be easier to describe one or more of the functionalities of a given set of flows by only referencing a limited number of components or network elements. It should be appreciated that the networks and systems of FIGS. 1 and 4 (and their teachings) are readily scalable. The system implemented in network environment 100 can accommodate a large number of components, as well as more complicated or sophisticated arrangements and configurations. Accordingly, the examples provided should not limit the scope or inhibit the broad teachings of the system as potentially applied to a myriad of other architectures. In addition, the system has been described herein as operating in conjunction with particular VMware architectures; however, other architectures can readily be accommodated by the present solution.
It is also important to note that the steps described with reference to the preceding FIGURES illustrate only some of the possible scenarios that may be executed by, or within, the system and method for managing virtual machine configurations. Some of these steps may be deleted or removed where appropriate, or these steps may be modified or changed considerably without departing from the scope of the discussed concepts. In addition, a number of these operations have been described as being executed concurrently with, or in parallel to, one or more additional operations. However, the timing of these operations may be altered considerably. The preceding operational flows have been offered for purposes of example and discussion. Substantial flexibility is provided by the present disclosure in that any suitable arrangements, chronologies, configurations, and timing mechanisms may be provided without departing from the teachings of the discussed concepts.

Claims

1. A method, comprising:

receiving a plurality of command messages through a control channel, wherein the plurality of command messages includes one or more criteria;

reconstructing the plurality of command messages to determine an intended command for configuring one or more virtual machines on a server device, wherein the intended command corresponds to an operation defined in a policy database;

determining whether the plurality of command messages are received from a control proxy, wherein the server device is disabled from performing operations associated with the plurality of configuration commands based, at least in part, on whether they are received from the control proxy;

determining if the operation is permitted by comparing one or more policies associated with the operation to the one or more criteria; and

sending the plurality of command messages to the server device if the operation is permitted.

2. The method of claim 1, wherein the operation includes one of creating, cloning, deleting, starting, stopping, and modifying the one or more virtual machines.

3. The method of claim 1, wherein the operation includes configuring a selected one of a group of hardware components of one of the virtual machines, the group of hardware components consisting of: a processor, a CD drive, a DVD drive, a floppy drive, a memory element, a SCSI device, a network adapter, a parallel port, and a serial port.

4. The method of claim 1, wherein the plurality of command messages use Simple Object Access Protocol (SOAP) messaging framework.

5. The method of claim 1, wherein the control proxy is adapted to receive only the plurality of command messages through the control channel.

6. The method of claim 1, further comprising,

creating the policy database with the one or more policies and a plurality of operations for configuring the one or more virtual machines on the server device, wherein the one or more policies are mapped to selected operations of the plurality of operations.

7. The method of claim 1, further comprising:

sending an error message to be displayed on the client device when the operation corresponding to the intended command is not permitted.

8. The method of claim 1, wherein the one or more criteria includes a user sending the message, a time of day the message is sent, and an address of the client device.

9. The method of claim 1, wherein one of the policies includes a predefined time of day the operation is permissible, and wherein one of the criteria includes the time of day the message is sent.

10. A non-transitory media having logic stored therein to perform operations comprising:

11. The media of claim 10, wherein the operation includes one of creating, cloning, deleting, starting, stopping, and modifying the one or more virtual machines.

12. The media of claim 10, wherein the control proxy is adapted to receive only the plurality of command messages through the control channel.

13. The media of claim 10, the processor being operable to perform operations comprising:

14. The media of claim 10, the processor being operable to perform operations comprising:

15. The media of claim 10, wherein one of the policies includes a predefined time of day the operation is permissible, and wherein one of the criteria includes the time of day the message is sent.

16. A control proxy, comprising:

a memory component configured to store a policy database; and

a processor operable to execute instructions associated with a protocol message module and a policy module, including:

17. The control proxy of claim 16, wherein the operation includes one of creating, cloning, deleting, starting, stopping, and modifying the one or more virtual machines.

18. The control proxy of claim 16, wherein the control proxy is adapted to receive only the plurality of command messages through the control channel.

19. The control proxy of claim 16, wherein the processor is operable to execute instructions associated with an administration module comprising:

20. The control proxy of claim 16, wherein one of the policies includes a predefined time of day the operation is permissible, and wherein one of the criteria includes the time of day the message is sent.