Application resiliency using APIs

• US 10,601,680 B2
• Filed: 01/09/2018
• Issued: 03/24/2020
• Est. Priority Date: 06/02/2016
• Status: Active Grant

• Current Assignee: Kyndryl Incorporated (Kyndryl Holdings, Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: Gunjal, Richard D., Hardikar, Dilip V., Mandalia, Baiju D., Ramakrishna, Madhusudan, Robinson, Joseph D.
• Primary Examiner(s): Serrao, Ranodhi
• Application Number:
  US15/865,908
• Publication Number:
  US 20180152339A1
• Time in Patent Office: 805 Days
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5025 by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
• CPC Class Codes: H04L 41/5058 Service discovery by the service manager
• CPC Class Codes: H04L 41/5096 wherein the managed service relates to distributed or central networked applications

Abstract

An approach is provided for managing resiliency of an application provided by a first service provider (SP). A fail condition indicating an outage of a first service of the first SP is detected. Based on a topology mapping the first SP to a second SP and the first service to a second service of the second SP, a first API provided by the first SP is determined to have provided the first service prior to the fail condition, and a second API provided by the second SP is determined to provide the second service. The first API is disabled and the second API is activated, thereby continuing to provide a functionality of the application that had been provided by the first service prior to the fail condition being detected, even though the first SP is experiencing the fail condition.

Claims

1. A method of managing resiliency of an application provided by a first service provider (SP), the method comprising the steps of:

a computer detecting a fail condition of the first SP, which indicates an outage of a first service provided by the first SP;

in response to the step of detecting the fail condition and based on a topology which maps the first SP to a second SP and maps the first service to a second service provided by the second SP, the computer determining that a first application programming interface (API) provided by the first SP had provided the first service prior to the fail condition and that a second API provided by the second SP provides the second service;

based on the first API having provided the first service and the second API providing the second service, the computer disabling the first API provided by the first SP and activating the second API provided by the second SP, so that a functionality of the application that had been provided by the first service prior to the fail condition being detected continues by being provided by the second API even though the first SP is experiencing the fail condition;

the computer receiving information specifying the first and second services;

the computer receiving other information specifying the application and infrastructure components of the first and second SPs, which are cloud service providers; and

based on the information specifying the first and second services and the other information specifying the application and the infrastructure components, the computer generating the topology.

2. The method of claim 1, further comprising the steps of:

the computer receiving sets of APIs for respective portals of corresponding SPs which are corresponding cloud service providers (CSPs), each of the received sets of APIs indicating mechanisms to deploy a service on the corresponding CSP, the mechanisms including at least one of deploying a virtual machine, configuring the virtual machine, deploying a network, configuring the network, deploying middleware, configuring the middleware, deploying the application, and configuring the application;

the computer storing the sets of APIs in a configuration management database (CMDB); and

the computer generating and storing rules in the CMDB, so that each rule indicates conditions under which a corresponding set of APIs is executed to deploy the service on the corresponding CSP,

wherein the steps of disabling the first API and activating the second API are based on the rules stored in the CMDB.

3. The method of claim 1, further comprising the steps of:

the computer receiving sets of APIs for respective SPs which are respective cloud service providers (CSPs), each of the received sets of APIs indicating mechanisms to deploy a service on a corresponding CSP included in the respective CSPs;

the computer generating and storing rules in a configuration management database (CMDB), so that each rule indicates conditions under which a corresponding set of APIs is executed to deploy the service on the corresponding CSP;

the computer obtaining a subscription to a service that sends a notification of changes to the sets of APIs;

based on the subscription, the computer receiving a notification of a change to a set of APIs specified by a rule stored in the CMDB; and

in response to the step of receiving the notification, the computer updating the rule in the CMDB based on the change to the set of APIs.

4. The method of claim 1, further comprising the steps of:

the computer receiving first, second, and third information about the first service provided by the first SP which is a first cloud service provider (CSP), the second service provided by the second SP which is a second CSP, and the a third service provided by a third SP which is a third CSP, respectively, wherein the first, second, and third information includes geographic attributes of the first, second, and third CSPs, respectively;

the computer determining that the second and third services provide the functionality of the application;

the computer determining a threshold for a latency of the application;

based on the geographic attributes in the second information, the computer determining that redeploying the application to the second CSP results in a first latency of the application;

based on the geographic attributes in the third information, the computer determining that redeploying the application to the third CSP results in a second latency of the application;

the computer determining that the first latency does not exceed the threshold and the second latency exceeds the threshold; and

based on the second service providing the functionality of the application, the first latency not exceeding the threshold, and the second latency exceeding the threshold, the computer redeploying the application to the second CSP and not to the third CSP.

5. The method of claim 1, wherein the step of detecting the fail condition includes detecting an outage of an entire data center provided by the first SP which is a first cloud service provider (CSP), the outage of the entire data center causing the outage of the first service.

6. The method of claim 1, further comprising the step of:

providing at least one support service for at least one of creating, integrating, hosting, maintaining, and deploying computer-readable program code in the computer, the program code being executed by a processor of the computer to implement the steps of detecting the fail condition, determining that the first API had provided the first service prior to the fail condition and that the second API provides the second service, disabling the first API, activating the second API, receiving the information specifying the first and second services, receiving the other information specifying the application and the infrastructure components of the first and second SPs, and generating the topology.

7. A computer program product, comprising:

a computer-readable storage device; and

a computer-readable program code stored in the computer-readable storage device, the computer-readable program code containing instructions that are executed by a central processing unit (CPU) of a computer system to implement a method of managing resiliency of an application provided by a first service provider (SP), the method comprising the steps of;

the computer system detecting a fail condition of the first SP, which indicates an outage of a first service provided by the first SP;

in response to the step of detecting the fail condition and based on a topology which maps the first SP to a second SP and maps the first service to a second service provided by the second SP, the computer system determining that a first application programming interface (API) provided by the first SP had provided the first service prior to the fail condition and that a second API provided by the second SP provides the second service;

based on the first API having provided the first service and the second API providing the second service, the computer system disabling the first API provided by the first SP and activating the second API provided by the second SP, so that a functionality of the application that had been provided by the first service prior to the fail condition being detected continues by being provided by the second API even though the first SP is experiencing the fail condition;

the computer system receiving information specifying the first and second services;

the computer system receiving other information specifying the application and infrastructure components of the first and second SPs, which are cloud service providers; and

based on the information specifying the first and second services and the other information specifying the application and the infrastructure components, the computer system generating the topology.

8. The computer program product of claim 7, wherein the method further comprises the steps of:

the computer system receiving sets of APIs for respective portals of corresponding SPs which are corresponding cloud service providers (CSPs), each of the received sets of APIs indicating mechanisms to deploy a service on the corresponding CSP, the mechanisms including at least one of deploying a virtual machine, configuring the virtual machine, deploying a network, configuring the network, deploying middleware, configuring the middleware, deploying the application, and configuring the application;

the computer system storing the sets of APIs in a configuration management database (CMDB); and

the computer system generating and storing rules in the CMDB, so that each rule indicates conditions under which a corresponding set of APIs is executed to deploy the service on the corresponding CSP,

wherein the steps of disabling the first API and activating the second API are based on the rules stored in the CMDB.

9. The computer program product of claim 7, wherein the method further comprises the steps of:

the computer system receiving sets of APIs for respective SPs which are respective cloud service providers (CSPs), each of the received sets of APIs indicating mechanisms to deploy a service on a corresponding CSP included in the respective CSPs;

the computer system generating and storing rules in a configuration management database (CMDB), so that each rule indicates conditions under which a corresponding set of APIs is executed to deploy the service on the corresponding CSP;

the computer system obtaining a subscription to a service that sends a notification of changes to the sets of APIs;

based on the subscription, the computer system receiving a notification of a change to a set of APIs specified by a rule stored in the CMDB; and

in response to the step of receiving the notification, the computer system updating the rule in the CMDB based on the change to the set of APIs.

10. The computer program product of claim 7, wherein the method further comprises the steps of:

the computer system receiving first, second, and third information about the first service provided by the first SP which is a first cloud service provider (CSP), the second service provided by the second SP which is a second CSP, and the a third service provided by a third SP which is a third CSP, respectively, wherein the first, second, and third information includes geographic attributes of the first, second, and third CSPs, respectively;

the computer system determining that the second and third services provide the functionality of the application;

the computer system determining a threshold for a latency of the application;

based on the geographic attributes in the second information, the computer system determining that redeploying the application to the second CSP results in a first latency of the application;

based on the geographic attributes in the third information, the computer system determining that redeploying the application to the third CSP results in a second latency of the application;

the computer system determining that the first latency does not exceed the threshold and the second latency exceeds the threshold; and

based on the second service providing the functionality of the application, the first latency not exceeding the threshold, and the second latency exceeding the threshold, the computer system redeploying the application to the second CSP and not to the third CSP.

11. The computer program product of claim 7, wherein the step of detecting the fail condition includes detecting an outage of an entire data center provided by the first SP which is a cloud service provider, the outage of the entire data center causing the outage of the first service.

12. A computer system comprising:

a central processing unit (CPU);

a memory coupled to the CPU; and

a computer readable storage device coupled to the CPU, the storage device containing instructions that are executed by the CPU via the memory to implement a method of managing resiliency of an application provided by a first service provider (SP), the method comprising the steps of;

the computer system detecting a fail condition of the first SP, which indicates an outage of a first service provided by the first SP;

in response to the step of detecting the fail condition and based on a topology which maps the first SP to a second SP and maps the first service to a second service provided by the second SP, the computer system determining that a first application programming interface (API) provided by the first SP had provided the first service prior to the fail condition and that a second API provided by the second SP provides the second service;

based on the first API having provided the first service and the second API providing the second service, the computer system disabling the first API provided by the first SP and activating the second API provided by the second SP, so that a functionality of the application that had been provided by the first service prior to the fail condition being detected continues by being provided by the second API even though the first SP is experiencing the fail condition;

the computer system receiving information specifying the first and second services;

the computer system receiving other information specifying the application and infrastructure components of the first and second SPs, which are cloud service providers; and

based on the information specifying the first and second services and the other information specifying the application and the infrastructure components, the computer system generating the topology.

13. The computer system of claim 12, wherein the method further comprises the steps of:

the computer system receiving sets of APIs for respective portals of corresponding SPs which are corresponding cloud service providers (CSPs), each of the received sets of APIs indicating mechanisms to deploy a service on the corresponding CSP, the mechanisms including at least one of deploying a virtual machine, configuring the virtual machine, deploying a network, configuring the network, deploying middleware, configuring the middleware, deploying the application, and configuring the application;

the computer system storing the sets of APIs in a configuration management database (CMDB); and

the computer system generating and storing rules in the CMDB, so that each rule indicates conditions under which a corresponding set of APIs is executed to deploy the service on the corresponding CSP,

wherein the steps of disabling the first API and activating the second API are based on the rules stored in the CMDB.

14. The computer system of claim 12, wherein the method further comprises the steps of:

the computer system receiving sets of APIs for respective SPs which are respective cloud service providers (CSPs), each of the received sets of APIs indicating mechanisms to deploy a service on a corresponding CSP included in the respective CSPs;

the computer system generating and storing rules in a configuration management database (CMDB), so that each rule indicates conditions under which a corresponding set of APIs is executed to deploy the service on the corresponding CSP;

the computer system obtaining a subscription to a service that sends a notification of changes to the sets of APIs;

based on the subscription, the computer system receiving a notification of a change to a set of APIs specified by a rule stored in the CMDB; and

in response to the step of receiving the notification, the computer system updating the rule in the CMDB based on the change to the set of APIs.

15. The computer system of claim 12, wherein the method further comprises the steps of:

the computer system receiving first, second, and third information about the first service provided by the first SP which is a first cloud service provider (CSP), the second service provided by the second SP which is a second CSP, and the a third service provided by a third SP which is a third CSP, respectively, wherein the first, second, and third information includes geographic attributes of the first, second, and third CSPs, respectively;

the computer system determining that the second and third services provide the functionality of the application;

the computer system determining a threshold for a latency of the application;

based on the geographic attributes in the second information, the computer system determining that redeploying the application to the second CSP results in a first latency of the application;

based on the geographic attributes in the third information, the computer system determining that redeploying the application to the third CSP results in a second latency of the application;

the computer system determining that the first latency does not exceed the threshold and the second latency exceeds the threshold; and

based on the second service providing the functionality of the application, the first latency not exceeding the threshold, and the second latency exceeding the threshold, the computer system redeploying the application to the second CSP and not to the third CSP.

16. The computer system of claim 12, wherein the step of detecting the fail condition includes detecting an outage of an entire data center provided by the first SP which is a first cloud service provider (CSP), the outage of the entire data center causing the outage of the first service.