Home - Pranav-SA/thesis-support-examples GitHub Wiki

Welcome to the chaos-research wiki!


Guidelines

We covered several tools and scenarios such as litmus, chaos mesh, chaos toolkit, fis, along with several low-level tools such as forkcomb, k6, toxi proxy, stressng, and even bpf linux. We highlight the ones with potential utility for us in this wiki. A complete comparison can also be found in Tools Research section.

Note: Several experiment examples are depicted with the chaos toolkit as a base due to the following reasons:

  • It provides extensibility through the means of different associated drivers along with its core functionalities.

  • Heavily used in SAP in various forms by different teams.

  • It is easily accessible using the command line utility, supporting automation and scheduling.

Selection

In conclusion, we opt for the chaos toolkit for high customizability and extensive support. We also cover AWS FIS because of easy integration with our AWS Native Stack.
Recently, AWS FIS added support for Litmus and Chaos Mesh as an EKS Action Provider. Thus we cover Litmus, and Chaos Mesh briefly. Find more here. Proposal covers the selection stack.

Contents of Wiki

  1. Activity Framework: Describes the activity framework designed for a smooth start of Chaos Engineering using different reference literature.

  2. AWS Native Tooling: This page includes brief information about AWS FIS with relevant links to the up-to-date documentation.

  3. Chaos Mesh: We describe Chaos Mesh in brief as it is offered as an action with AWS FIS EKS actions.

  4. Chaos Toolkit: This page covers the basic concepts of Chaos Toolkit. We also cover some sample experiments with sample applications used to test Chaos Toolkit in the Dev Test environment. This page serves as a good starting point.

  5. Cluster Setup: On this page, we describe cluster setup instructions for different offerings.

  6. Litmus Chaos: We describe Litmus in brief as it is offered as an action with AWS FIS EKS actions.

  7. Observability: This page describe some of the metrics used for the observation of the long-term impact of Chaos Engineering. We also cover how to use open-source tools for observability with your testing clusters.

  8. Principles and Use Cases: Chaos Engineering Community has provided some guidelines which are described on this page.

  9. Proposal: The outlook of the GameDay Tools usable with Concur T2 has been described as Proposed Solution Stack.

  10. Reporting: We can ship our Chaos Results as reports with Chaos Toolkit. We Describe the process on this wiki page.



This Wiki has been authored by Pranav Shankar as part of the Master Thesis on Chaos Engineering at SAP Concur

⚠️ **GitHub.com Fallback** ⚠️