Patent Description:
It is the object of the present invention to reduce the spin-up time of virtual machines.

Briefly stated, the disclosed technology is generally directed to virtual machines. In one example of the technology, a first virtual machine executing on a first virtual machine host is reconfigured without rebooting the first virtual machine. In some examples, the reconfiguring includes controlling the following actions. At least one compute artifact of a plurality of compute artifacts is associated with a first user that is associated with the first virtual machine. At least one compute artifact of the plurality of compute artifacts is modified. A configuration is published to the first virtual machine host.

Other aspects of and applications for the disclosed technology will be appreciated upon reading and understanding the attached figures and description.

Non-limiting and non-exhaustive examples of the present disclosure are described with reference to the following drawings. In the drawings, like reference numerals refer to like parts throughout the various figures unless otherwise specified. These drawings are not necessarily drawn to scale.

For a better understanding of the present disclosure, reference will be made to the following Detailed Description, which is to be read in association with the accompanying drawings, in which:.

The following description provides specific details for a thorough understanding of, and enabling description for, various examples of the technology. One skilled in the art will understand that the technology may be practiced without many of these details. In some instances, well-known structures and functions have not been shown or described in detail to avoid unnecessarily obscuring the description of examples of the technology. It is intended that the terminology used in this disclosure be interpreted in its broadest reasonable manner, even though it is being used in conjunction with a detailed description of certain examples of the technology. Although certain terms may be emphasized below, any terminology intended to be interpreted in any restricted manner will be overtly and specifically defined as such in this Detailed Description section. Throughout the specification and claims, the following terms take at least the meanings explicitly associated herein, unless the context dictates otherwise. The meanings identified below do not necessarily limit the terms, but merely provide illustrative examples for the terms. For example, each of the terms "based on" and "based upon" is not exclusive, and is equivalent to the term "based, at least in part, on", and includes the option of being based on additional factors, some of which may not be described herein. As another example, the term "via" is not exclusive, and is equivalent to the term "via, at least in part", and includes the option of being via additional factors, some of which may not be described herein. The meaning of "in" includes "in" and "on. " The phrase "in one embodiment," or "in one example," as used herein does not necessarily refer to the same embodiment or example, although it may. Use of particular textual numeric designators does not imply the existence of lesser-valued numerical designators. For example, reciting "a widget selected from the group consisting of a third foo and a fourth bar" would not itself imply that there are at least three foo, nor that there are at least four bar, elements. References in the singular are made merely for clarity of reading and include plural references unless plural references are specifically excluded. The term "or" is an inclusive "or" operator unless specifically indicated otherwise. For example, the phrases "A or B" means "A, B, or A and B. " As used herein, the terms "component" and "system" are intended to encompass hardware, software, or various combinations of hardware and software. Accordingly, for example, a system or component may be a process, a process executing on a computing device, the computing device, or a portion thereof.

A VM, including the compute artifacts of a VM, is reconfigured without rebooting the VM in some examples. Such compute artifacts may include, for example, the machine name, account username, account password, time zone, and/or the like. The VM may be a system VM, that is, a VM that provides the functionality to operate an entire operating system. In some examples, a user may wish an existing VM already used to be the VM to be reconfigured. In other examples, a partially configured VM may be reconfigured. For example, partially configured VMs, which are configured in all aspects except for customer specific settings in some examples, may be pooled so that fully configured VMs may be provided more quickly upon request by reconfiguring a partially configured VM than creating a new VM from scratch.

A VM may be reconfigured based on a virtual machine reconfiguration request that includes user-specific settings. Artifacts, including compute artifacts and possibly other artifacts, may be allocated to the user. Artifacts, including compute artifacts and possibly other artifacts, may also be modified and/or created as needed. The configuration can then be communicated to the VM host.

<FIG> is a diagram of environment <NUM> in which aspects of the technology may be practiced. As shown, environment <NUM> includes computing devices <NUM>, as well as network nodes <NUM>, connected via network <NUM>. Even though particular components of environment <NUM> are shown in <FIG>, in other examples, environment <NUM> can also include additional and/or different components. For example, in certain examples, the environment <NUM> can also include network storage devices, maintenance managers, and/or other suitable components (not shown).

As shown in <FIG>, network <NUM> can include one or more network nodes <NUM> that interconnect multiple computing devices <NUM>, and connect computing devices <NUM> to external network <NUM>, e.g., the Internet or an intranet. For example, network nodes <NUM> may include switches, routers, hubs, network controllers, or other network elements. In certain examples, computing devices <NUM> can be organized into racks, action zones, groups, sets, or other suitable divisions. For example, in the illustrated example, computing devices <NUM> are grouped into three host sets identified individually as first, second, and third host sets 112a-112c. In the illustrated example, each of host sets 112a-112c is operatively coupled to a corresponding network node 120a-120c, respectively, which are commonly referred to as "top-of-rack" or "TOR" network nodes. TOR network nodes 120a-120c can then be operatively coupled to additional network nodes <NUM> to form a computer network in a hierarchical, flat, mesh, or other suitable types of topology that allows communication between computing devices <NUM> and external network <NUM>. In other examples, multiple host sets 112a-112c may share a single network node <NUM>. Computing devices <NUM> may be virtually any type of general- or specific-purpose computing device. For example, these computing devices may be user devices such as desktop computers, laptop computers, tablet computers, display devices, cameras, printers, or smartphones. However, in a data center environment, these computing devices may be server devices such as application server computers, virtual computing host computers, or file server computers. Moreover, computing devices <NUM> may be individually configured to provide computing, storage, and/or other suitable computing services.

<FIG> is a diagram illustrating one example of computing device <NUM> in which aspects of the technology may be practiced. Computing device <NUM> may be virtually any type of general- or specific-purpose computing device. For example, computing device <NUM> may be a user device such as a desktop computer, a laptop computer, a tablet computer, a display device, a camera, a printer, or a smartphone. Likewise, computing device <NUM> may also be server device such as an application server computer, a virtual computing host computer, or a file server computer, e.g., computing device <NUM> may be an example of computing device <NUM> or network node <NUM> of <FIG>. Likewise, computer device <NUM> may be an example any of the devices illustrated in <FIG>, as discussed in greater detail below. As illustrated in <FIG>, computing device <NUM> includes processing circuit <NUM>, operating memory <NUM>, memory controller <NUM>, data storage memory <NUM>, input interface <NUM>, output interface <NUM>, and network adapter <NUM>. Each of these aforelisted components of computing device <NUM> includes at least one hardware element.

Computing device <NUM> includes at least one processing circuit <NUM> configured to execute instructions, such as instructions for implementing the herein-described workloads, processes, or technology. Processing circuit <NUM> may include a microprocessor, a microcontroller, a graphics processor, a coprocessor, a field programmable gate array, a programmable logic device, a signal processor, or any other circuit suitable for processing data. The aforementioned instructions, along with other data (e.g., datasets, metadata, operating system instructions, etc.), may be stored in operating memory <NUM> during run-time of computing device <NUM>. Operating memory <NUM> may also include any of a variety of data storage devices/components, such as volatile memories, semi-volatile memories, random access memories, static memories, caches, buffers, or other media used to store run-time information. In one example, operating memory <NUM> does not retain information when computing device <NUM> is powered off. Rather, computing device <NUM> may be configured to transfer instructions from a non-volatile data storage component (e.g., data storage component <NUM>) to operating memory <NUM> as part of a booting or other loading process.

Operating memory <NUM> may include <NUM>th generation double data rate (DDR4) memory, <NUM>rd generation double data rate (DDR3) memory, other dynamic random access memory (DRAM), High Bandwidth Memory (HBM), Hybrid Memory Cube memory, 3D-stacked memory, static random access memory (SRAM), or other memory, and such memory may comprise one or more memory circuits integrated onto a DIMM, SIMM, SODIMM, or other packaging. Such operating memory modules or devices may be organized according to channels, ranks, and banks. For example, operating memory devices may be coupled to processing circuit <NUM> via memory controller <NUM> in channels. One example of computing device <NUM> may include one or two DIMMs per channel, with one or two ranks per channel. Operating memory within a rank may operate with a shared clock, and shared address and command bus. Also, an operating memory device may be organized into several banks where a bank can be thought of as an array addressed by row and column. Based on such an organization of operating memory, physical addresses within the operating memory may be referred to by a tuple of channel, rank, bank, row, and column.

Despite the above-discussion, operating memory <NUM> specifically does not include or encompass communications media, any communications medium, or any signals per se.

Memory controller <NUM> is configured to interface processing circuit <NUM> to operating memory <NUM>. For example, memory controller <NUM> may be configured to interface commands, addresses, and data between operating memory <NUM> and processing circuit <NUM>. Memory controller <NUM> may also be configured to abstract or otherwise manage certain aspects of memory management from or for processing circuit <NUM>. Although memory controller <NUM> is illustrated as single memory controller separate from processing circuit <NUM>, in other examples, multiple memory controllers may be employed, memory controller(s) may be integrated with operating memory <NUM>, or the like. Further, memory controller(s) may be integrated into processing circuit <NUM>. These and other variations are possible.

In computing device <NUM>, data storage memory <NUM>, input interface <NUM>, output interface <NUM>, and network adapter <NUM> are interfaced to processing circuit <NUM> by bus <NUM>. Although, <FIG> illustrates bus <NUM> as a single passive bus, other configurations, such as a collection of buses, a collection of point to point links, an input/output controller, a bridge, other interface circuitry, or any collection thereof may also be suitably employed for interfacing data storage memory <NUM>, input interface <NUM>, output interface <NUM>, or network adapter <NUM> to processing circuit <NUM>.

In computing device <NUM>, data storage memory <NUM> is employed for long-term non-volatile data storage. Data storage memory <NUM> may include any of a variety of non-volatile data storage devices/components, such as non-volatile memories, disks, disk drives, hard drives, solid-state drives, or any other media that can be used for the non-volatile storage of information. However, data storage memory <NUM> specifically does not include or encompass communications media, any communications medium, or any signals per se. In contrast to operating memory <NUM>, data storage memory <NUM> is employed by computing device <NUM> for non-volatile long-term data storage, instead of for run-time data storage.

Also, computing device <NUM> may include or be coupled to any type of processor-readable media such as processor-readable storage media (e.g., operating memory <NUM> and data storage memory <NUM>) and communication media (e.g., communication signals and radio waves). While the term processor-readable storage media includes operating memory <NUM> and data storage memory <NUM>, the term "processor-readable storage medium," throughout the specification and the claims whether used in the singular or the plural, is defined herein so that the term "processor-readable storage medium" specifically excludes and does not encompass communications media, any communications medium, or any signals per se. However, the term "processor-readable storage medium" does encompass processor cache, Random Access Memory (RAM), register memory, and/or the like.

Computing device <NUM> also includes input interface <NUM>, which may be configured to enable computing device <NUM> to receive input from users or from other devices. In addition, computing device <NUM> includes output interface <NUM>, which may be configured to provide output from computing device <NUM>. In one example, output interface <NUM> includes a frame buffer, graphics processor, graphics processor or accelerator, and is configured to render displays for presentation on a separate visual display device (such as a monitor, projector, virtual computing client computer, etc.). In another example, output interface <NUM> includes a visual display device and is configured to render and present displays for viewing.

In the illustrated example, computing device <NUM> is configured to communicate with other computing devices or entities via network adapter <NUM>. Network adapter <NUM> may include a wired network adapter, e.g., an Ethernet adapter, a Token Ring adapter, or a Digital Subscriber Line (DSL) adapter. Network adapter <NUM> may also include a wireless network adapter, for example, a Wi-Fi adapter, a Bluetooth adapter, a ZigBee adapter, a Long-Term Evolution (LTE) adapter, or a <NUM> adapter.

Although computing device <NUM> is illustrated with certain components configured in a particular arrangement, these components and arrangement are merely one example of a computing device in which the technology may be employed. In other examples, data storage memory <NUM>, input interface <NUM>, output interface <NUM>, or network adapter <NUM> may be directly coupled to processing circuit <NUM>, or be coupled to processing circuit <NUM> via an input/output controller, a bridge, or other interface circuitry. Other variations of the technology are possible.

Some examples of computing device <NUM> include at least one storage memory (e.g. data storage memory <NUM>), at least one operating memory (e.g., operating memory <NUM>) and at least one processor (e.g., processing unit <NUM>) that are respectively adapted to store and execute processor-executable code that, in response to execution, enables computing device <NUM> to perform actions, such as, in some examples, the actions of process <NUM> of <FIG>, as discussed in greater detail below.

<FIG> is a block diagram illustrating an example of a system (<NUM>). System <NUM> may include network <NUM>, as well as resource manager <NUM>, VM pool manager <NUM>, compute manager <NUM>, storage manager <NUM>, networking manager <NUM>, and virtual machine host <NUM>, which all may connect to network <NUM>.

Resource manger <NUM> may be configured to communicate with customers, including receiving customer requests, and to coordinate actions based on customer requests. Resource manager <NUM> may also be configured to coordinate other high-level functions associated with VM management. In some examples, compute manager <NUM> manages the compute aspects of VMs, storage manager <NUM> manages the storage aspect of VMs, and networking manager <NUM> manages the networking aspect of VMs. In some examples, compute manager <NUM> also orchestrates management of other resources, including networking resources and storage resources, not just compute resources. In some examples, virtual machine host <NUM> is configured to create and run VMs, responsive to control from, inter alia, compute manager <NUM>.

In some examples, VM pool manager <NUM> is configured to manage a pool of partially provisioned VMs. The partially provisioned VMs may be booted and configured except with respect to customer-specific settings. In some examples, some properties cannot be configured without reboot of a VM or recreating the VM, such as VM size, OS type, storage type, and/or the like. VM pool manager <NUM> may manage keeping a suitable number of each combination of partially configured VMs that may be needed.

Network <NUM> may include one or more computer networks, including wired and/or wireless networks, where each network may be, for example, a wireless network, local area network (LAN), a wide-area network (WAN), and/or a global network such as the Internet. On an interconnected set of LANs, including those based on differing architectures and protocols, a router acts as a link between LANs, enabling messages to be sent from one to another. Also, communication links within LANs typically include twisted wire pair or coaxial cable, while communication links between networks may utilize analog telephone lines, full or fractional dedicated digital lines including T1, T2, T3, and T4, Integrated Services Digital Networks (ISDNs), Digital Subscriber Lines (DSLs), wireless links including satellite links, or other communications links known to those skilled in the art. Furthermore, remote computers and other related electronic devices could be remotely connected to either LANs or WANs via a modem and temporary telephone link. Network <NUM> may include various other networks such as one or more networks using local network protocols such as 6LoWPAN, ZigBee, or the like. In essence, network <NUM> includes any communication technology by which information may travel between resource manager <NUM>, VM pool manager <NUM>, compute manager <NUM>, storage manager <NUM>, and virtual machine host <NUM>. Although each device or service is shown connected as connected to network <NUM>, that does not mean that each device communicates with each other device shown. In some examples, some devices/services shown only communicate with some other devices/services shown via one or more intermediary devices. Also, although network <NUM> is illustrated as one network, in some examples, network <NUM> may instead include multiple networks that may or may not be connected with each other, with some of the devices shown communicating with each other through one network of the multiple networks and other of the devices shown communicating with each other with a different network of the multiple networks.

<FIG> is a block diagram illustrating an example of a system (<NUM>), which may be employed as an example of system <NUM> of <FIG>. System <NUM> may include resource manager <NUM>, VM pool manager <NUM>, compute manager <NUM>, storage manager <NUM>, networking manager <NUM>, and virtual machine host <NUM>. Although only one virtual machine host is shown in <FIG>, some examples of system <NUM> may include a large number of virtual machine hosts.

In various some virtualization environments, a VM (such as a Windows, Linux, or Unix VM) is created from scratch following a customer request for that VM. For example, such creation may include retrieving an image from Platform Image Repository (PIR), copying the image to the customer's account, creating a VM with that image, and booting the VM up. Using a Windows VM as an example as follows, once started, the VM goes through Windows setup (specialized and out-of-box experience (OOBE) passes), which provisions the VM from the generalized image to a specialized image. Despite speed increases in modern computing systems, various amounts of time may be associated with creating a VM. For example, some VMs are associated with end-to-end "spin-up" times in the vicinity of one to five minutes, for example, depending on various factors such as operating system, network speed, resources of the physical hardware, virtualization system load, etc. The present disclosure may be employed, for example, by various providers and tenants of virtualization services to reduce "spin-up time" for VMs following customer requests for VMs. For example, various aspects of the present technology may be employed to facilitate at least partial configuration, provisioning, booting, or other steps typically performed prior to a VM being ready for customer use before a customer has requested the VM. By, for example, performing such steps prior to the request, the duration of time between the customer request and availably of the VM may be reduced in comparison to the typical amount of time associated with "spinning-up" a VM "from scratch" following a request.

Examples of the disclosure may also be used to reconfigure a virtual machine already used by a customer, including at least reconfiguring compute aspects of the virtual machine.

Some examples of system <NUM> may operate in a hierarchy of multiple levels, with, for example, individual virtual machine hosts on the node level, in which there are clusters of virtual machines hosts, and regional data centers each consisting of multiple clusters. In other examples, other suitable arrangements may be employed. In some examples, one or more of compute manager <NUM>, storage manager <NUM>, and networking manager <NUM> each encompass devices operating at more than one level of the hierarchy.

In some examples, VM pool manager <NUM> is configured to manage a pool of partially provisioned VMs. VMs may be booted and configured except with respect to customer-specific settings. In some examples, some properties cannot be configured without reboot of a VM or recreating the VM, such as VM size, OS type, storage type (e.g., premium storage or standard storage), type of internet routing (e.g., IPv4 or IPv6), processor resources, memory resources, and/or the like. VM pool manager <NUM> may manage keeping a suitable number of each combination of partially configured VMs that may be needed.

In some examples, each such type is a virtual machine combination type based on a combination of each parameter that is a property that cannot be configured without reboot but that is selectable by customer as an option. VM pool manager <NUM> may determine how many partially provisioned VMs of each type are needed, for example by identifying current needs for partially configured VMs, and then communicate to compute manager <NUM> in order to create each needed partially provisioned VM. When compute manager <NUM> receives a request from VM pool manager <NUM> to create a partially provisioned VM, in some examples, compute manager <NUM> then manages creation of the requested partially provisioned VM.

Partially provisioned VMs that are configured except with regard to certain user-specific settings may each be generated as follows. Without customer data, generic virtual machine artifacts are created. The generic artifacts may include generic compute artifacts, and may also include generic storage artifacts and generic networking artifacts. The generic compute artifacts may include, for example, a placeholder machine name, a placeholder account username, a placeholder account password, and/or the like. The generic networking artifacts may include, for example, a placeholder virtual network, and a placeholder customer IP address. A VM is created/composed using the generic artifacts, using the particular combination of properties that are not reconfigured (e.g., VM size, OS type, storage type, processor resources, memory resources, etc.), and the VM is booted.

In some examples, pool manager <NUM> manages the VM pool. Pool manager <NUM> may be configured to determine which VMs should be created for the pool. Pool manager <NUM> may communicate with compute manager <NUM> in order for the VMs to be created, with the creation of the VMs controlled by compute manager <NUM>. Compute manager <NUM> may manage the compute aspects, as well as the orchestration of the networking resources and the storage resources.

In some examples, compute manager <NUM> also communicates the networking resources needed to networking manager <NUM>, which manages the networking resources, and communicates the storage resources needed to storage manager <NUM>, which manages the storage resources. In some examples, networking manager <NUM> is configured to, upon request from compute manager <NUM>, provide generic networking artifacts for the partially provisioned VM to be created.

In some examples, compute manager <NUM> also communicates storage resources needed to storage manager <NUM>. In some examples, during the partial provisioning, only the OS disc storage is assigned during partial provisioning. In some examples, if a customer wishes additional storage, that is handled during the full configuration. In some examples, details of storage for the OS is a property that is not reconfigured, and so storage details options are included in the combination of different types of partially provisioned VMs that are created and managed by pool manager <NUM>.

In some examples, actual creation and booting of the VM occurs in VM host <NUM>. In some examples, during the boot process, VM host <NUM> causes the VM enters a state in which the VM actively seeks new configuration, so that the VM can be reconfigured with customer-specific settings once a configuration with the customer-specific settings is published. Also, in some examples, VM host <NUM> causes the VM to be created such that the VM includes an agent that is capable of causing reconfiguration the VM according to the user-specific settings in response to publication of a configuration with the customer-specific settings.

In some examples, VM host <NUM> executes a service called Instance Metadata Service that publishes a full configuration when available; in these examples, the agent may actively poll the Instance Metadata Service for the full configuration. In some examples, the manner in which the VM is partially configured and then enters into a state seeking full configuration varies depending on the OS type of the VM.

In some examples in which the VM has a Linux OS, the VM is booted, VM host <NUM> passes the VM a tag that indicates that the configuration is partial and not the final configuration. In some examples, when the VM is booted, the VM is configured with some but not all of the configurations-some configurations, including certain user-specific settings, are not done. However, in some examples, even though some user-specific settings are not done, or are done but given generic placeholder/default settings rather than user-specific settings, the VM sends a success message to VM host <NUM> indicating that the configuration is done. In some examples, because the configuration is not complete, in essence the VM is faking a success message so that the VM may remain in configuration mode, and configuration is completed when a full configuration with user-specified settings is available. In some examples, the success message is received by virtual machine host <NUM>, and is sent from virtual machine host <NUM> to compute manager <NUM>.

In response to the tag indicating that the configuration is only partial and not the final configuration, in some examples, the VM enters a state in which the VM polls VM host <NUM> for the new configuration. In some examples, the VM reads the tag to determine whether the configuration is partial or final. In some examples, a configuration with the tag is treated as a partial and not final configuration, and a configuration lacking the tag is treated as a final configuration. In some examples, the VM remains in this "partially booted" state, waiting for the complete configuration, until VM host <NUM> publishes a full configuration for the VM, at which point the VM's polling indicates that the full configuration is available.

In some examples in which the VM has a Windows OS, the VM is booted with a minimal configuration. In some examples, Windows itself cannot provision again after the minimal configuration performed in the first boot. Instead, in some examples, after setup finishes, VM host <NUM> causes a code extension to be installed and executed in the VM which causes the VM to keep running, and to enter a state in which the VM polls VM host <NUM> for the new configuration. In some examples, the VM remains in the polling state, waiting for the complete configuration, until VM host <NUM> publishes a full configuration for the VM, at which point the VM's polling indicates that the full configuration is available. In some examples, the code extension is capable of performing the reconfiguration to the full configuration.

In some examples, regardless of the OS type, after partially provisioning, in some examples, the VM is in a state in which it is polling for a full configuration to be used by which to reconfigure the VM. At this point, in some examples, a success message is sent to from the VM to VM host <NUM>, from VM host <NUM> to compute manager <NUM>, and compute manager <NUM> sends the success message to pool manager <NUM>. At this point, in some examples, the VM is in the pool of partially provisioned VMs managed by VM pool manager <NUM>.

Resource manager <NUM> may receive requests for VMs to customers, and may manage such requests. In some examples, customers may communicate with system <NUM> via a portal, and the portal may communicate requests from customers to resource manager <NUM>. In response to customer request(s) for VM(s), resource manager <NUM> may send a request to compute manager <NUM> to deploys VMs. In response to the request from resource manager <NUM>, compute manager <NUM> may communicate with VM pool manager <NUM> to determine from VM pool manager <NUM> whether or not there are existing partially provisioned VMs pooled by VM pool manger <NUM> that meet the required criteria. In some examples, if not, VMs will be created from scratch to meet the request.

If, however, there are available partially provisioned VMs in the VM pool managed by VM pool manager <NUM>, then, in some examples, each partially provisioned VM is reconfigured to meet user-specific settings required based on the VMs requested, as follows for each VM in some examples. Compute manager <NUM> may send a request to storage manager <NUM> to cause corresponding storage artifacts to move their association from the platform to the particular customer. Such storage artifacts may include, for example, the disk on which the OS will be copied to and in which the OS will run, and any additional storage requested by the customer. By moving the association of the storage artifacts to the customer, in some examples, the customer has access to and can manage the storage artifacts, including, for example, the disk on which the OS will run.

Compute manager <NUM> may also request that certain storage artifacts be modified and/or reconfigured and/or created based on the user-specific settings. For example, the customer may have requested additional storage, which may be created and then associated with the particular customer. Compute manager <NUM> may also move corresponding compute artifacts, associated with the user-specific compute settings, to the particular customer. In this way, in some examples, the customer has access to and can manage the compute artifacts, including the VM itself. Compute manager <NUM> may also cause certain compute artifacts to be modified and/or reconfigured based on the user-specific settings.

An example of modifying and/or reconfiguring a compute artifact based on user-specific settings is changing the machine name based on the user-specific compute settings. A default/placeholder machine name may have been given to the partially provisioned VM during partial configuration in order to complete the initial, partial configuration. However, as part of the full configuration of the VM based on the user-specific settings, the user may have requested a VM with a particular machine name. Compute manager <NUM> may modify the machine name based on the user-specific settings.

The changes in association of compute, network, and storage artifacts may be accomplished with changes to the internal data structures--metadata changes to move the artifacts from the platform tenant to the customer tenant. A customer may have a particular subscription associated with the customer and the customer's subscription, where the customer subscription is used as a logical unit by which all of the virtual machines are included for the customer. Artifacts may be moved from the platform tenant to the customer subscription tenant by updating the internal data structures including updating the corresponding metadata to reflect the re-association from the platform tenant to the customer's account.

Compute manager <NUM> may also send a request to networking manager <NUM> to cause corresponding networking artifacts to move their association from the platform to the particular customer, as well as for networking artifacts to be modified and/or reconfigured and/or created. Networking manager <NUM> may send a success message to compute manager <NUM> when the networking aspects are complete.

In some examples, after the modifications, reconfigurations, creations, and/or re-associations to be performed outside the VM host <NUM> are complete, compute manager <NUM> communicates the reconfiguration information to VM host <NUM>.

The compute agent in VH host <NUM> may then generate a file with the new configuration, and then publish the new configuration via the Instance Metadata Service in VM host <NUM>, so that the new configuration is available to be polled by the partially configured VM, which is in a state of polling the Instance Metadata Service, for the new configuration, and the polling will be successful once the new configuration is published by the Instance Metadata Service.

The agent on the VM may then accept the user-specific settings associated with the reconfiguration requests, including user-specific networking settings, and then apply those user-specific settings, so that compute and possibly other aspects of the VM are reconfigured accordingly. In this way, in some examples, the partially provisioned VM becomes reconfigured based on the user-specific settings.

The manner in which the reconfiguration of the VM happens may depend in the OS type of the VM in some examples.

For instance, in some examples, if the OS type of the VM is Linux, the reconfiguration may be completed at this time. In some examples, the VM was left in a "partially booted" state, waiting for the complete configuration, and the configuration is allowed to finish now that the full configuration has been received, using the newly received full configuration.

In some examples, if the OS type is Windows, Windows cannot perform the configuration again, or remain in a partially booted state. Instead, in some examples, the same code extension that caused the VM to enter a state in which it polls VM host <NUM> for the new configuration may cause the VM to be reconfigured based on the full configuration, by in essence using the same configuration process normally used by Windows, except that the configuration is performed by the code extension rather than by Windows.

After the reconfiguration is successfully completed, the VM may send a success message to VM host <NUM> indicating that the reconfiguration is successful. VM host <NUM> may then communicate the success message to compute manager <NUM>. Compute manager <NUM> may then communicate the success message to resource manager <NUM>, which may in turn communicate the success message to the customer portal, which may in turn communicate the success to the customer. In some examples, use of the re-configured VM may then be tracked, and success or failure of the use of the re-configured VM may be reported, and appropriate actions may be taken based on the success or failure of the use of the re-configured VM.

An example of reconfiguring a partially provisioned VM has been described. A fully provisioned VM may also be reconfigured based on a customer request, and this reconfiguration, including changing compute aspects of the VM, may be performed without rebooting the VM. In some examples, the process is essentially the same as reconfiguring a partially provisioned VM, except that artifacts already associated with the customer do not need to have their association moved to the customer.

Resource manager <NUM> may receive a request from a customer to reconfigure a fully provisioned VM. In response to the customer request to reconfigure the VM, resource manager <NUM> may send a request to compute manager <NUM> to reconfigure the VM.

In response to the customer request from resource manager <NUM> to reconfigure the VM, compute manager <NUM> may, if relevant, send a request to storage manager <NUM> to cause corresponding storage artifacts to be modified and/or reconfigured and/or created based on the user-specific settings for which the VM is to be reconfigured, and send a request to networking manager <NUM> to cause corresponding networking artifacts to be modified and/or reconfigured and/or created based on the user-specific settings for which the VM is to be reconfigured. This may include, inter alia, networking manager <NUM> creating a new virtual network, reusing the MAC address and the physical IP address of the VN prior to reconfiguration, remapping the physical IP address of the VM to the new customer-provided customer IP address, reprogramming the virtual load balances, configuring customer-requested rules for the NIC and the MAC, applying the new virtual network to the VM, and sending a success message to compute manager <NUM>.

In some examples, compute manager <NUM> also causes certain corresponding compute artifacts to be modified and/or reconfigured based on the user-specific settings. An example of modifying and/or reconfiguring a compute artifact based on user-specific settings is changing the machine name based on the user-specific compute settings. In some examples, the fully provisioned VM already has a machine name. However, part of the reconfiguration request by the customer may include a request that the machine name of the VM be changed, and the new machine name requested by the customer may be part of the user-specified settings in the VM reconfiguration request. Compute manager <NUM> may modify the machine name based on the user-specific settings.

Compute manager <NUM> may then communicate the new configuration to VM host <NUM>. VM host <NUM> may then provide the new configuration to the VM. The agent on the VM may then accept the user-specific settings associated with the reconfiguration request, including user-specific networking settings, and apply those user-specific settings, so that the compute aspects of the VM and possibly other aspects of the VM can be reconfigured accordingly. In this way, in some examples, the VM becomes reconfigured based on the user-specific settings. After the reconfiguration is successfully completed, the VM may send a success message to VM host <NUM> indicating that the reconfiguration is successful. VM host <NUM> may then communicate the success message to compute manager <NUM>. Compute manager <NUM> may then communicate the success message to resource manager <NUM>, which may in turn communicate the success message to the customer portal, which in turn may communicate the success to the customer.

For clarity, the processes described herein are described in terms of operations performed in particular sequences by particular devices or components of a system. However, it is noted that other processes are not limited to the stated sequences, devices, or components. For example, certain acts may be performed in different sequences, in parallel, omitted, or may be supplemented by additional acts or features, whether or not such sequences, parallelisms, acts, or features are described herein. Likewise, any of the technology described in this disclosure may be incorporated into the described processes or other processes, whether or not that technology is specifically described in conjunction with a process. The disclosed processes may also be performed on or by other devices, components, or systems, whether or not such devices, components, or systems are described herein. These processes may also be embodied in a variety of ways. For example, they may be embodied on an article of manufacture, e.g., as processor-readable instructions stored in a processor-readable storage medium or be performed as a processor-implemented process. As an alternate example, these processes may be encoded as processor-executable instructions and transmitted via a communications medium.

<FIG> is a flow diagram illustrating an example process (<NUM>) that may be performed, e.g., by compute manager <NUM> of <FIG> or compute manager <NUM> of <FIG>. In some examples, a first virtual machine executing on a first virtual machine host is reconfigured without rebooting the first virtual machine, which is accomplished, in some examples, with steps <NUM>-<NUM>.

In the illustrated example, step <NUM> occurs first. At step <NUM>, in some examples, at least one compute artifact of a plurality of compute artifacts is associated with a first user that is associated with the first virtual machine. As shown, step <NUM> occurs next in some examples. At step <NUM>, in some examples, at least one compute artifact of the plurality of compute artifacts is modified.

As shown, step <NUM> occurs next in some examples. At step <NUM>, in some examples, a configuration is published to the first virtual machine host. The process may then proceed to a return block, where other processing is resumed.

Claim 1:
An apparatus, comprising:
a device including at least one memory adapted to store run-time data for the device, and at least one processor that is adapted to execute processor-executable code that, in response to execution, enables the device to perform actions, including:
receiving a request for a virtual machine, wherein the request includes user-specific configurable parameters and non-configurable parameters;
determining that a first virtual machine has non-configurable parameters matching the non-configurable parameters of the request;
in response to determining that the non-configurable parameters of the first virtual machine match the non-configurable parameters of the request, reconfiguring the first virtual machine executing on a first virtual machine host, including controlling acts, including:
associating (<NUM>) at least one compute artifact of a plurality of compute artifacts with a first user that is associated with the first virtual machine;
modifying (<NUM>) at least one compute artifact of the plurality of compute artifacts, wherein modifying the at least one compute artifact is based, at least in part, on the user-specific configurable parameters in the request; and
publishing (<NUM>) the configuration to the first virtual machine host.