Automated software deployment

Patent metadata

Field	Value
Publication number	US-2016239280-A1
Application number	US-201514621114-A
Country	US
Kind code	A1
Filing date	Feb 12, 2015
Priority date	Feb 12, 2015
Publication date	Aug 18, 2016
Grant date	—

Abstract

Particular deployment logic is selected that describes a plurality of steps in a type of software deployment. Release data is identified that defines a selection of a set of software artifacts to be deployed in a particular deployment. Further, environmental data is selected that describes configuration of a target system for the particular deployment. First associations are determined, using data processing apparatus, between steps in the plurality of steps and software artifacts in the set of software artifacts. Second associations are determined between steps in the plurality of steps and configuration information of the target system used in the respective steps. The artifacts are automatically deployed on the target system, using one or more data processing apparatus, based on the first and second associations.

First claim

1 . A method comprising:
identifying a selection of deployment logic describing a plurality of steps in a type of software deployment; identifying release data defining a selection of a set of software artifacts to be deployed in a particular deployment; identifying a selection of environment data describing a set of existing configuration attributes of a target system upon which the set of software artifacts are to be deployed in the particular deployment; determining, using data processing apparatus, first associations between steps in the plurality of steps and software artifacts in the set of software artifacts and second associations between steps in the plurality of steps and respective configuration attributes in the set of existing configuration attributes of the target system, wherein the second associations define configuration attributes of the target system to be used in completion of associated steps in the plurality of steps; and causing the artifacts to be automatically deployed on the target system based on the first and second associations.

2 . The method of claim 1 , further comprising generating deployment data from the selected deployment logic, the selected environment data, the release data, and the first and second associations.

3 . The method of claim 2 , wherein the artifacts are deployed automatically according to the deployment data.

4 . The method of claim 2 , wherein the selected deployment logic, the selected environment data, and the release data each originate from a different source.

5 . The method of claim 2 , further comprising generating a deployment plan module from the selected deployment logic and the release data, wherein the deployment plan module identifies each of the plurality of steps and maps each artifact in the set of artifacts to a respective one of the plurality of steps.

6 . The method of claim 5 , wherein the set of artifacts comprises a plurality of artifacts and a particular one of the plurality of artifacts is mapped to a first one of the plurality of steps and is to be used in the first step, and at least two other artifacts in the plurality of artifacts are mapped to a second one of the plurality of steps and are to be used in the second step.

7 . The method of claim 6 , wherein generating the deployment data comprises associating the selected environment data to the deployment plan module and mapping the plurality of steps and artifacts to be used in the step to respective components in the target system.

8 . The method of claim 7 , wherein the components comprise a plurality of computing devices and each of the plurality of computing devices is mapped to a respective step in the plurality of steps.

9 . The method of claim 7 , wherein the deployment plan module comprises a reusable deployment plan module to be associated with any one of a plurality of environment data modules, each plan environment data module corresponds to a respective computing system, and associating the deployment plan module to environment data causes corresponding deployment data to be generated to define deployment of the artifacts on the respective computing system using the plurality of steps.

10 . The method of claim 1 , wherein the deployment logic further describes dependencies between the plurality of steps.

11 . The method of claim 1 , wherein determining the first associations comprises:
identifying that a particular one of the plurality of steps uses a particular type of artifact; identifying that a particular one of the set of artifacts is of the particular type; and automatically associating the particular artifact with the particular step.

12 . The method of claim 1 , wherein the environment data identifies a set of components of the target system and the configuration attributes comprise a location of each component and information for accessing each component.

13 . The method of claim 12 , wherein determining the second associations comprises:
identifying that a particular one of the plurality of steps is to deploy a particular one of the set of artifacts on a particular type of system component; identifying that a particular one of the set of components is of the particular type; and automatically determining that the particular step is to be used to deploy the particular artifact on the particular component.

14 . The method of claim 1 , further comprising performing, using data processing apparatus, the deployment of the artifacts on the target system.

15 . The method of claim 1 , wherein the particular deployment comprises a deployment of new software.

16 . The method of claim 1 , wherein the particular deployment comprises deployment of an update to existing software.

17 . The method of claim 1 , further comprising generating the deployment logic based on selection of the plurality of steps from a library of defined steps.

18 . The method of claim 17 , wherein each step in the library is associated with respective step logic, and generating the deployment logic comprises:
including the step logic of each of the selected plurality of steps; and receiving a definition of dependencies between the plurality of steps.

19 . A computer program product comprising a non-transitory computer readable storage medium comprising computer readable program code embodied therewith, the computer readable program code comprising:
computer readable program code configured to identify a selection of deployment logic describing a plurality of steps in a type of software deployment; computer readable program code configured to identify release data defining a selection of a set of software artifacts to be deployed in a particular deployment; computer readable program code configured to identify a selection of environment data describing a set of existing configuration attributes of a target system upon which the set of software artifacts are to be deployed in the particular deployment; computer readable program code configured to determine first associations between steps in the plurality of steps and software artifacts in the set of software artifacts and second associations between steps in the plurality of steps and respective configuration attributes in the set of existing configuration attributes of the target system, wherein the second associations define configuration attributes of the target system to be used in completion of associated steps in the plurality of steps; and computer readable program code configured to cause the artifacts to be automatically deployed on the target system based on the first and second associations.

20 . A system comprising:
a data processing apparatus; a memory element; a deployment automation engine to:
identify a selection of deployment logic describing a plurality of steps in a type of software deployment;
identify a selection of a set of software artifacts to be deployed in a particular deployment;
identify a selection of environment data describing a set of existing configuration attributes of a target system upon which the set of software artifacts are to be deployed in the particular deployment;
determine first associations between steps in the plurality of steps and software artifacts in the set of software artifacts and second associations between steps in the plurality of steps and respective configuration attributes in the set of existing configuration attributes of the target system, wherein the second associations define configuration attributes of the target system to be used in completion o

Assignees

• Ca Inc

Inventors

• Scheiner Uri
• Avisror Yaron

Classifications

• G06F8/65

  Updates (security arrangements therefor G06F21/57) · CPC title

• G06F8/61

  Installation · CPC title

• G06F8/60 Primary

  Software deployment · CPC title