Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/chaostoolkit/chaostoolkit
Chaos Engineering Toolkit & Orchestration for Developers
https://github.com/chaostoolkit/chaostoolkit
automation chaos-engineering chaostoolkit devops-tools reliability reliability-engineering resiliency sre
Last synced: 4 days ago
JSON representation
Chaos Engineering Toolkit & Orchestration for Developers
- Host: GitHub
- URL: https://github.com/chaostoolkit/chaostoolkit
- Owner: chaostoolkit
- License: apache-2.0
- Created: 2017-09-24T15:49:05.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2024-07-20T16:58:33.000Z (6 months ago)
- Last Synced: 2025-01-14T19:23:41.280Z (11 days ago)
- Topics: automation, chaos-engineering, chaostoolkit, devops-tools, reliability, reliability-engineering, resiliency, sre
- Language: Python
- Homepage: https://chaostoolkit.org
- Size: 1.04 MB
- Stars: 1,898
- Watchers: 45
- Forks: 186
- Open Issues: 10
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Roadmap: ROADMAP.md
Awesome Lists containing this project
- awesome-github-repos - chaostoolkit/chaostoolkit - Chaos Engineering Toolkit & Orchestration for Developers (Python)
- awesome-repositories - chaostoolkit/chaostoolkit - Chaos Engineering Toolkit & Orchestration for Developers (Python)
- awesome-chaos-engineering - Chaos Toolkit - A chaos engineering toolkit to help you build confidence in your software system. (3. Fault Injection / Generic Tools)
- awesome-failure-diagnosis - Chaos Toolkit
README
Chaos Toolkit - Chaos Engineering for All Engineers
Community •
Installation •
Tutorials •
Reference •
ChangeLog
---
# Chaos Toolkit - Chaos Engineering for All Engineers
The Chaos Toolkit, or as we love to call it “ctk”, is a simple
CLI-driven tool who helps you write and run Chaos Engineering experiment. It
supports any target platform you can think of through
[existing extensions](https://chaostoolkit.org/drivers/overview/) or
the ones you write as you need.
Chaos Toolkit is versatile and works really well in settings where other Chaos
Engineering tools may not fit: cloud environments, datacenters, CI/CD, etc.
## Install or Upgrade
Provided you have Python 3.8+ installed, you can install it as follows:
```console
$ pip install -U chaostoolkit
```
## Getting Started
Once you have installed the Chaos Toolkit you can use it through its simple command line tool.
Running an experiment is as simple as:
```console
$ chaos run experiment.json
```
## Get involved!
Chaos Toolkit's mission is to provide an open API to chaos engineering in all its forms. As such, we encourage and welcome you to [join][join] our open community Slack team to discuss and share your experiments and needs with the community.
You can also use [StackOverflow][so] to ask any questions regarding using the
Chaos Toolkit or Chaos Engineering.
[join]: https://join.slack.com/t/chaostoolkit/shared_invite/zt-22c5isqi9-3YjYzucVTNFFVIG~Kzns8g
[so]: https://stackoverflow.com/questions/ask?tags=chaostoolkit+chaosengineering
If you'd prefer not to use Slack then we welcome the raising of GitHub issues on this repo for any questions, requests, or discussions around the Chaos Toolkit.
Finally you can always email `[email protected]` with any questions as well.
## Contribute
Contributors to this project are welcome as this is an open-source effort that
seeks [discussions][join] and continuous improvement.
From a code perspective, if you wish to contribute, you will need to run a
Python 3.8+ environment. Please, fork this project, write unit tests to cover
the proposed changes, implement the changes, ensure they meet the formatting
standards set out by `ruff`, add an entry into
`CHANGELOG.md`, and then raise a PR to the repository for review
The project is driven by [PDM][pdm], so install it and you can run the
following commands:
[pdm]: https://pdm-project.org/latest/
```console
$ pdm install
$ pdm run test
$ pdm run format
$ pdm run lint
```
The Chaos Toolkit projects require all contributors must sign a
[Developer Certificate of Origin][dco] on each commit they would like to merge
into the master branch of the repository. Please, make sure you can abide by
the rules of the DCO before submitting a PR.
[dco]: https://github.com/probot/dco#how-it-works
