Dynamic code deployment and versioning

• US 9,715,402 B2
• Filed: 09/30/2014
• Issued: 07/25/2017
• Est. Priority Date: 09/30/2014
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Wagner, Timothy Allen, Reque, Sean Philip, Manwaring, Derek Steven, Zhao, Xin, Thomas, Dylan Chandler
• Primary Examiner(s): BROPHY, MATTHEW J
• Application Number:
  US14/502,620
• Publication Number:
  US 20160092250A1
• Time in Patent Office: 1,029 Days
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 2009/45575 Starting, stopping, suspending or resuming virtual machine instances
• CPC Class Codes: G06F 9/44536 Selecting among different versions
• CPC Class Codes: G06F 9/44552 Conflict resolution, i.e. enabling coexistence of conflicting executables
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

A system for providing dynamic code deployment and versioning is provided. The system may be configured to receive a first request to execute a newer program code on a virtual compute system, determine, based on the first request, that the newer program code is a newer version of an older program code loaded onto an existing container on a virtual machine instance on the virtual compute system, initiate a download of the newer program code onto a second container on the same virtual machine instance, and causing the first request to be processed with the older program code in the existing container.

Claims

1. A system for providing low-latency computational capacity from a virtual compute fleet, the system comprising:

an electronic data store configured to store at least a program code of a user; and

a virtual compute system comprising one or more hardware computing devices executing specific computer-executable instructions, said virtual compute system in communication with the data store, and configured to at least;

maintain a plurality of virtual machine instances on one or more physical computing devices, wherein the plurality of virtual machine instances comprise;

a warming pool comprising virtual machine instances having one or more software components loaded thereon and waiting to be assigned to a user; and

an active pool comprising virtual machine instances assigned to one or more users;

receive a first code execution request to execute a program code on the virtual compute system, the first code execution request including version information identifying a first version of the program code;

determine, based on the version information, that the program code was updated, prior to the receipt of the first code execution request by the virtual compute system, from a second version to the first version;

determine whether the second version of the program code is loaded onto an existing container created on a particular instance of the virtual machine instances in the active pool;

initiate a download of the first version of the program code onto at least one of the data store, a code cache of the particular instance, or the existing container; and

in response to determining that the second version of the program code is loaded onto an existing container created on the particular instance, determine that the download of the first version of the program code is expected to take longer than a threshold amount of time; and

based on the determination that the first version of the program code is expected to take longer than the threshold amount of time, cause the first code execution request to be processed with the second version of the program code that is in the existing container.

2. The system of claim 1, wherein the virtual compute system is further configured to:

receive a second code execution request to execute the first version of the program code on the virtual compute system; and

cause the second code execution request to be processed with the first version of the program code loaded onto another container created on the particular instance, while the existing container is executing the second version of the program code.

3. The system of claim 1, wherein the virtual compute system is further configured to:

associate the data store of the virtual compute system with multiple virtual machine instances in the active pool, each of said multiple virtual machine instances having access to data stored on the data store; and

cause one or more program codes that are loaded onto any one of said multiple virtual machine instances to be loaded onto the data store.

4. A system, comprising:

a virtual compute system comprising one or more hardware computing devices executing specific computer-executable instructions and configured to at least;

receive a first request to execute a program code on the virtual compute system, the first request including version information identifying a first version of the program code;

determine, based on the version information, that the first version is different from a second version of the program code loaded onto a first container created on a first virtual machine instance on the virtual compute system;

initiate a download of the first version of the program code onto at least one of a second container created on the first virtual machine instance, an internal data store of the virtual compute system, and a code cache of the first virtual machine instance;

determine that the download of the first version of the program code is expected to take longer than a threshold amount of time; and

based on the determination that the first version of the program code is expected to take longer than the threshold amount of time, cause the first request to be processed with the second version of the program code loaded onto the first container.

5. The system of claim 4, wherein the virtual compute system is further configured to:

determine that the program code has been updated; and

cause a latest version of the program code to be downloaded onto the virtual compute system before any request associated with the latest version of the program code is received.

6. The system of claim 4, wherein the virtual compute system is further configured to:

receive a second request associated with the first version of the program code; and

cause the second request to be processed with the first version of the program code in a new container created on the first virtual machine instance while the first container is executing the second version of the program code.

7. The system of claim 4, wherein the first request includes an indication that phasing in the first version of the program code is not urgent, and wherein the virtual compute system is further configured to continue processing additional requests associated with the first version of the program code using the second version of the program code while the first version of the program code is being downloaded.

8. The system of claim 4, wherein the first request includes an indication that phasing in the first version of the program code is urgent, and wherein the virtual compute system is further configured to prevent any subsequent requests associated with the first version of the program code from being processed with the second version of the program code.

9. The system of claim 4, wherein the virtual compute system comprises an active pool of virtual machine instances configured to execute user code in one or more containers created thereon, and wherein the virtual compute system is further configured to:

associate the internal data store of the virtual compute system with multiple virtual machine instances in the active pool, each of said multiple virtual machine instances having access to data stored on the internal data store; and

cause one or more program codes that are loaded onto any one of said multiple virtual machine instances to be loaded onto the internal data store.

10. The system of claim 9, wherein the internal data store is configured to, after the first virtual machine instance is terminated, terminate an association between the first virtual machine instance and any data previously associated with the first virtual machine instance on the internal data store while retaining said any data on the internal data store.

11. A computer-implemented method comprising:

as implemented by one or more computing devices configured with specific executable instructions,

receiving a first request to execute a program code on a virtual compute system, the first request including version information identifying a first version of the program code;

determining, based on the version information, that the first version is different from a second version of the program code loaded onto a first container created on a first virtual machine instance on the virtual compute system;

initiating a download of the first version of the program code onto at least one of a second container created on the first virtual machine instance, an internal data store of the virtual compute system, or a code cache of the first virtual machine instance;

determining that the download of the first version of the program code is expected to take longer than a threshold amount of time; and

based on the determination that the first version of the program code is expected to take longer than the threshold amount of time, causing the first request to be processed with the second version of the program code loaded onto the first container.

12. The computer-implemented method of claim 11, further comprising:

determining that the program code has been updated; and

causing a latest version of the program code to be downloaded onto the virtual compute system before any request associated with the latest version of the program code is received.

13. The computer-implemented method of claim 11, further comprising:

receiving a second request to execute the first version of the program code on the virtual compute system; and

causing the second request to be processed with the first version of the program code loaded onto another container created on the first virtual machine instance while the first container is executing the second version of the program code.

14. The computer-implemented method of claim 11, wherein the first request includes an indication that phasing in the first version of the program code is urgent, and wherein the method further comprises preventing any subsequent requests associated with the first version of the program code from being processed with the second version of the program code.

15. The computer-implemented method of claim 11, wherein the virtual compute system comprises an active pool of virtual machine instances configured to execute user code in one or more containers created thereon, and wherein the method further comprises:

associating the internal data store of the virtual compute system with multiple virtual machine instances in the active pool, each of said multiple virtual machine instances having access to data stored on the internal data store; and

causing one or more program codes that are loaded onto any one of said multiple virtual machine instances to be loaded onto the internal data store.

16. Non-transitory physical computer storage storing computer executable instructions that, when executed by one or more computing devices, configure the one or more computing devices to:

receive a first request to execute a program code on a virtual compute system, the first request including version information identifying a first version of the program code;

determine, based on the version information, that the first version is different from a second version of the program code loaded onto a first container created on a first virtual machine instance on the virtual compute system;

initiate a download of the first version of the program code onto at least one of a second container created on the first virtual machine instance, an internal data store of the virtual compute system, or a code cache of the first virtual machine instance;

determine that the download of the first version of the program code is expected to take longer than a threshold amount of time; and

based on the determination that the first version of the program code is expected to take longer than the threshold amount of time, cause the first request to be processed with the second version of the program code loaded onto the first container.

17. The non-transitory physical computer storage of claim 16, wherein the instructions further configure the one or more computing devices to:

determine that the program code has been updated; and

cause a latest version of the program code to be downloaded onto the virtual compute system before any request associated with the latest version of the program code is received.

18. The non-transitory physical computer storage of claim 16, wherein the instructions further configure the one or more computing devices to:

receive a second request to execute the first version of the program code on the virtual compute system; and

cause the second request to be processed with the first version of the program code loaded onto another container created on the first virtual machine instance while the first container is executing the second version of the program code.

19. The non-transitory physical computer storage of claim 16, wherein the first request includes an indication that phasing in the first version of the program code is urgent, and wherein the instructions further configure the one or more computing devices to prevent any subsequent requests associated with the first version of the program code from being processed with the second version of the program code.

20. The non-transitory physical computer storage of claim 16, wherein the virtual compute system comprises an active pool of virtual machine instances configured to execute user code in one or more containers created thereon, and wherein the instructions further configure the one or more computing devices to:

associate the internal data store of the virtual compute system with multiple virtual machine instances in the active pool, each of said multiple virtual machine instances having access to data stored on the internal data store; and

cause one or more program codes that are loaded onto any one of said multiple virtual machine instances to be loaded onto the internal data store.