Resilience as a Service
US-2016371134-A1 · Dec 22, 2016 · US
US9753826B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9753826-B2 |
| Application number | US-201514804528-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 21, 2015 |
| Priority date | Jul 21, 2015 |
| Publication date | Sep 5, 2017 |
| Grant date | Sep 5, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Methods, systems, and computer program products for providing fault injection to Cloud-provisioned machines are provided herein. A method includes determining one or more fault conditions to be associated with a fault injection implementation based on one or more parameters associated with a request for the fault injection implementation; generating a specification for a lifecycle of the fault injection implementation based on the one or more fault conditions; and executing the fault injection implementation in a target system, wherein said executing comprises effecting the lifecycle of the fault injection implementation according to the generated specification.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: determining one or more fault conditions to be associated with a fault injection implementation based on one or more parameters associated with a request for the fault injection implementation, wherein said determining is carried out automatically by a decision-making component executing on a hardware processor, and wherein said determining the one or more fault conditions to be associated with the fault injection implementation comprises ranking multiple fault conditions based on one or more variables; generating a specification for a lifecycle of the fault injection implementation based on the one or more fault conditions, wherein said generating is carried out automatically by a fault injection specification component executing on the hardware processor and communicatively linked to the decision-making component; and executing the fault injection implementation in a target system, wherein said executing comprises effecting the lifecycle of the fault injection implementation according to the generated specification, and wherein said executing is carried out automatically by a fault injection execution component executing on the hardware processor and communicatively linked to the decision-making component and the fault injection specification component. 2. The method of claim 1 , wherein the one or more fault conditions comprises fault type. 3. The method of claim 1 , wherein the one or more fault conditions comprises fault occasion. 4. The method of claim 1 , wherein the one or more fault conditions comprises fault location. 5. The method of claim 1 , wherein the one or more fault conditions comprises target system workload. 6. The method of claim 1 , wherein the one or more parameters associated with the request comprise identification of the target system. 7. The method of claim 1 , wherein said determining further comprises determining the one or more fault conditions to be associated with the fault injection implementation based on feedback provided by an individual issuing the request. 8. The method of claim 1 , wherein said determining further comprises determining the one or more fault conditions to be associated with the fault injection implementation based on input provided by a knowledge based system. 9. The method of claim 1 , wherein said determining further comprises determining the one or more fault conditions to be associated with the fault injection implementation based on input provided by an error detection system. 10. The method of claim 1 , wherein said determining further comprises determining the one or more fault conditions to be associated with the fault injection implementation based on input provided by a cloud monitoring system. 11. The method of claim 1 , wherein the one or more variables comprises a likelihood of each of the multiple fault conditions causing the target system to fail. 12. The method of claim 1 , wherein the one or more variables comprises severity of failures caused by each of the multiple fault conditions. 13. The method of claim 1 , wherein the one or more variables comprises a frequency of usage of each of the multiple fault conditions in systems analogous to the target system. 14. The method of claim 1 , wherein the one or more variables comprises a frequency of past usage of each of the multiple fault conditions in the target system. 15. The method of claim 1 , wherein at least one of (i) said determining, (ii) said generating, and (iii) said executing is a cloud-based service. 16. The method of claim 1 , comprising: monitoring one or more predetermined items of data during the fault injection implementation in the target system. 17. The method of claim 16 , comprising: outputting the one or more predetermined items of data monitored during the fault injection implementation to a database. 18. A computer program product, the computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a computing device to cause the computing device to: determine one or more fault conditions to be associated with a fault injection implementation based on one or more parameters associated with a request for the fault injection implementation, wherein said determining the one or more fault conditions to be associated with the fault injection implementation comprises ranking multiple fault conditions based on one or more variables; generate a specification for a lifecycle of the fault injection implementation based on the one or more fault conditions; and execute the fault injection implementation in a target system, wherein said executing comprises effecting the lifecycle of the fault injection implementation according to the generated specification. 19. A system comprising: a memory; and at least one processor coupled to the memory and configured for: determining one or more fault conditions to be associated with a fault injection implementation based on one or more parameters associated with a request for the fault injection implementation, wherein said determining the one or more fault conditions to be associated with the fault injection implementation comprises ranking multiple fault conditions based on one or more variables; generating a specification for a lifecycle of the fault injection implementation based on the one or more fault conditions; and executing the fault injection implementation in a target system, wherein said executing comprises effecting the lifecycle of the fault injection implementation according to the generated specification.
Workload generation, e.g. scripts, playback · CPC title
Generation of test inputs, e.g. test vectors, patterns or sequences {; with adaptation of the tested hardware for testability with external testers} · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.