# US 2018/0026828 A1 · Instantiating resources of an it-service

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

- Number: US 2018/0026828 A1
- Document ID: US20180026828A1
- Status: Published application
- Kind: A1
- Application number: 15/724,124
- Filed: 2017-10-03
- Published: 2018-01-25
- Earliest claimed: 2012-06-27
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: John E. Arwe; Gerd Breiter; Marek Chodorowski; Felix Dross; Narine Kokhlikyan; Hoang Anh Le; David B. Lindquist; Simon Moser; Isabell Schwertle; Thomas Spatzier
- Web page: https://patentgrep.com/patent/US20180026828A1

## CPC

- H04L 41/5048: {Automatic or semi-automatic definitions, e.g. definition templates}
- G06F 9/4492: {Inheritance}
- G06F 9/50: Allocation of resources, e.g. of the central processing unit [CPU]
- G06F 9/5005: {to service a request}
- G06F 9/5016: {the resource being the memory}
- G06F 9/5027: {the resource being a machine, e.g. CPUs, Servers, Terminals}
- H04L 41/022: Multivendor or multi-standard integration
- H04L 41/046: comprising network management agents or mobile agents therefor
- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- H04L 41/22: comprising specially adapted graphical user interfaces [GUI]
- H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04L 41/5041: characterised by the time relationship between creation and deployment of a service
- H04L 41/5051: Service on demand, e.g. definition and deployment of services in real time
- H04L 47/70: Admission control; Resource allocation
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/1004: Server selection for load balancing
- H04L 67/1078: {Resource delivery mechanisms}
- H04L 67/60: Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70)
- H04L 2012/5631: {Resource management and allocation}
- 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

Instantiating a resource of an IT-service includes analyzing a service model of the IT-service where the service model includes a node representing a resource for providing the IT-service. The node has a generic API providing an abstract method for instantiating the resource. A determination is made whether the node is a multi-instance node representing a resource being instantiable multiple times. If so, a determination is made whether a first instance of the resource represented by the multi-instance node already exists in a runtime environment providing the IT-service. If so, a selection criteria is computed to identify and select a resource manager configured to instantiate a second instance of the resource based on collocation or anti-collocation parameters in the runtime environment. The abstract method for instantiating the second instance of the resource is overridden with a resource-manager specific method of a resource-manager-specific API specified by the selected resource manager.

## Claims

### Claim 1

A method, comprising:
analyzing a service model of an IT-service, the service model including a node representing a resource for providing the IT-service, the node having a generic API providing at least one abstract method for instantiating the resource;
determining if the node is a multi-instance node representing a resource being instantiable multiple times;
responsive to determining that the node is a multi-instance node, determining whether a first instance of the resource represented by the multi-instance node already exists in a runtime environment providing the IT-service;
responsive to determining that the first instance of the resource represented by the multi-instance node already exists in the runtime environment, computing a selection criteria to identify and select a resource manager configured to instantiate a second instance of the resource based on collocation or anti-collocation parameters of the second instance in the runtime environment with the first instance; and
overriding the at least one abstract method for instantiating the second instance of the resource with a resource-manager specific method of a resource-manager-specific API specified by the selected resource manager.

### Claim 2 (depends on 1)

The method of claim 1, further comprising annotating the node with a multi-instance property attribute.

### Claim 3 (depends on 1)

The method of claim 1, further comprising computing the selection criteria to identify and select the resource manager to instantiate the second instance in another runtime environment not hosting the first instance based on the anti-collocation parameter.

### Claim 4 (depends on 1)

The method of claim 1, further comprising computing the selection criteria to identify and select the resource manager to instantiate the second instance in the runtime environment hosting the first instance based on the collocation parameter.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
assigning a load characteristic to the first instance; and
instantiating the second instance in response to determining that the load characteristic of the first instance exceeds a threshold.

### Claim 6 (depends on 5)

The method of claim 5, further comprising monitoring the load characteristic of the first instance.

### Claim 7 (depends on 1)

The method of claim 1, further comprising configuring the service model to define a chronological sequence of resources to be instantiated for the IT-service.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
sending a request to an address of the resource manager for a description of the resource-manager-specific API of the resource manager;
receiving the requested description from the resource manager; and
determining a data transmission protocol to be used for interoperating with the resource manager.

### Claim 9

A method, comprising:
identifying a plurality of resource managers each operable to provide a resource for providing an IT-service;
analyzing a service model of the IT-service, the service model comprising nodes representing the respective resources, the nodes specifying a generic API, the generic API not being specific to any of the resource managers and providing at least one abstract method for instantiating the resource represented by the respective node;
selecting one of the nodes;
selecting one of the resource managers to instantiate the resource as indicated by the selected node;
sending a request to the selected resource manager for a description of a resource-manager-specific API of the resource manager; and
determining a data transmission protocol to be used for interoperating with the resource manager based on the resource-manager-specific API to instantiate the resource.

### Claim 10 (depends on 9)

The method of claim 9, further comprising overriding the abstract method for instantiating the resource with a resource-manager specific method of the resource-manager-specific API.

### Claim 11 (depends on 9)

The method of claim 9, wherein the nodes are nodes of a graph, and wherein analyzing the service model comprises traversing the graph for instantiating the resource represented by the graph's node in accordance with a topology of the graph.

### Claim 12 (depends on 9)

The method of claim 9, wherein the service model is indicative of a chronological sequence of a plurality of resources to be instantiated, the sequence being specified by a topology of a graph.

### Claim 13 (depends on 9)

The method of claim 9, wherein each resource manager includes a catalog registration unit for adding, upon deployment of the respective resource manager, an entry to the service provider catalog indicative of the respective resource manager.

### Claim 14 (depends on 13)

The method of claim 13, wherein the entry is further indicative of the resource type provided by the respective resource manager and an address of the respective resource manager.