Stitching an application model to an infrastructure template

• US 10,212,051 B2
• Filed: 10/30/2013
• Issued: 02/19/2019
• Est. Priority Date: 10/30/2013
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Inventors: Maes, Stephane Herman
• Primary Examiner(s): Chan, Wing F
• Assistant Examiner(s): Maniwang, Joseph R
• Application Number:
  US15/028,527
• Publication Number:
  US 20160254965A1
• Time in Patent Office: 1,938 Days
• Field of Search: 709223
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/122 of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 41/5096 wherein the managed service relates to distributed or central networked applications
• 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/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/562 Brokering proxy services

Abstract

A method of stitching an application model to an infrastructure template, comprising identifying patterns in the application model, identifying patterns in the infrastructure topology, and matching the patterns in the application model and infrastructure topology using policies associated with the application model. A system for stitching an application model to an infrastructure topology, comprising a stitching engine, and a number of infrastructure topology sources, in which the stitching engine, identifies patterns in the application model, identifies patterns in the infrastructure topology, and matches the patterns in the application model and infrastructure topology using policies associated with the application model.

Claims

1. A method of stitching an application model to an infrastructure topology, comprising:

identifying, by at least one processor of a cloud service broker, patterns in the application model;

identifying, by the at least one processor of the cloud service broker, patterns in the infrastructure topology;

matching, by the at least one processor of the cloud service broker, the patterns in the application model and infrastructure topology using policies associated with the application model, wherein the matching comprises matching policies and lifecycle management actions (LCMAs) associated with a number of nodes of the application model with policies and LCMAs associated with a number of nodes of the infrastructure topology; and

stitching, by the at least one processor of the cloud service broker, the application model with the infrastructure topology based on at least the matching.

2. The method of claim 1, wherein the infrastructure topology comprises a number of portions of a number of infrastructure templates stitched together to form an infrastructure template.

3. The method of claim 2, wherein the number of portions of infrastructure templates are stitched together based on policies and LCMAs.

4. The method of claim 1, wherein matching the patterns in the application model and infrastructure topology using policies associated with the application model further comprises searching a number of realized topologies in a realized topology system management (RTSM) database and a number of lifecycle management (LCM) topologies in a catalog to find matches to the application model.

5. The method of claim 4, further comprising:

providing the number of realized topologies, the number of lifecycle management (LCM) topologies, portions of realized topologies, portions of lifecycle management (LCM) topologies, or combinations thereof to a customer via a graphical user interface;

or

providing a number of realized topologies, number of lifecycle management (LCM) topologies, portions of realized topologies, portions of lifecycle management (LCM) topologies, or combinations thereof to a stitching engine, in which the stitching engine matches the patterns in the application model and infrastructure topology using policies associated with the application model.

6. The method of claim 5, further comprising receiving input from a customer, via the graphical user interface, indicating how the realized topologies, number of lifecycle management (LCM) topologies, portions of realized topologies, portions of lifecycle management (LCM) topologies, or combinations thereof are to be modified to allow the application model to be stitched to the realized topologies, number of lifecycle management (LCM) topologies, portions of realized topologies, portions of lifecycle management (LCM) topologies, or combinations thereof.

7. The method of claim 1, wherein using policies associated with the application model to match the patterns in the application model and infrastructure topology comprises:

discovering requirements in an application level;

associating those requirements with components that support them in a library of infrastructure topologies.

8. A system for stitching an application model to an infrastructure topology, comprising:

a stitching engine, wherein the stitching engine comprises at least one processor of a cloud service broker; and

a number of infrastructure topology sources;

wherein the stitching engine;

identifies patterns in the application model;

identifies patterns in the infrastructure topology;

matches the patterns in the application model and infrastructure topology using policies associated with the application model, wherein the matching comprises matching policies and lifecycle management actions (LCMAs) associated with a number of nodes of the application model with policies and LCMAs associated with a number of nodes of the infrastructure topology; and

stitches, by the at least one processor of the cloud service broker, the application model with the infrastructure topology based on at least the matching.

9. The system of claim 8, wherein the infrastructure topology comprises a number of portions of a number of infrastructure templates stitched together to form an infrastructure template.

10. The system of claim 9, wherein the number of portions of the number of infrastructure templates are stitched together based on policies associated with the number of portions of the number of infrastructure templates.

11. The system of claim 8, further comprising:

a realized topology system management (RTSM) comprising a number of realized topologies; and

a catalog comprising a number of lifecycle management (LCM) topologies;

in which matching the patterns in the application model and infrastructure topology using policies associated with the application model further comprises searching the number of realized topologies in the realized topology system management (RTSM) database and the number of lifecycle management (LCM) topologies in the catalog to find matches to the application model.

12. The system of claim 8, further comprising a graphical user interface in which the system receives input from a customer, via the graphical user interface, indicating how realized topologies, a number of lifecycle management (LCM) topologies, portions of realized topologies, portions of lifecycle management (LCM) topologies, or combinations thereof are to be modified to allow the application model to be stitched to the realized topologies, number of lifecycle management (LCM) topologies, portions of realized topologies, portions of lifecycle management (LCM) topologies, or combinations thereof.

13. A non-transitory computer readable storage medium encoded with computer usable program code, the computer usable program code for stitching an application model to an infrastructure template, executable by a tangible processor, the computer readable storage medium comprising, computer usable program code to:

identify patterns in the application model;

identify patterns in the infrastructure template;

match the patterns in the application model and the infrastructure topology using policies associated with the application model, wherein the matching comprises matching policies and lifecycle management actions (LCMAs) associated with a number of nodes of the application model with policies and LCMAs associated with a number of nodes of the infrastructure topology;

stitch the application model with the infrastructure topology based on at least the matching.

14. The non-transitory computer readable storage medium of claim 13, further comprising computer usable program code to:

search a number of realized topologies in a realized topology system management (RTSM) database and a number of lifecycle management (LCM) topologies in a catalog to find matches to the application model;

provide the number of realized topologies, the number of lifecycle management (LCM) topologies, portions of realized topologies, portions of lifecycle management (LCM) topologies, or combinations thereof to a customer via a graphical user interface; and

receive input from a customer, via a graphical user interface, indicating how the realized topologies, number of lifecycle management (LCM) topologies, portions of realized topologies, portions of lifecycle management (LCM) topologies, or combinations thereof are to be modified to allow the application model to be stitched to the realized topologies, number of lifecycle management (LCM) topologies, portions of realized topologies, portions of lifecycle management (LCM) topologies, or combinations thereof.