Instantiating resources of an IT-service

• US 9,787,528 B2
• Filed: 08/02/2016
• Issued: 10/10/2017
• 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
• Primary Examiner(s): Luu, Le H
• Application Number:
  US15/226,556
• Publication Number:
  US 20160344840A1
• Time in Patent Office: 434 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. A resource type of the resource being indicated by the node is determined, and a service provider catalog is evaluated to determine a resource manager operable to instantiate the resource and an address of the resource manager. A request is sent to the address of the resource manager for a description of a resource-manager-specific API of the resource manager. Upon receipt of the requested description, at least one abstract method for instantiating the resource is overridden with a resource-manager specific method of the resource-manager-specific API, and the resource-manager specific method for instantiating the resource represented by the node is executed.

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;

determining a resource type of the resource being indicated by the node;

evaluating a service provider catalog to determine a resource manager being operable to instantiate the resource and an address of the resource manager;

sending a request to the address of the resource manager for a description of a resource-manager-specific API of the resource manager;

receiving the requested description from the resource manager;

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

executing the resource-manager specific method for instantiating the resource represented by the node.

2. The method of claim 1, further comprising adding, upon deployment of a further resource manager, an entry to the service provider catalog indicative of the further resource manager.

3. The method of claim 1, further comprising, upon deployment of the resource manager, adding an entry to the service provider catalog, the entry being indicative of the resource manager, the resource type provided by the resource manager, and the address of the resource manager.

4. The method of claim 3, further comprising, upon receipt of the request, sending the description of the resource manager-specific API from the resource manager to a management engine.

5. The method of claim 1, wherein the node is a node 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.

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

7. The method of claim 1, further comprising:

evaluating the received description for determining a data transmission protocol to be used for interoperating with the resource manager;

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

executing the interoperation by the determined transmission protocol and/or by the determined API methods and API parameters.

8. 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 resource managers and providing at least one abstract method for instantiating the resource represented by the respective node;

selecting one of the nodes;

evaluating a service provider catalog and selecting one of the resource managers being operable 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;

overriding the abstract method for instantiating the resource with a resource-manager specific method of the resource-manager-specific API; and

executing the resource-manager specific method for instantiating the resource represented by the node.

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

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

11. The method of claim 8, wherein the management engine is further configured for:

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

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

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

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

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

14. A method, comprising:

upon deployment of a resource manager operable to instantiate a resource of an IT-service, adding an entry to a service provider catalog of the resource manager, the entry being indicative of the resource manager, a resource type provided by the resource manager, and an address of the resource manager;

receiving a request for a description of a resource-manager-specific API of the resource manager;

sending, for the resource, the description to a management engine of an IT-service management system;

sending, to the management engine, a description of a transmission protocol for enabling the management engine to interoperate with the resource manager via the resource-manager-specific API to instantiate the resource.

15. The method of claim 14, wherein the sending of the description comprises sending at least one resource-manager specific method for instantiating the resource.