The present invention relates generally to cloud computing, and more particularly to optimizing the deployment of virtual machines by pre-generating a virtual machine's first-boot metadata (e.g., RSA key, Globally Unique IDentifier (GUID)) by the cloud controller.
In a cloud computing environment, computing is delivered as a service rather than a product, whereby shared resources, software and information are provided to computers and other devices as a metered service over a network, such as the Internet. In such an environment, computation, software, data access and storage services are provided to users that do not require knowledge of the physical location and configuration of the system that delivers the services.
In a virtualized computer environment, such as may be implemented in a physical cloud computing node of the cloud computing environment, the virtualized computer environment includes a virtual operating system. The virtual operating system includes a common base portion and separate user portions that all run on a physical computer. The physical computer is referred to as a host. The common base portion may be referred to as a hypervisor and each user portion may be called a guest. Each guest is a logical partition of physical resources of the computer. A guest operating system runs on each guest, and the guest appears to the guest operating system as a real computer. Each guest operating system may host one or more virtual machines.
An image of the virtual operating system contains many pieces of unique metadata that are often generated on the first boot to ensure randomness and security, such as a RSA key, a Globally Unique IDentifier (GUID), a Secure Sockets Layer (SSL) certificate and a Lightweight Third-Party Authentication (LTPA) key. Currently, the virtual machine generates these metadata at deployment time. Since some of the metadata requires extensive time to generate, the deployment time of the instance of the virtual machine can be lengthy. If, however, the virtual machine can be relieved of generating such metadata, the deployment time could be lessened. As a result, instead of the cloud's limited resources being used on first-boot activities, such as generating these first-boot metadata, such resources could be used for other activities.
In one embodiment of the present invention, a method for optimizing virtual machine deployment comprises pre-generating a virtual machine's first-boot metadata prior to deployment of the virtual machine. The method further comprises storing the pre-generated first-boot metadata. Furthermore, the method comprises deploying the virtual machine. Additionally, the method comprises receiving a request from an agent of the virtual machine requesting the pre-generated first-boot metadata. The method additionally comprises retrieving the requested pre-generated first-boot metadata. Furthermore, the method comprises signing the retrieved pre-generated first-boot metadata with a private key to generate a signature. In addition, the method comprises transmitting, by a processor, a public key, the signature and the retrieved pre-generated first-boot metadata to the agent of the virtual machine.
Other forms of the embodiment of the method described above are in a system and in a computer program product.
The foregoing has outlined rather generally the features and technical advantages of one or more embodiments of the present invention in order that the detailed description of the present invention that follows may be better understood. Additional features and advantages of the present invention will be described hereinafter which may form the subject of the claims of the present invention.
A better understanding of the present invention can be obtained when the following detailed description is considered in conjunction with the following drawings, in which:
The present invention comprises a method, system and computer program product for optimizing virtual machine deployment. In one embodiment of the present invention, a cloud controller pre-generates and stores a virtual machine's first-boot metadata (e.g., a RSA key, a GUID identifier, a SSL certificate and a LTPA key) prior to the deployment of the virtual machine so that the virtual machine does not need to generate such metadata at deployment time thereby reducing the deployment time of the virtual machine. Instead, after the deployment and activation of the virtual machine, an activation agent running on the virtual machine requests the pre-generated first-boot metadata from the cloud controller. The cloud controller retrieves the requested pre-generated first-boot metadata and signs the retrieved pre-generated first-boot metadata with a private key to generate a signature. The cloud controller transmits the requested pre-generated first-boot metadata, the signature, and a public key, corresponding to the private key used to generate the signature, to the requesting activation agent of the virtual machine thereby allowing the virtual machine to validate the authenticity and integrity of the pre-generated first-boot metadata. By reducing the deployment time for the virtual machine, cloud resources can be used for other activities.
In the following description, numerous specific details are set forth to provide a thorough understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention may be practiced without such specific details. In other instances, well-known circuits have been shown in block diagram form in order not to obscure the present invention in unnecessary detail. For the most part, details considering timing considerations and the like have been omitted inasmuch as such details are not necessary to obtain a complete understanding of the present invention and are within the skills of persons of ordinary skill in the relevant art.
It is understood in advance that although this disclosure includes a detailed description on cloud computing, implementation of the teachings recited herein are not limited to a cloud computing environment. Rather, the embodiments of the present invention are capable of being implemented in conjunction with any type of clustered computing environment now known or later developed.
In any event, the following definitions have been derived from the “The NIST Definition of Cloud Computing” by Peter Mell and Timothy Grance, dated September 2011, which is cited on an Information Disclosure Statement filed herewith, and a copy of which is provided to the U.S. Patent and Trademark Office.
Cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. This cloud model is composed of five essential characteristics, three service models, and four deployment models.
Characteristics are as follows:
On-Demand Self-Service: A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed, automatically without requiring human interaction with each service's provider.
Broad Network Access: Capabilities are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, tablets, laptops and workstations).
Resource Pooling: The provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state or data center). Examples of resources include storage, processing, memory and network bandwidth.
Rapid Elasticity: Capabilities can be elastically provisioned and released, in some cases automatically, to scale rapidly outward and inward commensurate with demand. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.
Measured Service: Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth and active user accounts). Resource usage can be monitored, controlled and reported providing transparency for both the provider and consumer of the utilized service.
Service Models are as Follows:
Software as a Service (SaaS): The capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from various client devices through either a thin client interface, such as a web browser (e.g., web-based e-mail) or a program interface. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.
Platform as a Service (PaaS): The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages, libraries, services and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems or storage, but has control over the deployed applications and possibly configuration settings for the application-hosting environment.
Infrastructure as a Service (IaaS): The capability provided to the consumer is to provision processing, storage, networks and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage and deployed applications; and possibly limited control of select networking components (e.g., host firewalls).
Deployment Models are as Follows:
Private Cloud: The cloud infrastructure is provisioned for exclusive use by a single organization comprising multiple consumers (e.g., business units). It may be owned, managed and operated by the organization, a third party or some combination of them, and it may exist on or off premises.
Community Cloud: The cloud infrastructure is provisioned for exclusive use by a specific community of consumers from organizations that have shared concerns (e.g., mission, security requirements, policy and compliance considerations). It may be owned, managed and operated by one or more of the organizations in the community, a third party, or some combination of them, and it may exist on or off premises.
Public Cloud: The cloud infrastructure is provisioned for open use by the general public. It may be owned, managed and operated by a business, academic or government organization, or some combination of them. It exists on the premises of the cloud provider.
Hybrid Cloud: The cloud infrastructure is a composition of two or more distinct cloud infrastructures (private, community or public) that remain unique entities, but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load balancing between clouds).
Referring now to the Figures in detail,
Network 103 may be, for example, a local area network, a wide area network, a wireless wide area network, a circuit-switched telephone network, a Global System for Mobile Communications (GSM) network, Wireless Application Protocol (WAP) network, a WiFi network, an IEEE 802.11 standards network, various combinations thereof, etc. Other networks, whose descriptions are omitted here for brevity, may also be used in conjunction with system 100 of
Cloud computing environment 102 is used to deliver computing as a service to client device 101 implementing the model discussed above. An embodiment of cloud computing environment 102 is discussed below in connection with
Referring now to
With reference now to cloud computing node 201A, cloud computing node 201A includes a virtual operating system 302A. Operating system 302A executes on a real or physical computer 303A. Real computer 303A includes one or more processors 304A, a memory 305A (also referred to herein as the host physical memory), one or more disk drives 306A and the like. Other components of real computer 303A are not discussed herein for the sake of brevity.
Virtual operating system 302A further includes user portions 307A-307B (identified as “Guest 1 and Guest 2,” respectively, in
Each guest operating system 308A, 308B may host one or more virtual machine applications 309A-309C (identified as “VM 1,” “VM 2” and “VM 3,” respectively, in
In one embodiment, an agent 310A, referred to herein as the “activation agent,” is run on a virtual machine, such as virtual machine 309A. As discussed further below in connection with
Virtual operating system 302A further includes a common base portion 311A, referred to herein as a hypervisor. Hypervisor 311A may be implemented in microcode running on processor 304A or it may be implemented in software as part of virtual operating system 302A. Hypervisor 311A is configured to manage and enable guests 307A, 307B to run on a single host.
As discussed above, virtual operating system 302A and its components execute on physical or real computer 303A. These software components may be loaded into memory 305A for execution by processor 304A.
As also discussed above, cloud computing environment 102 (
Guests 307A-307D may collectively or individually be referred to as guests 307 or guest 307, respectively. Guest operating systems 308A-308D may collectively or individually be referred to as guest operating systems 308 or guest operating system 308, respectively. Virtual machines 309A-309E may collectively or individually be referred to as virtual machines 309 or virtual machine 309, respectively. Activation agents 310A-310B may collectively or individually be referred to as activation agents 310 or activation agent 310, respectively. Hypervisors 311A-311B may collectively or individually be referred to as hypervisors 311 or hypervisor 311, respectively.
Referring again to
Referring now to
Referring again to
Cloud controller 301 may further include a communications adapter 409 coupled to bus 402. Communications adapter 409 interconnects bus 402 with an outside network (e.g., network 103 of
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” ‘module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the C programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the present invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the function/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the function/acts specified in the flowchart and/or block diagram block or blocks.
As stated in the Background section, an image of the virtual operating system contains many pieces of unique metadata that are often generated on the first boot to ensure randomness and security, such as a RSA key, a Globally Unique IDentifier (GUID), a Secure Sockets Layer (SSL) certificate and a Lightweight Third-Party Authentication (LTPA) key. Currently, the virtual machine generates these metadata at deployment time. Since some of the metadata requires extensive time to generate, the deployment time of the instance of the virtual machine can be lengthy. If, however, the virtual machine can be relieved of generating such metadata, the deployment time could be lessened. As a result, instead of the cloud's limited resources being used on first-boot activities, such as generating these first-boot metadata, such resources could be used for other activities.
The principles of the present invention provide a means for reducing the deployment time of virtual machines by having the cloud controller pre-generate a virtual machine's first-boot metadata (e.g., a RSA key, a Globally Unique IDentifier (GUID), a Secure Sockets Layer (SSL) certificate and a Lightweight Third-Party Authentication (LTPA) key) prior to deployment of the virtual machine instead of having the virtual machine generate such metadata at deployment time as discussed further below in connection with
Referring to
In step 502, cloud controller 301 stores the pre-generated first-boot metadata, such as in hard drive 408 of cloud controller 301.
In step 503, cloud controller 301 deploys the virtual machine 309. Once virtual machine 309 (e.g., virtual machine 309A) has been deployed and activated, in step 504, activation agent 310 (e.g., activation agent 310A) of the deployed virtual machine 309 (e.g., virtual machine 309A) transmits a request for the pre-generated first-boot metadata to cloud controller 301. In one embodiment, such communications occurs using an out-of-band communication, such as using a REST call. In this manner, the pre-generated metadata may be securely transferred from cloud controller 301 to virtual machine 309 as discussed further below. In one embodiment, the communication may include additional data, such as the hostname, the IP address, location information, application data, etc. of virtual machine 309, which is used by cloud controller 301 to modify/augment the stored pre-generated first-boot metadata to make it usable for virtual machine 309. The first-boot metadata stored by cloud controller 301 may be missing information (e.g., hostname, IP address) that needs to be included in the first-boot metadata in order for it to be used by virtual machine 309. Such information may be provided by activation agent 310 in its request to cloud controller 301 for the pre-generated first-boot metadata.
In step 505, cloud controller 301 processes the request and retrieves the requested pre-generated first-boot metadata, such as from disk unit 408. In one embodiment, the retrieved pre-generated metadata is modified/augmented based on the additional data supplied by activation agent 310.
In step 506, cloud controller 301 signs the retrieved pre-generated first-boot metadata with cloud controller's 301 private key to generate a signature thereby allowing virtual machine 309 to validate the authenticity and integrity of the pre-generated first-boot metadata as discussed further below.
In step 507, cloud controller 301 transmits the requested pre-generated first-boot metadata, the signature and a public key (public key that is corresponding to the private key used by cloud controller 301 in step 506) to the requesting activation agent 310 of virtual machine 309. In one embodiment, only a single instance of the generated first-boot metadata is ever stored and used by cloud controller 301. Hence, when cloud controller 301 transmits the requested pre-generated first-boot metadata, there are no stored copies of the transmitted pre-generated first-boot metadata remaining in cloud controller 301 thereby preventing it from being used again by another virtual machine 309 for security purposes.
In step 508, virtual machine 309 determines whether the signature is verified using the received public key. If the signature is verified by the public key, then, in step 509, virtual machine 309 installs the requested pre-generated first-boot metadata. Otherwise, if the signature is not verified by the public key, then, in step 510, virtual machine 309 does not install the requested pre-generated first-boot metadata.
While the foregoing discusses the use of public-key cryptography for authenticating the requesting pre-generated first-boot metadata, other cryptographic systems may be used for authenticating the requesting pre-generated first-boot metadata. Embodiments employing such cryptographic systems fall within the scope of the present invention.
In some implementations, method 500 may include other and/or additional steps that, for clarity, are not depicted. Further, in some implementations, method 500 may be executed in a different order presented and that the order presented in the discussion of
The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
Number | Name | Date | Kind |
---|---|---|---|
6370249 | Van Oorschot | Apr 2002 | B1 |
20060258340 | Eronen | Nov 2006 | A1 |
20080163194 | Dias et al. | Jul 2008 | A1 |
20090006850 | Birger et al. | Jan 2009 | A1 |
20090154709 | Ellison | Jun 2009 | A1 |
20120131579 | Pujolle et al. | May 2012 | A1 |
Entry |
---|
Mell et al., “The NIST Definition of Cloud Computing,” Special Publication 800-145, Sep. 2011. |
Number | Date | Country | |
---|---|---|---|
20140059541 A1 | Feb 2014 | US |