INSTANTIATING RESOURCES OF AN IT-SERVICE

• US 20180026828A1
• Filed: 10/03/2017
• Published: 01/25/2018
• Est. Priority Date: 06/27/2012
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Arwe, John E., Breiter, Gerd, Chodorowski, Marek, Dross, Felix, Kokhlikyan, Narine, Le, Hoang Anh, Lindquist, David B., Moser, Simon, Schwertle, Isabell, Spatzier, Thomas
• Granted Patent: US 10,135,669 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 9/4492 Inheritance
• CPC Class Codes: G06F 9/50 Allocation of resources, e.g. of the central processing unit [CPU]
• CPC Class Codes: G06F 9/5005 to service a request
• CPC Class Codes: G06F 9/5016 the resource being the memory
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• CPC Class Codes: H04L 2012/5631 Resource management and allocation
• CPC Class Codes: H04L 41/022 Multivendor or multi-standard integration
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 41/5048 Automatic or semi-automatic definitions, e.g. definition templates
• CPC Class Codes: H04L 41/5051 Service on demand, e.g. definition and deployment of services in real time
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• 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/1004 Server selection for load balancing
• CPC Class Codes: H04L 67/1078 Resource delivery mechanisms
• CPC Class Codes: 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

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

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.

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

3. 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.

4. 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.

5. 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.

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

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

8. 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.

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.

10. 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.

11. 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.

12. 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.

13. 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.

14. 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.