Release management system for a multi-node application

• US 9,043,767 B2
• Filed: 03/23/2012
• Issued: 05/26/2015
• Est. Priority Date: 04/12/2011
• Status: Active Grant

• Current Assignee: Pivotal Software, Inc. (Broadcom, Inc.)
• Original Assignee: Pivotal Software, Inc. (Broadcom, Inc.)
• Inventors: Spivak, Vadim, Skaar, Kent, Shaldibin, Oleg
• Primary Examiner(s): Wong, Don
• Assistant Examiner(s): KABIR, MOHAMMAD H
• Application Number:
  US13/428,121
• Publication Number:
  US 20120266158A1
• Time in Patent Office: 1,159 Days
• US Class Current: 717/148
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 2009/45595 Network integration; Enabling network access in virtual machine instances
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/5055 considering software capabilities, i.e. software resources associated or available to the machine
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

A deployment system provides the ability to deploy a multi-node distributed application, such as a cloud computing platform application that has a plurality of interconnected nodes performing specialized jobs. The deployment system includes a release management system that builds and manages versioned releases of application services and/or software modules that are executed by the plurality of nodes of the cloud computing platform application. The release management system utilizes specification files to define a jobs and application packages and configurations needed to perform the jobs. The jobs and application packages are assembled into a self-contained release bundle that may be provided to the deployment system. The deployment system unwraps the release bundle and provides each job to deployment agents executing on VMs. The deployment agents apply the jobs to their respective VM (e.g., launching applications), thereby deploying the cloud computing platform application.

Claims

1. A computer-implemented method for managing releases of an application having a plurality of functional components that are executed on a plurality of different nodes, the method comprising:

retrieving a first plurality of specifications for the functional components, wherein each of the first plurality of specifications specifies one or more software components required to implement one of the functional components;

retrieving a second plurality of specifications for the specified software components, wherein each of the second plurality of specifications specifies contents of a software component used to compile a compatible executable file of the software component, the specifications including one or more files having computer code formatted in an architecture-independent representation; and

generating an archive file that includes the first plurality of specifications for the functional components and the contents specified by the second plurality of specifications, wherein the archive file is assigned a version number that identifies a release of the application.

2. The method of claim 1, wherein each of the second plurality of specifications further specifies a compilation script configured to generate a runtime executable for the specified software component based on the one or more files having computer code formatted in an architecture-independent format.

3. The method of claim 1, further comprising:

retrieving a cached copy of one of the software components from a previous generation of the archive file; and

determining whether the one of the software components specified by the one of the second plurality of specifications has been changed from the cached copy according to a fingerprint value generated based on the specified contents of the software component;

responsive to determining the one of the software components have been changed, generating a package of the contents of the software component for inclusion in the archive file.

4. The method of claim 1, wherein the retrieving the first plurality of specifications comprises:

scanning a local file directory to identify specification files having a pre-determined file type.

5. The method of claim 1, further comprising:

generating a first plurality of manifest files for the functional components for inclusion in the archive file, each of the manifest files incorporating the contents of a corresponding one of the first plurality of specifications and including a fingerprint value and versioning identifier for the functional component.

6. The method of claim 5, further comprising:

generating a second plurality of manifest files for the software components for inclusion in the archive file, each of the manifest files for the software components incorporating the contents of a corresponding one of the second plurality of specifications and including a fingerprint value and versioning identifier for the software component.

7. The method of claim 1, further comprising:

providing, to a deployment module, the generated archive file to distribute the one or more files contained therein to a plurality of VMs configured to execute an instance of any one of the functional components.

8. A non-transitory computer-readable storage medium comprising instructions that, when executed in a computing device, manage releases of an application having a plurality of functional components that are executed on a plurality of different nodes, by performing the steps of:

retrieving a first plurality of specifications for the functional components, wherein each of the first plurality of specifications specifies one or more software components required to implement one of the functional components;

retrieving a second plurality of specifications for the specified software components, wherein each of the second plurality of specifications specifies contents of a software component used to compile a compatible executable file of the software component, the specifications including one or more files having computer code formatted in an architecture-independent representation; and

generating an archive file that includes the first plurality of specifications for the functional components and the contents specified by the second plurality of specifications, wherein the archive file is assigned a version number that identifies a release of the application.

9. The non-transitory computer-readable storage medium of claim 8, wherein each of the second plurality of specifications further specifies a compilation script configured to generate a runtime executable for the specified software component based on the one or more files having computer code formatted in an architecture-independent format.

10. The non-transitory computer-readable storage medium of claim 8, further comprising instructions that, when executed in the computing device, perform the steps of:

retrieving a cached copy of one of the software components from a previous generation of the archive file; and

determining whether the one of the software components specified by the one of the second plurality of specifications has been changed from the cached copy according to a fingerprint value generated based on the specified contents of the software component;

responsive to determining the one of the software components have been changed, generating a package of the contents of the software component for inclusion in the archive file.

11. The non-transitory computer-readable storage medium of claim 8, wherein the instructions for retrieving the first plurality of specifications comprises instructions that perform the steps of:

scanning a local file directory to identify specification files having a pre-determined file type.

12. The non-transitory computer-readable storage medium of claim 8, further comprising instructions that, when executed in the computing device, perform the steps of:

generating a first plurality of manifest files for the functional components for inclusion in the archive file, each of the manifest files incorporating the contents of a corresponding one of the first plurality of specifications and including a fingerprint value and versioning identifier for the functional component.

13. The non-transitory computer-readable storage medium of claim 12, further comprising instructions that, when executed in the computing device, perform the steps of:

generating a second plurality of manifest files for the software components for inclusion in the archive file, each of the manifest files for the software components incorporating the contents of a corresponding one of the second plurality of specifications and including a fingerprint value and versioning identifier for the software component.

14. The non-transitory computer-readable storage medium of claim 8, further comprising instructions that, when executed in the computing device, perform the steps of:

providing, to a deployment module, the generated archive file to distribute the one or more files contained therein to a plurality of VMs configured to execute an instance of any one of the functional components.

15. A computer system for managing releases of an application having a plurality of functional components that are executed on a plurality of different nodes, the computer system comprising a system memory and a processor programmed to carry out the steps of:

retrieving a first plurality of specifications for the functional components, wherein each of the first plurality of specifications specifies one or more software components required to implement one of the functional components;

retrieving a second plurality of specifications for the specified software components, wherein each of the second plurality of specifications specifies contents of a software component used to compile a compatible executable file of the software component, the specifications including one or more files having computer code formatted in an architecture-independent representation; and

generating an archive file that includes the first plurality of specifications for the functional components and the contents specified by the second plurality of specifications, wherein the archive file is assigned a version number that identifies a release of the application.

16. The computer system of claim 15, wherein each of the second plurality of specifications further specifies a compilation script configured to generate a runtime executable for the specified software component based on the one or more files having computer code formatted in an architecture-independent format.

17. The computer system of claim 15, wherein the processor is further programmed to carry out the step of:

retrieving a cached copy of one of the software components from a previous generation of the archive file; and

determining whether the one of the software components specified by the one of the second plurality of specifications has been changed from the cached copy according to a fingerprint value generated based on the specified contents of the software component;

responsive to determining the one of the software components have been changed, generating a package of the contents of the software component for inclusion in the archive file.

18. The computer system of claim 15, wherein the processor is further programmed to carry out the step of:

scanning a local file directory to identify specification files having a pre-determined file type.

19. The computer system of claim 15, wherein the processor is further programmed to carry out the step of:

generating a first plurality of manifest files for the functional components for inclusion in the archive file, each of the manifest files incorporating the contents of a corresponding one of the first plurality of specifications and including a fingerprint value and versioning identifier for the functional component.

20. The computer system of claim 19, wherein the processor is further programmed to carry out the step of:

generating a second plurality of manifest files for the software components for inclusion in the archive file, each of the manifest files for the software components incorporating the contents of a corresponding one of the second plurality of specifications and including a fingerprint value and versioning identifier for the software component.