Instantiating resources of an IT-service

• US 9,432,247 B2
• Filed: 12/08/2013
• Issued: 08/30/2016
• Est. Priority Date: 06/27/2012
• Status: Expired due to Fees

• 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
• Primary Examiner(s): Luu, Le H
• Application Number:
  US14/099,966
• Publication Number:
  US 20140095721A1
• Time in Patent Office: 996 Days
• US Class Current: 1/1
• 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 including nodes representing resources and being indicative of a resource type, each node comprising a generic API providing at least one abstract method for instantiating the resource represented by the respective node. For each node, determining the resource type indicated by the node; evaluating a service provider catalog indicative of a resource manager operable to provide a resource of a given resource type and determining an address of the resource manager; selecting a resource manager; sending a request to the address of the selected resource manager for a description of a resource-manager-specific API of the resource manager; receiving the requested description from the selected resource manager; overriding the abstract method by a resource-manager specific method of the resource-manager-specific API for instantiating the resource; and executing the overridden abstract method for instantiating the resource represented by the node.

Claims

1. A computer-implemented method for instantiating one or more resources of an IT-service, each resource being of one of one or more resource types, each resource being provided by one of one or more resource managers of an IT-service management system, the method comprising:

analyzing, by a management engine, a service model of said IT-service, the service model comprising nodes respectively representing one of the resources and respectively being indicative of a resource type of said represented resource, each of the nodes comprising a generic API, the generic API not being specific to any particular one of the resource managers and providing at least one abstract method for instantiating the resource represented by the respective node; and

for each of the nodes, executing, by the management engine, at runtime of the IT-service management system;

determining the one of the one or more resource types being indicated by said node;

evaluating a service provider catalog, the service provider catalog being indicative of one or more of the resource managers respectively being operable to provide a resource of a given resource type, for determining one or more of the resource managers respectively being operable to provide a resource having the determined resource type, and for determining an address of each of said determined one or more resource managers;

selecting one of the one or more resource managers;

sending a request to the address of the selected resource manager, the request being a request for a description of a resource-manager-specific API of said resource manager;

receiving the requested description from the selected resource manager;

overriding said at least one abstract method by a resource-manager specific method of the resource-manager-specific API for instantiating said resource, said resource-manager specific method being specified in the received description; and

executing the overridden at least one abstract method for instantiating the resource represented by said node.

2. The computer-implemented method of claim 1, wherein the nodes are nodes of a graph, and wherein analyzing the service model comprises traversing the graph for instantiating the resources represented by said graph'"'"'s nodes in accordance with the topology of said graph.

3. The computer-implemented method of claim 1, wherein the service model is indicative of a chronological sequence of the resources to be instantiated, said sequence being specified by means of a topology of a graph comprising the nodes or being specified by a process model contained in the service model.

4. The computer-implemented method of claim 1, further comprising, at runtime of the IT-service management system:

adding a further resource manager to the IT-service management system, the further resource manager being adapted to provide resources of a further resource type; and

as a consequence of said adding, adding a further entry to the service provider catalog, the further entry being indicative of the further resource manager, the further resource type and of an address of the further resource manager.

5. The computer-implemented method of claim 4, wherein the adding of the further entry is executed in accordance with the Open Services for Lifecycle Collaboration (OSLC) technology.

6. The computer-implemented method of claim 1, the nodes comprising at least a first and a second node, the first node representing a first resource of a first resource type, the second node representing a second resource of a second resource type, the first and second resource types being selected, in any combination, from a group comprising:

a data storage resource type for providing data storage as a service (StaaS);

an application program resource type for providing software as a service (SaaS);

a computing resource type for providing infrastructure as a service (laaS);

a networking component resource type for providing network as a service (NaaS); and

a middleware component resource type for providing platform as a service (PaaS).

7. The computer-implemented method of claim 1, wherein instantiating the resource by executing the at least one abstract method is executed by the management engine interoperating with the selected resource manager, the interoperation being executed via the obtained resource-manager-specific API.

8. The computer-implemented method of claim 1, wherein the generic API comprises further abstract methods for controlling and/or deleting an instance of the resource represented by said node, the method further comprising:

overriding said further abstract methods by a respective resource-manager specific method of the resource-manager-specific API; and

executing the overwritten generic API by the management engine, whereby the management engine interoperates with the selected resource manager, wherein the interoperation is executed for controlling and/or deleting said instance.

9. The computer-implemented method of claim 1, further comprising:

evaluating, by the management engine, the received description for determining a data transmission protocol to be used by the management engine for interoperating with the determined resource manager; and

determining one or more API methods and API parameters to be used by the management engine for interoperating with the determined resource manager; and

wherein the interoperation is executed by the determined transmission protocol and/or by the determined API methods and API parameters.

10. The computer-implemented method of claim 1, wherein the IT-service management system comprises at least a first and a second resource manager, the first resource manager comprising a first resource-manager specific API and being operable to provide a first resource of a first resource type, the second resource manager comprising a second resource- manager specific API and being operable to provide a second resource of a second resource type, the method further comprising:

instantiating at least the first resource via the first resource manager specific API by means of a first set of API methods and API parameters and/or by means of a first data transmission protocol; and

instantiating at least the second resource via the second resource manager specific API by means of a second set of API methods and API parameters and/or by means of a second data transmission protocol.