chaostoolkit | Chaos Engineering Toolkit & Orchestration for Developers | Automation library

by chaostoolkit Python Version: 1.19.0 License: Apache-2.0

X-Ray Key Features Code Snippets(3)Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | chaostoolkit Summary

chaostoolkit is a Python library typically used in Automation applications. chaostoolkit has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has medium support. You can install using 'pip install chaostoolkit' or download it from GitHub, PyPI.

Chaos Engineering Experiments Automation & Orchestration

Support

Quality

Security

License

Reuse

Support

chaostoolkit has a medium active ecosystem.

It has 1729 star(s) with 179 fork(s). There are 41 watchers for this library.

There were 3 major release(s) in the last 6 months.

There are 6 open issues and 159 have been closed. On average issues are closed in 305 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of chaostoolkit is 1.19.0

Quality

chaostoolkit has 0 bugs and 0 code smells.

Security

chaostoolkit has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

chaostoolkit code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

chaostoolkit is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

chaostoolkit releases are available to install and integrate.

Deployable package is available in PyPI.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed chaostoolkit and discovered the below as its top functions. This is intended to give you an instant insight into chaostoolkit implemented functionality, and help decide if they suit your requirements.

Command line tool
Configure a logger
Check if a new command is newer
Run an experiment
Check if the hypothesis strategy is valid
Get the version from the package

Get all kandi verified functions for this library.

chaostoolkit Key Features

No Key Features are available at this moment for chaostoolkit.

chaostoolkit Examples and Code Snippets

chaostoolkit-gremlin,Usage

Python

Lines of Code : 60

License : Permissive (Apache-2.0)

Copy

{
    "secrets": {
        "gremlin": {
            "email": {
                "type": "env",
                "key": "GREMLIN_EMAIL"
            },
            "password": {
                "type": "env",
                "key": "GREMLIN_PWD"

Kubernetes CRD/operator for running Chaos Toolkit experiments on-demand,Run Chaos Toolkit experiment

Python

Lines of Code : 40

License : Permissive (Apache-2.0)

Copy

---
apiVersion: v1
kind: ConfigMap
metadata:
  name: chaostoolkit-experiment
  namespace: chaostoolkit-run
data:
  experiment.json: |
    {
        "title": "...",
    }
---
apiVersion: chaostoolkit.org/v1
kind: ChaosToolkitExperiment
metadata:
  nam

Chaos Toolkit Driver for Toxiproxy,Usage,Proxy actions

Python

Lines of Code : 34

License : Permissive (Apache-2.0)

Copy

 "method": [
      {
            "type": "action",
            "name": "setup_toxiproxy_proxy",
            "provider": {
                "type": "python",
                "module": "chaostoxi.proxy.actions",
                "func": "create_proxy",

Community Discussions

Trending Discussions on chaostoolkit

Chaostoolkit experiment failing when run as a Job from within a k8s cluster

QUESTION

Chaostoolkit experiment failing when run as a Job from within a k8s cluster

Asked 2022-Feb-04 at 05:29

I am using chaostoolkit and am able to run a chaos experiment successfully from command line. However, when i try to run the same as a job in k8s it is throwing up 'connection refused' error. What I find it strange is that at times the steady state hypothesis step runs successfully and returns 200 OK while failing in the terminate pod action, but a lot of times it is also failing at the hypothesis step itself (before the action to terminate pod). I am doing this in Google cloud by the way.

During some runs i see that the hypothesis before action as well as the termination pod are successful but the hypothesis after action (termination) gets 'connection refused' error.

Any help/tip is appreciated.

Here is the error msg:

...

ANSWER

Answered 2022-Feb-04 at 05:29

After struggling for over a day, I tried reinstalling Istio and it started working fine. Must be something wrong with Istio then.

Source https://stackoverflow.com/questions/70967630

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install chaostoolkit

Generally speaking, you can install it as follows:. It is recommended that you create a Python virtual environment for running your chaos experiments. Full instructions for installing chaostoolkit and its requirements are available in the installation documentation.
While installing via packages gives you the most control over what to deploy, you may also be interested in simply dowloading a standalone binary that can be run as-is.
Once you have installed the Chaos Toolkit you can use it through its simple command line tool. The tool's main job is to run your experiment and then generate a report of the findings from the experiment to then share with your team for discussion.

Support

Contributors to this project are welcome as this is an open-source effort that seeks discussions and continuous improvement. From a code perspective, if you wish to contribute, you will need to run a Python 3.5+ environment. Then, fork this repository and submit a PR. The project cares for code readability and checks the code style to match best practices defined in PEP8. Please also make sure you provide tests whenever you submit a PR so we keep the code reliable. The Chaos Toolkit projects require all contributors must sign a Developer Certificate of Origin 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.

Find more information at: