Discovery and modeling of deployment actions for multiple deployment engine providers

• US 10,628,128 B2
• Filed: 03/26/2018
• Issued: 04/21/2020
• Est. Priority Date: 06/30/2012
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Berg, Daniel C., Elder, Michael D., Gaponenko, Yulia, Poddar, Indrajit, Pravosud, Yuri
• Primary Examiner(s): Bullock, Jr., Lewis A
• Assistant Examiner(s): Kepnang, Gilles R
• Application Number:
  US15/935,248
• Publication Number:
  US 20180210708A1
• Time in Patent Office: 757 Days
• Field of Search: None
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/35 model driven
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0886 Fully automatic configuration
• 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

Abstract

Provided are techniques for modeling operational units, each operational unit corresponding to an operational workflow and to one or more deployment engines of a plurality of deployment engines; selecting, for each of the plurality of operational units, one of the corresponding deployment engines; ordering the operational units with respect to the operational workflow; grouping the ordered operation units according to the selected deployment engines into deployment engine groupings; mapping output parameters corresponding to a first operational unit that concludes a first deployment engine grouping to input parameters corresponding to a second operational unit that initiates a second deployment engine grouping, inserting between the first operational unit and the second operational unit a transitional operational unit for transitioning between a first deployment engine corresponding to the first deployment engine grouping and a second deployment engine corresponding to the second deployment engine grouping to generate a multi-deployment engine operational workflow.

Claims

1. A method, comprising:

modeling a plurality of operational units, each operational unit implementing a portion of an operational workflow by one or more deployment engines of a plurality of deployment engines;

selecting, for each of the plurality of operational units, one of the deployment engines of the one or more deployment engines, wherein the one or more deployment engines include at least a first deployment engine and a second deployment engine;

ordering the operational units with respect to the operational workflow;

grouping the ordered operational units according to the selected deployment engines into a plurality of deployment engine groupings, wherein a first deployment engine grouping of the plurality of deployment engine groupings belongs to the first deployment engine, and wherein a second deployment engine grouping of the plurality of deployment engine groupings belongs to the second deployment engine;

generating a mapping of a plurality of output parameters to a plurality of input parameters, the output parameters corresponding to a first operational unit that concludes the first deployment engine grouping of the plurality of deployment engine groupings, the input parameters corresponding to a second operational unit that initiates the second deployment engine grouping, and the second grouping immediately follows the first grouping with respect to the ordering, wherein the input parameters corresponding to the second operational unit is generated based on the output parameters of the first deployment engine grouping;

inserting, based upon the mapping, a transitional operational unit between the first operational unit that concludes the first deployment engine grouping and the second operational unit that initiates the second deployment engine grouping;

generating a multi-deployment engine operational workflow;

storing for execution the multi-deployment engine operational workflow;

prior to invoking the second deployment engine;

generating the output parameters of the first deployment engine grouping; and

based on the transitional operational unit, converting the output parameters into the input parameters of the second deployment engine grouping; and

executing the multi-deployment engine operational workflow.

2. The method of claim 1, the inserting, comprising mapping a plurality of output parameters corresponding to a first deployment action that concludes the first operational unit to a plurality of input parameters of a second deployment action that initiates the second operational unit.

3. The method of claim 1, further comprising designating a particular deployment engine of the plurality of deployment engines as a master deployment engine, wherein the master deployment engine executes the transitional operational unit.

4. The method of claim 1, further comprising inserting a transitional operational unit between each pair of adjacent deployment engine groupings.

5. The method of claim 1, further comprising providing a graphical user interface (GUI) for the selecting, for each of the plurality of operational units, one of the corresponding deployment engines of the one or more deployment engines.

6. An apparatus, comprising:

a processor;

a computer-readable storage medium coupled to the processor; and

logic, stored on the computer-readable storage medium and executed on the processor, for;

modeling a plurality of operational units, each operational unit implementing a portion of an operational workflow by one or more deployment engines of a plurality of deployment engines;

selecting, for each of the plurality of operational units, one of the deployment engines of the one or more deployment engines, wherein the one or more deployment engines include at least a first deployment engine and a second deployment engine;

ordering the operational units with respect to the operational workflow;

grouping the ordered operational units according to the selected deployment engines into a plurality of deployment engine groupings, wherein a first deployment engine grouping of the plurality of deployment engine groupings belongs to the first deployment engine, and wherein a second deployment engine grouping of the plurality of deployment engine groupings belongs to the second deployment engine;

generating a mapping of a plurality of output parameters to a plurality of input parameters, the output parameters corresponding to a first operational unit that concludes the first deployment engine grouping of the plurality of deployment engine groupings, the input parameters corresponding to a second operational unit that initiates the second deployment engine grouping, and the second grouping immediately follows the first grouping with respect to the ordering, wherein the input parameters corresponding to the second operational unit is generated based on the output parameters of the first deployment engine grouping;

inserting, based upon the mapping, a transitional operational unit between the first operational unit that concludes the first deployment engine grouping and the second operational unit that initiates the second deployment engine grouping;

generating a multi-deployment engine operational workflow;

storing for execution the multi-deployment engine operational workflow;

prior to invoking the second deployment engine;

generating the output parameters of the first deployment engine grouping; and

based on the transitional operational unit, converting the output parameters into the input parameters of the second deployment engine grouping; and

executing the multi-deployment engine operational workflow.

7. The apparatus of claim 6, the logic for the inserting, comprising logic for mapping a plurality of output parameters corresponding to a first deployment action that concludes the first operational unit to a plurality of input parameters of a second deployment action that initiates the second operational unit.

8. The apparatus of claim 6, the logic further comprising logic for designating a particular deployment engine of the plurality of deployment engines as a master deployment engine, wherein the master deployment engine executes the transitional operational unit.

9. The apparatus of claim 6, the logic further comprising logic for inserting a transitional operational unit between each pair of adjacent deployment engine groupings.

10. The apparatus of claim 6, further comprising a graphical user interface (GUI) for the selecting, for each of the plurality of operational units, one of the deployment engines of the one or more deployment engines.

11. A non-transitory computer programming product, comprising:

A computer-readable storage medium; and

logic, stored on the computer-readable storage medium for execution on a processor, for;

logic, stored on the computer-readable storage medium and executed on the processor, for;

modeling a plurality of operational units, each operational unit implementing a portion of an operational workflow by one or more deployment engines of a plurality of deployment engines;

selecting, for each of the plurality of operational units, one of the deployment engines of the one or more deployment engines, wherein the one or more deployment engines include at least a first deployment engine and a second deployment engine;

ordering the operational units with respect to the operational workflow;

grouping the ordered operational units according to the selected deployment engines into a plurality of deployment engine groupings, wherein a first deployment engine grouping of the plurality of deployment engine groupings belongs to the first deployment engine, and wherein a second deployment engine grouping of the plurality of deployment engine groupings belongs to the second deployment engine;

generating a mapping of a plurality of output parameters to a plurality of input parameters, the output parameters corresponding to a first operational unit that concludes the first deployment engine grouping of the plurality of deployment engine groupings, the input parameters corresponding to a second operational unit that initiates the second deployment engine grouping, and the second grouping immediately follows the first grouping with respect to the ordering, wherein the input parameters corresponding to the second operational unit is generated based on the output parameters of the first deployment engine grouping;

inserting, based upon the mapping, a transitional operational unit between the first operational unit that concludes the first deployment engine grouping and the second operational unit that initiates the second deployment engine grouping;

generating a multi-deployment engine operational workflow;

storing for execution the multi-deployment engine operational workflow;

prior to invoking the second deployment engine;

generating the output parameters of the first deployment engine grouping; and

based on the transitional operational unit, converting the output parameters into the input parameters of the second deployment engine grouping; and

executing the multi-deployment engine operational workflow.

12. The non-transitory computer programming product of claim 11, the logic for inserting, comprising logic for mapping a plurality of output parameters corresponding to a first deployment action that concludes the first operational unit to a plurality of input parameters of a second deployment action that initiates the second operational unit.

13. The non-transitory computer programming product of claim 11, the logic further comprising logic for designating a particular deployment engine of the plurality of deployment engines as a master deployment engine, wherein the master deployment engine executes the transitional operational unit.

14. The non-transitory computer programming product of claim 11, the logic further comprising logic for inserting a transitional operational unit between each pair of adjacent deployment engine groupings.

15. The non-transitory computer programming product of claim 11, the logic further comprising logic for providing a graphical user interface (GUI) for the selecting, for each of the plurality of operational units, one of the deployment engines of the one or more corresponding deployment engines.