Forecasting future states of a multi-active cloud system

• US 9,424,525 B1
• Filed: 11/18/2015
• Issued: 08/23/2016
• Est. Priority Date: 11/18/2015
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Byrne, Alan, Lloyd, Jason, Penrose, Andrew T.
• Primary Examiner(s): CHEN, ALAN S
• Application Number:
  US14/944,255
• Time in Patent Office: 279 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 11/00 Error detection; Error correction; Monitoring error detection, correction or monitoring in information storage based on relative movement between record carrier and transducer G11B20/18; monitoring, i.e. supervising the progress of recording or reproducing G11B27/36; in static stores G11C29/00
• CPC Class Codes: G06F 11/008 Reliability or availability analysis
• CPC Class Codes: G06F 11/2294 by remote test
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3696 Methods or tools to render software testable
• CPC Class Codes: G06N 7/01 Probabilistic graphical models, e.g. probabilistic networks
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks

Abstract

An embodiment of the invention may include a method, computer program product and computer system for forecasting future states of a multi-active cloud. The method, computer program product and computer system may include a computing device that determines the operating state of the passive server. The operating state of the passive server is one or more of a deploying state and a smoke testing state. The computing device may determine the probability of the operating state successfully completing. The computing device may delay the second asynchronous workflow until the operating state successfully completes based on the probability of the operating state successfully completing exceeding a predetermined value.

Claims

1. A method of managing two asynchronous workflows in a computer system having at least an active server and a passive server, a first asynchronous workflow being for deployment of a code upgrade on said passive server, a second asynchronous workflow being for testing on said active server, the method comprising:

determining the operating state of the passive server, wherein the operating state of the passive server comprises one or more of a deploying state and a smoke testing state;

determining the probability of the operating state successfully completing, wherein determining the probability of the deploying state successfully completing comprises;

identifying a state rating associated with the current state of the passive server;

identifying a weighted rating associated with the passive server;

identifying a deployment success probability rating associated with the passive server; and

determining the probability of the deploying state successfully completing based on the state rating, the weighted rating and the deployment success probability;

based on the probability of the operating state successfully completing exceeding a predetermined value, performing the second asynchronous workflow after the operating state successfully completes.

2. The method of claim 1, wherein determining the probability of the smoke testing state successfully completing comprises:

identifying a state rating associated with the current state of the smoke test;

identifying a weighted rating associated with the smoke test;

identifying a deployment success probability rating associated with the smoke test; and

determining the probability of the smoke testing state successfully completing based on the state rating, the weighted rating and the deployment success probability.

3. The method of claim 2, wherein determining the probability of the smoke testing state successfully completing based on the state rating, the weighted rating and the deployment success probability comprises averaging the state rating, the weighted rating and the deployment success.

4. The method of claim 3, wherein delaying the second asynchronous workflow until the operating state successfully completes comprises determining if the probability of the operating state successfully completing is below a threshold value.

5. The method of claim 1, further comprising determining whether the passive server is in an available state and based on a determination that the passive server is in an available state executing the second asynchronous workflow.

6. The method of claim 1, further comprising determining whether the passive server is in a flipping state and based on a determination that the passive server is in a flipping state delaying the second asynchronous workflow.

7. A computer program product of managing two asynchronous workflows in a computer system having at least an active server and a passive server, a first asynchronous workflow being for deployment of a code upgrade on said passive server, a second asynchronous workflow being for testing on said active server, the computer program product comprising:

one or more computer-readable storage devices and program instructions stored on at least one of the one or more tangible storage devices, the program instructions comprising;

program instructions to determine the operating state of the passive server, wherein the operating state of the passive server comprises one or more of a deploying state and a smoke testing state;

program instructions to determine the probability of the operating state successfully completing, wherein the program instructions to determine the probability of the deploying state successfully completing comprises;

program instructions to identify a state rating associated with the current state of the passive server;

program instructions to identify a weighted rating associated with the passive server;

program instructions to identify a deployment success probability rating associated with the passive server; and

program instructions to determine the probability of the deploying state successfully completing based on the state rating, the weighted rating and the deployment success probability;

based on the probability of the operating state successfully completing exceeding a predetermined value, program instructions to perform the second asynchronous workflow after the operating state successfully completes.

8. The computer program product of claim 7, wherein determining the probability of the smoke testing state successfully completing comprises:

program instructions to identify a state rating associated with the current state of the smoke test;

program instructions to identify a weighted rating associated with the smoke test;

program instructions to identify a deployment success probability rating associated with the smoke test; and

program instructions to determine the probability of the smoke testing state successfully completing based on the state rating, the weighted rating and the deployment success probability.

9. The computer program product of claim 8, wherein determining the probability of the smoke testing state successfully completing based on the state rating, the weighted rating and the deployment success probability comprises averaging the state rating, the weighted rating and the deployment success.

10. The computer program product of claim 9, wherein the program instructions to delay the second asynchronous workflow until the operating state successfully completes comprises program instructions to determine if the probability of the operating state successfully completing is below a threshold value.

11. The computer program product of claim 7, further comprising program instructions to determine whether the passive server is in an available state and based on a determination that the passive server is in an available state executing the second asynchronous workflow.

12. The computer program product of claim 7, further comprising program instructions to determine whether the passive server is in a flipping state and based on a determination that the passive server is in a flipping state delaying the second asynchronous workflow.

13. A computer system for of managing two asynchronous workflows in a computer system having at least an active server and a passive server, a first asynchronous workflow being for deployment of a code upgrade on said passive server, a second asynchronous workflow being for testing on said active server, the computer system comprising:

one or more processors, one or more computer-readable memories, one or more computer-readable tangible storage devices, and program instructions stored on at least one of the one or more storage devices for execution by at least one of the one or more processors via at least one of the one or more memories, the program instructions comprising;

program instructions to determine the operating state of the passive server, wherein the operating state of the passive server comprises one or more of a deploying state and a smoke testing state;

program instructions to determine the probability of the operating state successfully completing, wherein the program instructions to determine the probability of the deploying state successfully completing comprises;

program instructions to identify a state rating associated with the current state of the passive server;

program instructions to identify a weighted rating associated with the passive server;

program instructions to identify a deployment success probability rating associated with the passive server; and

program instructions to determine the probability of the deploying state successfully completing based on the state rating, the weighted rating and the deployment success probability;

based on the probability of the operating state successfully completing exceeding a predetermined value, program instructions to perform the second asynchronous workflow after the operating state successfully completes.

14. The computer system of claim 13, wherein determining the probability of the smoke testing state successfully completing comprises:

program instructions to identify a state rating associated with the current state of the smoke test;

program instructions to identify a weighted rating associated with the smoke test;

program instructions to identify a deployment success probability rating associated with the smoke test; and

program instructions to determine the probability of the smoke testing state successfully completing based on the state rating, the weighted rating and the deployment success probability.

15. The computer system of claim 14, wherein determining the probability of the smoke testing state successfully completing based on the state rating, the weighted rating and the deployment success probability comprises averaging the state rating, the weighted rating and the deployment success.

16. The computer system of claim 13, further comprising program instructions to determine whether the passive server is in an available state and based on a determination that the passive server is in an available state executing the second asynchronous workflow.

17. The computer system of claim 13, further comprising program instructions to determine whether the passive server is in a flipping state and based on a determination that the passive server is in a flipping state delaying the second asynchronous workflow.