title | layout | filename |
---|---|---|
Home |
template |
index |
LitmusChaos is a toolset to do cloud-native chaos engineering. It takes a cloud-native approach to create, manage and monitor chaos. Chaos is orchestrated using the Kubernetes Custom Resource Definitions (CRDs) which are called ChaosEngine, ChaosExperiment and ChaosResult. For a higher performance we need these components to work accurately according to our hypothesis between every upgrade and updates which brings the need of LitmusChaos E2E.
The Litmus E2E is broadly divided in three categories Generic, OpenEBS. LitmusPortal managed by respective branch in litmus-e2e repository.
Branch | Description |
---|---|
generic | It contains the test cases (GO BDDs) for all litmus generic experiments along with litmus component tests. |
openebs | It contains the test cases (GO BDDs) for Litmus OpenEBS experiment which includes different OpenEBS control plane and data plane tests. |
litmus-portal | It contains different test cases for litmus portal |
To view the details of the last few pipelines runs:
- Select the buttons from header whose pipeline details you want.
- Inside it contains the details of every job along with pipeline details.
The Generic pipeline covers the test for litmus generic experiments which include some before and after chaos validation checks and performance checks for different litmus components. A sample application nginx is deployed along with nginx service and liveness probe to test the chaos.
Stages | Description |
---|---|
Setup | This stage is used for connecting to the OnPrem cluster which is a 4 node cluster(1 master and 3 worker) and clone the litmus-e2e folder |
Install | This is the Litmus installation stage, in this stage the crds rbacs and the operator are created. |
Deploy | This is the application deployment stage. The application under chaos is deployed and the liveness test for the application is also performed in this stage. |
Generic-experiment | This stage includes the creation of experiments and some positive & negative test cases for the experiments. |
Infra-experiment | This stage includes the creation of node level experiments and some positive & negative test cases for the Infra experiments. |
App-cleanup | This is the experiment and application cleanup stage on which all the engines, applications, experiments are removed. |
Cleanup | In this stage, the litmus repo is removed and cluster gets disconnected. |
It contains the openebs e2e BDDs for OpenEBS experiments. A stateful application (percona) is deployed using cstor (OpenEBS Storage class). The chaos is performed on the different OpenEBS components with the same application.At the end, the application, litmus, and OpenEBS all are uninstalled gracefully.
Stages | Description |
---|---|
Setup | This stage is used for connecting to the OnPrem cluster which is a 4 node cluster(1 master and 3 worker) and clone the litmus-e2e folder |
Infra setup | It contains the three jobs Build Litmus which is used to install Litmus, Build OpenEBS which is used to install openebs, App-deploy It is used to deploy application using openebs. |
Application setup | In this stage a sample stateful percona application is deployed which will be used to test the openebs experiments |
Experiment | This stage includes the creation of Chaos Experiments, Engine for the experiments and test cases (BDDs)for the experiments. |
Infra Cleanup | This stage include the set of jobs which will remove litmus,openebs and deployed application. |
Application cleanup | In this stage a sample stateful percona application is removed after chaos |
Cleanup | In this stage, the litmus-e2e repo is removed and cluster gets disconnected. |
It contains the test cases for litmus portal. Currently, it contains cypress test for testing the login and workflow UI.
Stages | Description |
---|---|
Setup | This stage is used for connecting to the OnPrem cluster which is a 4 node cluster(1 master and 3 worker) and clone the litmus-e2e folder |
Cypress tests | This stage deals with the cypress test for litmuschaos |
Cleanup | In this stage, the litmus-e2e repo is removed and cluster gets disconnected. |