Managing a server template

CROSS-REFERENCE TO RELATED APPLICATION

0001This application is a continuation of and claims priority to U.S. application Ser. No. 13/840,053, filed Mar. 15, 2013, entitled “Managing a Server Template”, the contents of which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

0002This description relates to virtual machines and templates.

BACKGROUND

0003In cloud computing environments, templates may be used to create virtual machines. It can be desirable to perform management tasks on the templates.

SUMMARY

0004According to one general aspect, a non-transitory computer-readable storage medium may comprise instructions for managing a server template stored thereon. When executed by at least one processor, the instructions may be configured to cause at least one computing system to at least convert the server template to a corresponding virtual machine, manage the corresponding virtual machine, and convert the corresponding virtual machine back into a template format.

0005According to one general aspect, a non-transitory computer-readable storage medium may comprise instructions for managing a server template stored thereon. When executed by at least one processor, the instructions may be configured to cause at least one computing system to at least determine that the first server is a template-type server, based on determining that the first server is a template-type server, determine whether a management resource pool has sufficient resources available to convert the first server from a template-type server to a first virtual machine, based on determining that the management resource pool does not have sufficient resources available to convert the first server from the template-type server to the first virtual machine, free up capacity in the management resource pool by removing an other virtual machine from the management resource pool, after freeing up capacity in the management resource pool, convert the first server to a first virtual machine, the first virtual machine corresponding to the first server, after converting the first server to the first virtual machine, manage the first virtual machine, after managing the first virtual machine, convert the first virtual machine back to the first template-type server, determine that the second server is a template-type server, based on determining that the second server is a template-type server, determine whether the management resource pool has sufficient resources available to convert the second server from a template-type server to a second virtual machine, based on determining that the management resource pool does have sufficient resources, convert the second server to a second virtual machine, the second virtual machine corresponding to the second server, after converting the second server to the second virtual machine, manage the second virtual machine, after managing the second virtual machine, convert the second virtual machine back to the second template-type server, determine that the third server is not a template-type server, and manage the third server.

0006According to another general aspect, a computer-implemented method may include converting a server template to a corresponding virtual machine, managing the corresponding virtual machine, and converting the corresponding virtual machine back into a template format.

0007The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

0008<figref idref="DRAWINGS">FIG. 1A</figref> is a diagram of a virtualization manager according to an example implementation.

0009<figref idref="DRAWINGS">FIG. 1B</figref> is a diagram of a server automation manager according to an example implementation.

0010<figref idref="DRAWINGS">FIG. 2A</figref> is a diagram of a virtual machine according to an example implementation.

0011<figref idref="DRAWINGS">FIG. 2B</figref> is a diagram of a template according to an example implementation.

0012<figref idref="DRAWINGS">FIG. 3</figref> is a diagram of a system in which conversion and management of templates may be performed according to an example implementation.

0013<figref idref="DRAWINGS">FIG. 4</figref> is a diagram showing a process for managing templates and virtual machines according to an example implementation.

0014<figref idref="DRAWINGS">FIG. 5</figref> shows a list of servers according to an example implementation.

DETAILED DESCRIPTION

0015Templates may be used to create virtual machines across multiple hypervisors. The virtual machines may be software implementations of machines or computers that run on a server. Multiple virtual machines may run on a single server; each virtual machine may have its own operating system and act as a distinct machine or computer. A hypervisor may manage the multiple virtual machines running on the single server. As described herein, an administrator may manage the virtual machines created based on templates by treating the template(s) as servers and/or as virtual machines. By managing and keeping the templates updated, the administrator can use the updated template(s) to create virtual machines. The administrator may perform server provisioning tasks on the template, updating the template and treating the template like a server.

0016To enable treating and/or managing the template as a server, a virtualization manager may convert the template into a virtual machine. The virtualization manager may assign a resource pool to the virtual machine and customize the virtual machine in accordance with specifications of the template. The virtualization manager, and/or another server such as a server automation manager and/or hypervisor, may perform management tasks on the template that has been converted into the virtual machine. The management tasks may include, for example, taking a snapshot of the server status at periodic intervals and auditing the changes, performing regulatory policy-based compliance on the server and remediating the virtual machine and correcting the template if the server is found to be non-compliant, copying files to the virtual machine and installing the files, performing patch analysis and installing needed patches, gathering information about the template and displaying the gathered information in a browser, and converting the virtual machine back to the updated template.

0017Hypervisors and/or virtualization managers and server automation managers that support creating virtual machines based on templates may manage the templates that are converted into virtual machines. The templates may be converted and managed, including updating the templates, periodically. The hypervisors, virtualization managers, and/or server automation managers may thereby manage the templates like servers.

0018<figref idref="DRAWINGS">FIG. 1A</figref> is a diagram of a virtualization manager <b>102</b> according to an example implementation. The virtualization manager <b>102</b> may support the virtual machines and templates. The templates may be created as virtual machines; the virtual machines, whether created based on a template or not, may run on hypervisors. The virtualization manager <b>102</b> may manage changes to virtual machines and template-type servers. The template-type servers may also be referred to as ‘server templates’ herein. The virtualization manager <b>102</b> may convert server templates to corresponding virtual machines, manage the corresponding virtual machines, and convert the corresponding virtual machines back into server templates. The virtualization manager <b>102</b> may, for example, convert server templates to corresponding virtual machines by making copies of the server templates and adding identification information to the copies. The virtualization manager <b>102</b> may convert the corresponding virtual machine back into the server template by removing the identification information from the copy, and deleting the original server template, according to an example implementation.

0019The virtualization manager <b>102</b> may perform functions with respect to server templates, such as converting the server templates to the corresponding virtual machines and converting the corresponding virtual machine back into the server templates. While <figref idref="DRAWINGS">FIG. 1A</figref> shows various modules included in a single virtualization manager <b>102</b>, this is merely an example. Some or all of the functions and processes described with respect to the virtualization manager <b>102</b>, as well as a server automation manager <b>116</b> shown in <figref idref="DRAWINGS">FIG. 1B</figref>, may be performed by a single computing system, or may be distributed and/or performed by other computing systems.

0020The virtualization manager <b>102</b> may include a converter <b>104</b>. The converter <b>104</b> may convert server templates to corresponding virtual machines and back into server templates. The converter <b>104</b> may convert a server template to a corresponding virtual machine by, for example, adding identification information to a server template and/or to a copy of the server template. In the example in which the converter <b>104</b> adds identification information to a copy of the server template, the converter <b>104</b> may copy the server template and add the identification information to the copy after copying the server template.

0021<figref idref="DRAWINGS">FIG. 2A</figref> is a diagram of a virtual machine <b>200</b>A according to an example implementation. The virtual machine <b>200</b>A may act as a machine and/or computing device running within a server. The virtual machine <b>200</b>A may include identification information <b>202</b>. The converter <b>104</b> shown in <figref idref="DRAWINGS">FIG. 1A</figref> may have added the identification information to the server template and/or the copy of the server template as part of the conversion from the server template to the virtual machine. The identification information <b>202</b> may include, for example, a name <b>204</b> of the virtual machine <b>200</b>A, an internet protocol (IP) address <b>206</b> of the virtual machine <b>200</b>A, and an operating system license key <b>208</b>. The virtual machine <b>200</b>A may also include an operating system <b>210</b>A, applications <b>212</b>A running on the virtual machine <b>200</b>A, and files <b>214</b>A included in or stored on the virtual machine <b>200</b>A.

0022The converter <b>104</b> may also convert the corresponding virtual machine back to the server template by removing identification information from the server template or from the corresponding virtual machine. The identification information may also be left in the server template and remain unused after the corresponding virtual machine has been converted back to the server template. <figref idref="DRAWINGS">FIG. 2B</figref> is a diagram of a template <b>200</b>B according to an example implementation. In this example, in which the identification information has been removed, the template <b>200</b>B, either before conversion to the virtual machine or after conversion from the virtual machine, may be similar to the virtual machine <b>200</b>A but not include the identification information <b>202</b>. The template <b>200</b>B may include, for example, an operating system <b>210</b>B, applications <b>212</b>B running on the template <b>200</b>B, and files <b>214</b>B stored on the template <b>200</b>B.

0023Creation of a virtual machine corresponding to a template may require computing resources, such as processing capacity and/or access to microprocessor functions, memory, and communication (input and/or output) nodes. The virtualization manager <b>102</b> may create the virtual machine(s) with computing resources managed by or included in the virtualization manager <b>102</b>, may determine whether sufficient computing resources are available to create the virtual machine(s), and/or may free up computing resources such as by removing other virtual machines.

0024Returning to <figref idref="DRAWINGS">FIG. 1A</figref>, the virtualization manager <b>102</b> may also include a resource checker <b>106</b>. The resource checker <b>106</b> may check and/or analyze the computing resource usage in a resource pool, shown and described with respect to <figref idref="DRAWINGS">FIG. 3</figref>, managed by the virtualization manager <b>102</b>. In some implementations, the resource checker <b>106</b> may check and/or analyze the computing resource usage in response to a request from a resource manager <b>132</b> included in the server automation manager <b>116</b> shown in <figref idref="DRAWINGS">FIG. 1B</figref>. The resource checker <b>106</b> may add the actual computing resource usage of some or all virtual machines and/or server templates accessing the resource pool, may add the computing resources reserved for some or all of the virtual machines and/or server templates reserving resources of the resource pool, or determine usage of the computing resources of the resource pool based on a function of both actual use and reservation of the computing resources of the resource pool. Based on determining the usage of the computing resources of the resource pool, the resource checker <b>106</b> may determine whether sufficient computing resources exist in the resource pool to create a new virtual machine based on a server template. The resource checker <b>106</b> may send a message to the resource manager <b>132</b> indicating whether sufficient computing resources exist in the resource pool.

0025If sufficient resources do exist in the resource pool, then the converter <b>104</b> may create the new virtual machine and/or convert the server template into the corresponding virtual machine. If sufficient resources do not exist in the resource pool, then the virtualization manager <b>102</b> may need to remove or delete one or more existing virtual machines from the resource pool. The virtualization manager <b>102</b> may remove or delete the one or more existing virtual machines in response to an instruction from the server automation manager <b>116</b>. The existing virtual machine(s) to be removed or deleted may be a virtual machine created based on a template so that the server automation manager <b>116</b> could perform management tasks on the virtual machine. In an example implementation, the virtualization manager <b>102</b> should not remove or delete a virtual machine in production use.

0026The virtualization manager <b>108</b> may also include a remover <b>108</b>. The remover <b>108</b> may remove virtual machines from the resource pool. The remover <b>108</b> may remove virtual machines if, for example, the resource checker <b>106</b> determines that the resource pool lacks sufficient resources to create a new virtual machine, and/or in response to an instruction from the server automation manager <b>116</b> to remove or delete a virtual machine. For example, if a virtual machine is to be created based on a server template (and/or the server template is to be converted into a corresponding virtual machine), but the resource pool lacks sufficient resources to create the new virtual machine, the remover <b>108</b> may remove and/or delete a currently existing virtual machine from the resource pool, freeing computing resources in the resource pool for the new virtual machine.

0027When performing management tasks on servers, the virtualization manager <b>102</b> may perform different processes or functions on the servers based on the type of server. For example, if the server is a template-type server or server template, the virtualization manager <b>102</b> may convert the server template into a corresponding virtual machine before the server automation manager <b>116</b> performs the management tasks, and convert the corresponding virtual machine back into a template server after the server automation manager <b>116</b> performs the management tasks. If the server is not a template-type server, the server automation manager <b>116</b> may perform the management tasks without the virtualization manager <b>102</b> performing any conversion.

0028The virtualization manager <b>102</b> may include at least one processor <b>110</b>. The at least one processor <b>110</b> may include one or more processors with one or multiple cores capable of performing functions and executing instructions, such as the functions and processes described herein.

0029The virtualization manager <b>102</b> may also include at least one memory <b>112</b>. The at least one memory <b>112</b> may store data and/or instructions, such as instructions for performing the functions and processes described herein. The memory <b>112</b> may store, for example, instructions that, when executed by the at least one processor <b>110</b>, cause a computing system such as the virtualization manager <b>102</b> to perform the functions and processes described herein. The memory <b>112</b> may also store data, such as data describing the templates and virtual machines described herein.

0030The virtualization manager <b>102</b> may also include an input/output device <b>114</b>. The input/output device <b>114</b> may send and receive information from and to the virtualization manager <b>102</b>. The input/output device <b>114</b> may include separate devices, with one or more devices for input and one or more devices for output, or may be combined into a single device. The input/output device <b>114</b> may include multiple interfaces. For example, input/output device <b>114</b> may include a keyboard and mouse for user input, and may include a wired or wireless communication interface for receiving signals from one or multiple computing devices. The input/output device <b>114</b> may also include a display or monitor as well as a wired or wireless communication interface for sending signals to one or multiple computing devices, such as servers, templates, and/or virtual machines. The input/output device <b>114</b> may also communicate with virtual machines existing on a same computing system as the virtualization manager <b>102</b> by passing messages to the virtual machines, according to an example implementation.

0031<figref idref="DRAWINGS">FIG. 1B</figref> is a diagram of the server automation manager <b>116</b> according to an example implementation. The server automation manager <b>116</b> may perform management tasks on the servers. The server automation manager <b>116</b> may also determine whether the servers are template-type servers or server templates, and instruct the virtualization manager <b>102</b> to convert a server template to a virtual machine if the server automation manager <b>116</b> determines that the server is a template-type server or server template.

0032The server automation manager <b>116</b> may include a type determiner <b>118</b>. The type determiner <b>118</b> may determine whether a server is a server template or a virtual machine. The type determiner <b>118</b> may determine whether the server is a server template or a virtual machine based on fields or data stored in or associated with the server, or based on a list of servers. The list of servers may indicate a type for each server in the list, such as template-type or virtual machine. An example of a list of servers indicating the type for each server is shown in <figref idref="DRAWINGS">FIG. 5</figref>. The virtualization manager <b>102</b> may perform type conversion, as well as creating a copy of the server and later removing the original server, based on the type determiner <b>118</b> of the server automation manager <b>116</b> determining that the server is a template-type server, before the server automation manager <b>116</b> performs management tasks, or the server automation manager <b>116</b> may simply perform the management tasks without performing any conversion based on the type determiner <b>118</b> determining that the server is not a template-type server, according to example implementations.

0033The server automation manager <b>116</b> may also include a server selector <b>120</b>. The server selector <b>120</b> may select a server upon which the virtualization manager <b>102</b> will perform functions, such as type determination, conversion, management, and/or removal. The server selector <b>120</b> may select the server in sequential order based on a queue or list, such as the list shown in <figref idref="DRAWINGS">FIG. 5</figref>, or may select the server based on priority information transmitted to the server selector <b>120</b>, according to example implementations.

0034The server automation manager <b>116</b> may also include a resource manager <b>122</b>. The resource manager <b>122</b> may send a request to the resource checker <b>106</b> of the virtualization manager <b>102</b> shown in <figref idref="DRAWINGS">FIG. 1A</figref> to determine whether sufficient resources exist in the resource pool to convert a template to a virtual machine. If the resource checker <b>106</b> determines that sufficient resources do not exist, and sends the resource manager <b>122</b> a message indicating that sufficient resources do not exist, then the resource manager <b>122</b> may, in response to receiving the message indicating that sufficient resources do not exist, send an instruction to the remover <b>108</b> of the virtualization manager <b>102</b> to remove a virtual machine from the resource pool. The remover <b>108</b> may, in response to receiving the instruction to remove a virtual machine from the resource pool, delete or remove a virtual machine from the resource pool as described above with respect to <figref idref="DRAWINGS">FIG. 1A</figref>.

0035The server automation manager <b>116</b> may perform management tasks on the virtual machine and/or server template. The server automation manager <b>116</b> may perform management tasks on virtual machines that were not created from templates, and/or may perform management tasks on virtual machines that were created from, correspond to, or were converted from, templates. When the server automation manager <b>116</b> performs the management tasks on virtual machines that were created from, correspond to, or were converted from templates, the server automation manager <b>116</b> may perform the management tasks after the creation or conversion. The management tasks may include provisioning, patching, presenting, copying, and policy checking, as non-limiting examples.

0036The server automation manager <b>116</b> may include, for example, a configuration manager <b>124</b>. The configuration manager <b>124</b> may perform server provisioning tasks on corresponding virtual machines which were created based on templates. The configuration manager <b>124</b> may, for example, set up the corresponding virtual machines for initial use, providing the corresponding virtual machines with identification and authorization information for users to access information stored or accessed by the virtual machines.

0037The server automation manager <b>116</b> may also include a patcher <b>126</b>. The patcher <b>126</b> may patch an operating system and/or application(s) of the server template or virtual machine. The patcher <b>126</b> may also determine whether a server template or virtual machine needs a patch to its respective operating system and/or application(s). For example, the patcher <b>126</b> may receive an operating system patch release or an application patch release, and information regarding which systems need the patch, from a vendor of the operating system or application. The patcher <b>126</b> may determine whether a given virtual machine or server template needs the operating system or application patch. If the patcher <b>126</b> determines that the virtual machine or server template does need the operating system or application patch, then the patcher <b>126</b> may apply the operating system or application patch to the virtual machine or server template.

0038The server automation manager <b>116</b> may also include a presenter <b>128</b>. The presenter <b>128</b> may present contents of the server template. The presenter <b>128</b> may present the contents in a browser. The presenter <b>128</b> may, for example, gather information which a user or administrator desires to view or browse, and display the information in the browser. The displayed information may include, for example, computing resources available and/or used by the server template, files or applications stored or installed on the server template, and/or processes running on the server template. By browsing the contents of the server template, an administrator may identify which template to use to create virtual machines.

0039The server automation manager <b>116</b> may also include a copier <b>130</b>. The copier <b>130</b> may copy files and/or new applications into the corresponding virtual machine created based on the template. The copier <b>130</b> may, for example, copy files selected by an administrator into the corresponding virtual machine, and install associated programs onto the corresponding virtual machine. The copier <b>130</b> may also copy and/or install new applications onto a corresponding virtual machine.

0040The server automation manager <b>116</b> may also include a policy engine <b>132</b>. The policy engine <b>132</b> may perform regulatory tasks on a virtual machine, such as determining whether the virtual machine and/or server template, based on which the virtual machine was created, complies with regulatory and/or policy requirements. The policy engine <b>132</b> may, for example, store regulatory requirements, such as data speed, privacy protection requirements, and/or energy usage, and compare the performance and/or processes of the virtual machine or template to the stored regulatory requirements. The policy engine <b>132</b> may provide a report of the comparison to an administrator, or may notify the administrator only if the policy engine determines that some regulations and/or policy requirements are not being complied with.

0041The server automation manager <b>116</b> may include at least one processor <b>134</b>. The at least one processor <b>134</b> may include one or more processors with one or multiple cores capable of performing functions and executing instructions, such as the functions and processes described herein.

0042The server automation manager <b>116</b> may also include at least one memory <b>136</b>. The at least one memory <b>136</b> may store data and/or instructions, such as instructions for performing the functions and processes described herein. The memory <b>136</b> may store, for example, instructions that, when executed by the at least one processor <b>134</b>, cause a computing system such as the server automation manager <b>116</b> to perform the functions and processes described herein. The memory <b>136</b> may also store data, such as data describing the templates and virtual machines described herein.

0043The server automation manager <b>116</b> may also include an input/output device <b>138</b>. The input/output device <b>138</b> may send and receive information from and to the virtualization manager <b>102</b>. The input/output device <b>138</b> may include separate devices, with one or more devices for input and one or more devices for output, or may be combined into a single device. The input/output device <b>138</b> may include multiple interfaces. For example, input/output device <b>138</b> may include a keyboard and mouse for user input, and may include a wired or wireless communication interface for receiving signals from one or multiple computing devices. The input/output device <b>138</b> may also include a display or monitor as well as a wired or wireless communication interface for sending signals to one or multiple computing devices, such as servers, templates, and/or virtual machines. The input/output device <b>138</b> may also communicate with virtual machines existing on a same computing system as the server automation manager <b>116</b> by passing messages to the virtual machines, according to an example implementation.

0044<figref idref="DRAWINGS">FIG. 3</figref> is a diagram of a system in which conversion and management of templates may be performed according to an example implementation. The system may include the virtualization manager <b>102</b> which converts templates, such as templates <b>306</b>A, <b>306</b>B, <b>306</b>C, <b>306</b>D, <b>306</b>E. The system may also include the server automation manager <b>116</b>. The server automation manager <b>116</b> may perform management functions on servers, such as virtual machines and templates. The system may also include virtual machines, such as virtual machines <b>304</b>A, <b>304</b>B, <b>304</b>C, <b>304</b>D, <b>304</b>E, <b>304</b>F, <b>304</b>G, <b>304</b>H. The virtual machines may be running on a single machine, such as the virtualization manager <b>102</b>.

0045The virtualization manager <b>102</b> may manage resource pool(s) <b>308</b>A, <b>308</b>B. The resource pool(s) <b>308</b>A, <b>308</b>B may include resources, such as processing capacity and/or access to microprocessor functions, memory, and/or communication (input and/or output) nodes which virtual machines may utilize, and in which virtual machines may be created and in which copies of templates may be made. The resource pool <b>308</b>B may be created for the purpose of managing the templates <b>314</b>A, <b>314</b>B, <b>314</b>C, <b>314</b>D, <b>314</b>E. The resource pool <b>308</b>B may be limited and may be able to accommodate only a limited number of virtual machines and/or server templates. The resource pool <b>308</b>B may not have enough resources to accommodate the virtual machines <b>314</b>A, <b>314</b>B, <b>314</b>C, <b>314</b>D, <b>314</b>E corresponding to all of the templates <b>306</b>A, <b>306</b>B, <b>306</b>C, <b>306</b>D, <b>306</b>E. The virtualization manager <b>102</b> may not be able to convert server templates into virtual machines after the resources in the resource pool <b>308</b>A, <b>308</b>B have reached a maximum limit or threshold.

0046The system may also include the resource pools <b>308</b>A, <b>308</b>B. The resource pools <b>308</b>A, <b>308</b>B may include computing resources, such as processors, memory, and/or communication devices in which the templates and servers may run and perform functions. The resource pools <b>308</b>A, <b>308</b>B may access the at least one processor(s) <b>110</b>, <b>134</b>, at least one memory <b>112</b>, <b>136</b>, and/or input/output device(s) of the virtualization manager <b>102</b> and/or server automation manager <b>116</b>, and/or may access computing resources of one or more other computing devices. The resource pool <b>308</b>A may store and run a number of virtual machines <b>310</b>A, <b>310</b>B, <b>310</b>C, <b>310</b>D, <b>310</b>E, <b>310</b>F. The resource pool <b>308</b>B, which may be considered a ‘management cache’, may store and run a number of corresponding virtual machines <b>312</b>A, <b>312</b>B which were created based on the templates <b>314</b>A, <b>314</b>B, <b>314</b>C, <b>314</b>D, <b>314</b>E. The virtual machines <b>312</b>A, <b>312</b>B representing templates <b>314</b>A, <b>314</b>B, <b>314</b>C, <b>314</b>D, <b>314</b>E may have been created based on the templates <b>306</b>A, <b>306</b>B, <b>306</b>C, <b>306</b>D, <b>306</b>E.

0047<figref idref="DRAWINGS">FIG. 4</figref> is a diagram showing a process for managing servers (<b>402</b>), including managing templates and virtual machines, according to an example implementation. The managing may be performed with respect to a set of target servers, which may include a set of virtual machines and templates. The process shown in <figref idref="DRAWINGS">FIG. 4</figref> may be performed by a single computing device, or distributed among multiple computing devices. In an example implementation, the processes may be distributed between the virtualization manager <b>102</b> and the server automation manager <b>116</b>.

0048The process may include the server automation manager <b>116</b> getting a next server (<b>404</b>). The server automation manager <b>116</b> may get the next server (<b>404</b>) by, for example, retrieving a next server on a list such as the list shown in <figref idref="DRAWINGS">FIG. 5</figref>, by selecting a server with a highest priority level, by selecting a server which has been waiting a longest time, based on a combination of priority level and waiting time, or other techniques used to choose a server that needs to be managed.

0049The process may also include the server automation manager <b>116</b> determining whether the server is a template (<b>406</b>). The server automation manager <b>116</b> may determine whether the server is a template by checking the list, which may indicate whether the server is a template or is not a template, or by checking fields or data included in or associated with the server. If the server is not a template, then the process may include the server automation manager <b>116</b> managing the server (<b>416</b>). Managing the server (<b>416</b>) may include provisioning tasks, patching, presenting contents of the server, copying the server, deploying files, configuration, or applications to the server, and/or determining whether the server complies with policy requirements, according to example implementations.

0050If the server is a template, then the server automation manager <b>116</b> may determine whether the server template is already available and/or cached in management cache (<b>408</b>). The management cache may be considered the resource pool <b>308</b>B shown in <figref idref="DRAWINGS">FIG. 3</figref>. The management cache may include storage and/or memory which allows the virtualization manager <b>102</b> to perform management tasks on a server template without converting the server template into a virtual machine. The management cache may be included, for example, in the at least one memory <b>112</b> of the virtualization manager <b>102</b>, the at least one memory <b>136</b> of the server automation manager <b>116</b>, and/or the resource pool <b>308</b>B shown in <figref idref="DRAWINGS">FIG. 1</figref>. If the server template is already available in management cache, then the server automation manager <b>116</b> may manage the server template (<b>416</b>).

0051If the server template is not already available in management cache, then the server automation manager <b>116</b> may determine whether resource capacity is available in the management resource pool <b>308</b>A, <b>308</b>B (<b>410</b>) to convert the server template into a virtual machine. The server automation manager <b>116</b> may determine whether resource capacity is available by the resource manager <b>122</b> sending a request to the resource checker <b>106</b> of the virtualization manager <b>102</b>. If resource capacity is available in the management pool, then the virtualization manager <b>102</b> may convert the server template into a virtual machine by creating a virtual machine based on the server template in the resource pool <b>308</b>A, <b>308</b>B (<b>414</b>). Creating the virtual machine may include, for example, making a copy of the template and adding identification information.

0052If resource capacity is not available in the management resource pool, then the virtualization manager <b>102</b> may free up capacity in the resource pool <b>308</b>A, <b>308</b>B by removing one or more virtual machines from the resource pool <b>308</b>A, <b>308</b>B (<b>412</b>). The virtual machines may be removed by, for example, deleting the virtual machines from the resource pool <b>308</b>A, <b>308</b>B. The virtualization manager <b>102</b> may determine which virtual machine(s) to remove or delete based, or example, on cache clearing techniques, such as least recently used or randomly. After freeing up capacity in the resource pool by removing some virtual machines, the virtualization manager <b>102</b> may create the corresponding virtual machine based on the server template in the management resource pool (<b>414</b>).

0053After the corresponding virtual machine has been created in the management resource pool, the server automation manager <b>116</b> may manage the server (<b>416</b>). At this time the server is a virtual machine. Managing the server (<b>416</b>) may include, for example, performing server provisioning tasks on the server, patching an operating system of the server, presenting or displaying contents of the server in a browser, copying a file into the server, taking a snapshot of the server, and determining whether the server complies with regulatory policy.

0054After managing the server (<b>416</b>), the server automation manager <b>116</b> may determine whether the server was a template (<b>418</b>). The server automation manager <b>116</b> may determine whether the server was a template by, for example, checking the list of servers which identifies which servers were templates and which servers were virtual machines (or non-template based servers), or by checking a field or data stored within or associated with the server. If the server was not a template, then the server automation manager <b>116</b> may determine whether there are any more servers to manage (<b>424</b>). If there are more servers to manage, then the server automation manager <b>116</b> may get the next server (<b>404</b>) and perform the processes described herein on the next server. If there are not more servers to manage, then the process may be considered finished (<b>426</b>).

0055If the server automation manager <b>116</b> determines that the server was a template, then the virtualization manager <b>102</b> may convert the server back into the template (<b>422</b>). The server automation manager <b>116</b> may determine whether management actions were performed on the corresponding virtual machine (<b>420</b>). If management actions were not performed on the corresponding virtual machine, no further action may need to be performed with respect to the server, and then the server automation manager <b>116</b> may determine whether there are any more servers to manage (<b>424</b>). If management actions were performed but did not result in changes to the server, no further action may need to be performed with respect to the server, and then the server automation manager <b>116</b> may determine whether there are any more servers to manage (<b>424</b>). If management actions were performed on the corresponding virtual machine which did result in changes to the corresponding virtual machine, then the virtualization manager <b>102</b> may convert the virtual machine back to the associated template (<b>422</b>). In the situations in which either no management actions were performed or management actions were performed but did not result in changes to the server, the virtualization manager <b>102</b> may optionally still convert the virtual machine back into the associated template (<b>422</b>).

0056Converting the virtual machine back to the associated template (<b>422</b>) may include the remover <b>108</b> of the virtualization manager <b>102</b> removing the identification information from the corresponding virtual machine and removing and/or deleting the previous server template maintained by the virtualization manager <b>302</b>. After the virtualization manager <b>102</b> converts the virtual machine back to the associated template, the server automation manager <b>116</b> may determine whether there are any more servers to manage (<b>424</b>), and if there are not any more servers to manage, then the process may be considered finished (<b>426</b>).

0057Servers may be converted and managed serially, or many servers may be converted and managed in parallel and/or at a same time. While <figref idref="DRAWINGS">FIG. 4</figref> shows processes being performed serially, multiple processes may be performed at a same time in a pipeline technique, and/or a single process may be performed concurrently on multiple servers, according to example implementations.

0058<figref idref="DRAWINGS">FIG. 5</figref> shows a list of servers according to an example implementation. The list identifies the servers by number and indicates the type for the servers. The type may include either a non-template based server, which may be a virtual machine or a physical server, or a template-based server. The type determiner <b>118</b> shown and described with respect to <figref idref="DRAWINGS">FIG. 1B</figref> may check the list shown in <figref idref="DRAWINGS">FIG. 5</figref> at (<b>406</b>) and (<b>418</b>) of the process shown and described with respect to <figref idref="DRAWINGS">FIG. 4</figref> to determine whether a server was a template or a server (such as a non-template based server).

0059The server automation manager <b>116</b> may, for example, determine that server ‘0’ is not a template, manage server ‘0’ without conversion, determine that server ‘1’ is not a template, manage server ‘1’ without conversion, determine that server ‘2’ is a template, determine that the resource pool <b>308</b>B does not have sufficient resources to convert server ‘2’ into a virtual machine, remove an existing virtual machine from the resource pool <b>308</b>B, convert server ‘2’ into a virtual machine, manager server ‘2’, determine that server ‘2’ was a template, convert server ‘2’ back into a template, determine that server ‘3’ is a template, determine that sufficient resources are available in the resource pool <b>308</b>B to convert server ‘3’ into a virtual machine, convert server ‘3’ into a virtual machine without removing any virtual machines from the resource pool <b>308</b>B, manage server ‘3’, determine that server ‘3’ was a template, convert server ‘3’ back into a template, determine that server ‘4’ is not a template, and manager server ‘4’ without performing any conversion on server ‘4’. Similar functions and processes may be performed on servers ‘5’ through ‘15’ based on their indicated type.

0060Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Implementations may implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. A computer program, such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

0061Method steps may be performed by one or more programmable processors executing a computer program to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

0062Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory may be supplemented by, or incorporated in special purpose logic circuitry.

0063To provide for interaction with a user, implementations may be implemented on a computer having a display device, e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.

0064Implementations may be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation, or any combination of such back-end, middleware, or front-end components. Components may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.

0065While certain features of the described implementations have been illustrated as described herein, many modifications, substitutions, changes and equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the embodiments of the invention.