Tracing using configurable reflection chaining
US-2024411664-A1 · Dec 12, 2024 · US
US9766912B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-9766912-B1 |
| Application number | US-201213686683-A |
| Country | US |
| Kind code | B1 |
| Filing date | Nov 27, 2012 |
| Priority date | Nov 27, 2012 |
| Publication date | Sep 19, 2017 |
| Grant date | Sep 19, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Embodiments are disclosed for launching a virtual machine and then configuring the virtual machine after launch. Metadata configuration information can be stored in conjunction with virtual machine image configuration data. The virtual machine image configuration data can be used to launch a virtual machine. The metadata configuration information can then be used to further configure the virtual machine after launch. Both the metadata configuration information and the virtual machine image configuration data can be stored in the same virtual machine registration record.
Opening claim text (preview).
What is claimed is: 1. A method of supplying configuration information to a virtual machine, comprising: storing metadata configuration information in a same registration record with a virtual machine image configuration in a service center, so that both the virtual machine image configuration and the metadata configuration information are identified by a single Application Programming Interface (API) request with a single identifier to a virtual machine image, wherein the virtual machine image configuration identifies hardware upon which the virtual machine is launched; changing the metadata configuration information to provide a configuration update to the virtual machine by a third-party vendor; receiving an API request including the single identifier to launch the virtual machine; in response to the request, launching the virtual machine using a virtual machine image, which includes software for booting the virtual machine, in conjunction with the virtual machine image configuration so that a first part of the registration record is used to launch the virtual machine; and after launch, further supplying the stored metadata configuration information to the virtual machine, which is free-form data or executable binaries that identify software to be loaded into the virtual machine, so that a second part of the registration record is used to configure a program running in the virtual machine and supplying configuration information to the virtual machine using user-defined metadata, the metadata configuration information being a first metadata configuration file and the user-defined metadata being a second metadata configuration file different than the first metadata configuration file, both the first and second metadata configuration files being used to configure the virtual machine after launch so that the virtual machine can perform self-customization. 2. The method of claim 1 , wherein a hypervisor uses the virtual machine image configuration to launch the virtual machine and the virtual machine uses a metadata service to further configure itself using the stored metadata configuration information. 3. The method of claim 1 , wherein the virtual machine image identifies at least an operating system to be used in the virtual machine. 4. A method of supplying configuration information to a virtual machine, comprising: storing, in a service center, metadata configuration information in association with a virtual machine image configuration by storing both the metadata configuration information and the virtual machine image configuration in a same registration record, wherein both the virtual machine image configuration and the metadata configuration information are identified by a single Application Programming Interface (API) request, wherein the virtual machine image configuration is associated with a virtual machine image and identifies virtual hardware used as a platform for the virtual machine image, the metadata configuration information including free-form data or executable binaries that identify at least one software package to be loaded, wherein both the virtual machine image configuration and the metadata configuration information are used in association with launching a virtual machine; launching the virtual machine using the virtual machine image configuration, wherein the launching of the virtual machine is upon the virtual hardware identified by the virtual machine image configuration and the launching is performed by a hypervisor executing on a server computer upon which the virtual machine is launched, and wherein the virtual machine image configuration is a first part of a configuration of the virtual machine; and after the launching of the virtual machine, supplying the metadata configuration information to configure a program running within the virtual machine, the metadata configuration information allowing the program running within the virtual machine to be configured by retrieving the at least one software package identified by the free-form data or the executable binaries, wherein the metadata configuration information is a second part of the configuration of the virtual machine and is retrieved through a metadata service. 5. The method of claim 4 , wherein the metadata configuration information is provided by a third-party. 6. The method of claim 4 , further including modifying the virtual machine image and changing virtual machine image configuration to point to the updated virtual machine image. 7. The method of claim 4 , wherein the virtual machine image configuration is a first virtual machine image configuration and further including associating the metadata configuration information with a second virtual machine image configuration, different than the first virtual machine image configuration. 8. The method of claim 4 , wherein the virtual machine image configuration identifies hardware upon which the virtual machine is run. 9. The method of claim 4 , wherein a hypervisor uses the virtual machine image configuration to launch the virtual machine. 10. One or more computer-readable storage media having instructions stored thereon for executing a method, the method comprising: receiving a request to launch a virtual machine; determining a virtual machine image, a virtual machine image configuration, and metadata configuration information, which are together associated with launching of the virtual machine, wherein the virtual machine image configuration identifies the virtual hardware associated with the launching of the virtual machine, wherein the virtual machine image includes software used to boot the virtual machine, and wherein the metadata configuration information is stored in a same registration record with the virtual machine image configuration, so that both the virtual machine image configuration and the metadata configuration information are identified by a single Application Programming Interface request; launching the virtual machine using the virtual machine image and the virtual machine image configuration; and as part of the launching process, supplying the metadata configuration information to the launched virtual machine so that the virtual machine can use the metadata configuration information to customize itself after launching, the metadata configuration information identifying software packages to be loaded into the virtual machine and the virtual machine interpreting or executing the metadata configuration information to obtain the software packages to load so that the virtual machine customizes itself after launching. 11. The one or more computer-readable storage of claim 10 , wherein the virtual machine image configuration and the metadata configuration information are stored in a same registration record. 12. The one or more computer-readable storage of claim 10 , further including launching, using a hypervisor, the virtual machine using the virtual machine image and configured according to the virtual machine image configuration. 13. The one or more computer-readable storage of claim 10 , wherein the metadata configuration information is received by the virtual machine through a metadata service. 14. The one or more computer-readable storage of claim 10 , further including self-configuring the virtual machine through receipt of user-defined metadata included in the request. 15. The one or more computer-readable storage of claim 10 , further including updating the virtual machine image and changing the virtual machine image configuration to point to the updated version of the virtual machine image. 16. The one or more computer-readable storage of
Hypervisor-specific management and integration aspects · CPC title
Starting, stopping, suspending or resuming virtual machine instances · CPC title
Creating, deleting, cloning virtual machine instances · CPC title
Memory management, e.g. access or allocation · CPC title
Program initiating; Program switching, e.g. by interrupt · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.