Matching and enforcing deployment pipeline configurations with live pipeline templates

• US 10,334,058 B2
• Filed: 12/21/2015
• Issued: 06/25/2019
• Est. Priority Date: 12/21/2015
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Frank, Martin Robert, Mosher, Ian Aird, Jodoin, Felix Walter Blue, Mansour, Mark Sidney James, Gu, Sixiang
• Primary Examiner(s): Dalencourt, Yves
• Assistant Examiner(s): Islam, Sm Z
• Application Number:
  US14/977,197
• Publication Number:
  US 20170180266A1
• Time in Patent Office: 1,282 Days
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

Techniques are presented for managing a deployment pipeline using an inheritable and extensible source code template—generally referred to as a live pipeline template (LPT). As described, live pipeline templates may be used to manage deployment pipelines which, in turn, are used to launch, maintain, and update the services and systems used to host and provide computing services.

Claims

1. A non-transitory computer-readable medium storing instructions, which, when executed on a processor, perform an operation to bring a configuration state of a deployment pipeline under control of a live pipeline template, the operation comprising:

generating a first application definition by invoking a plurality of analysis drivers, wherein each of the plurality of analysis drivers inspects a configuration of a respective computing service included in a first deployment pipeline deployed in at least a first cloud computing region, wherein the first application definition reflects a current configuration state of the first deployment pipeline;

generating one or more second application definitions, wherein each second application definition is generated from source code defining a live pipeline template and wherein each second application definition reflects a potential configuration state for a deployment pipeline;

comparing the current configuration state reflected in the first application definition with the potential configuration reflected in the one or more second application definitions;

determined, based on at least the comparison, that one of the second application definitions reflects a potential deployment configuration for a deployment pipeline that is compatible with the first deployment pipeline;

reconfiguring the first deployment pipeline to reflect the potential deployment configuration as specified by the determined second application definition; and

building and deploying one or more applications in the first cloud computing region, using the reconfigured first deployment pipeline.

2. The non-transitory computer-readable medium of claim 1, wherein the source code defining of at least a first one of the live pipeline templates includes one or more base pipeline templates.

4. The non-transitory computer-readable medium of claim 1, wherein the deployment pipeline is a continuous deployment pipeline used to deploy changes to the one or more applications in a production computing service hosted in the first cloud computing region.

5. The non-transitory computer-readable medium of claim 1, wherein the operation further comprises:

receiving source code specifying a set of instance specific parameters used to specialize the live pipeline template corresponding to the determined application definition.

6. The non-transitory computer-readable medium of claim 5, wherein the operation further comprises:

launching an instance of the deployment pipeline in at least a second cloud computing region by invoking, for each of a plurality of computing services service referenced in the determined second application definition, a respective pipeline synthesis driver to configure a corresponding one of the computing services in the second cloud computing region.

7. The non-transitory computer-readable medium of claim 1, wherein the first application definition and the second application definitions are each formatted according to a common interchange format.

3. The non-transitory computer-readable medium of 1, wherein the one or more base pipeline templates include a first base pipeline template specifying a set of configuration parameters for one or more deployment stages of the deployment pipeline.

8. A system, comprising:

a processor; and

a memory storing one or more applications, which when executed on the processor, perform an operation for monitoring a configuration state of a deployment pipeline, the operation comprising;

identifying a change made to the configuration of at least a first computing service used, at least in part, to provide the deployment pipeline,

generating an application definition from source code of an instance of a live pipeline template (LPT) associated with the deployment pipeline, wherein the application definition provides a fully-specified configuration for a plurality of computing services included in the deployment pipeline, including the first computing service,

comparing the identified change to the configuration of the first computing service with a configuration specified for the first computing service in the application definition, and

generating a report describing differences between the changed configuration of the first computing service and the configuration state for the first computing service specified in the application definition.

9. The system of claim 8, wherein the report identifies measure of risk to either the deployment pipeline or production computing service updated using the deployment pipeline resulting from the identified change.

10. The system of claim 9, wherein the report identifies a modification to the changed configuration of the deployment pipeline to reduce the measure of risk.

11. The system of claim 8, wherein the instance of the LPT specializes one or more base pipeline templates with instance specific parameters for the deployment pipeline and wherein the application definition is generated from the LPT instance.

12. The system of claim 8, wherein a second one of the base pipeline templates extends at least a first one of the base pipeline templates.

13. The system of claim 12, wherein the first base pipeline template specifies a set of configuration parameters for one or more deployment stages of the deployment pipeline and wherein the second base pipeline template specifies requirements for the deployment pipeline which are associated with a production service type.

14. The system of claim 8, wherein the deployment pipeline is a continuous deployment pipeline used to propagate updates to one or more applications in a production computing service hosted in the first cloud computing region.

15. The system of claim 8, wherein comparing the identified change to the configuration of the first computing service with a configuration for the first computing service specified in the application definition comprises:

determining a current configuration state of the first computing services; and

generating a description of the current configuration state of the first computing service, wherein the application definition and the generated description are each formatted according to a common interchange format.

16. A computer-implemented method for maintaining a deployment pipeline provisioned using an instance of a live pipeline template (LPT), the method comprising:

detecting a change made to at least a first computing service used to provide deployment pipeline;

generating a first application definition from the instance of the LPT associated with the deployment pipeline, wherein the first application definition provides a fully-specified configuration for a plurality of computing services included in the deployment pipeline, including the first computing service;

invoking, for at least the first computing service and by operation of one or more computer processors, a corresponding pipeline synthesis driver, wherein the pipeline synthesis driver reconfigures the first computing service according to the fully-specified configuration provided in the first application definition; and

building and deploying one or more applications using at least in part the reconfigured first computing service.

17. The computer-implemented method of claim 16, wherein detecting the change made to at least a first computing service used to provide deployment pipeline comprises:

generating a second application definition by invoking a plurality of analysis drivers, wherein each of the plurality of analysis drivers inspects a configuration of a respective one of the computing services included in the deployment pipeline; and

comparing the first application definition to the second application definition to detect the change made to the first computing service.

18. The computer-implemented method of claim 16, wherein the instance of the LPT includes source code for at least a first base pipeline template specifying a set of configuration parameters for one or more deployment stages of the deployment pipeline and source code specifying a set of instance specific parameters for the deployment pipeline.

19. The computer-implemented method of claim 16, wherein the deployment pipeline is a continuous deployment pipeline used to deploy changes to one or more applications in a production computing service deployed using the deployment pipeline.

20. The computer-implemented method of claim 16, further comprising, prior to invoking the corresponding pipeline synthesis driver used to reconfigure the first computing service, receiving a confirmation to enforce the configuration of the deployment pipeline specified in the instance of the live pipeline template.