# US 2016/0254965 A1 · Stitching an application model to an infrastructure template

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2016/0254965 A1
- Document ID: US20160254965A1
- Status: Published application
- Kind: A1
- Application number: 15/028,527
- Filed: 2013-10-30
- Published: 2016-09-01
- Earliest claimed: 2013-10-30
- Assignees: Hewlett Packard Enterprise Development LP
- Applicants: Hewlett Packard Enterprise Development LP
- Inventors: Stephane Herman Maes
- Web page: https://patentgrep.com/patent/US20160254965A1

## CPC

- H04L 41/122: of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
- H04L 41/22: comprising specially adapted graphical user interfaces [GUI]
- H04L 41/5041: characterised by the time relationship between creation and deployment of a service
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/562: Brokering proxy services
- G06F 8/10: Requirements analysis; Specification techniques
- H04L 41/5096: {wherein the managed service relates to distributed or central networked applications}
- H04L 67/52: specially adapted for the location of the user terminal
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## 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

### Claim 1

A method of stitching an application model to an infrastructure topology, comprising:
identifying patterns in the application model;
identifying patterns in the infrastructure topology;
matching the patterns in the application model and infrastructure topology using policies associated with the application model.

### Claim 2 (depends on 1)

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

### Claim 3 (depends on 2)

The method of claim 2, in which the number of portions of infrastructure templates are stitched together based on policies and lifecycle management actions (LCMAs).

### Claim 4 (depends on 1)

The method of claim 1, in matching the patterns in the application model and infrastructure topology using policies associated with the application model comprises matching policies and 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.

### Claim 5 (depends on 1)

The method of claim 1, in which 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.

### Claim 6 (depends on 5)

The method of claim 5, further comprising:
providing the 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 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.

### Claim 7 (depends on 6)

The method of claim 6, 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 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.

### Claim 8 (depends on 1)

The method of claim 1, in which using policies associated with the application model to match the patterns in the application model and infrastructure topology comprises:
discovering requirements in the application level;
associating those requirements with components that support them in a library of infrastructure topologies.

### Claim 9

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.

### Claim 10 (depends on 9)

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

### Claim 11 (depends on 9)

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

### Claim 12 (depends on 9)

The system of claim 9, 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.

### Claim 13 (depends on 9)

The system of claim 9, further comprising a graphical user interface in which the system receives 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 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.

### Claim 14

A computer program product for stitching an application model to an infrastructure template, the computer program product comprising:
a computer readable storage medium comprising computer usable program code embodied therewith, the computer usable program code comprising:
computer usable program code to, when executed by a processor, identify patterns in the application model;
computer usable program code to, when executed by a processor, identify patterns in the infrastructure template; and
computer usable program code to, when executed by a processor, match the patters in the application model and the infrastructure topology using policies associated with the application model.

### Claim 15 (depends on 14)

The computer program product of claim 14, further comprising:
computer program code to, when executed by a processor, 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;
computer program code to, when executed by a processor, provide the 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 customer via a graphical user interface; and
computer program code to, when executed by a processor, 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 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.
