assert-kth/royal-chaos

Chaos engineering systems invented at KTH Royal Institute of Technology.

Royal Chaos

This repository contains the chaos engineering systems invented at KTH Royal Institute of Technology. Every tool is organized in a separate folder in this repo, with a detailed README file inside.

ChaosMachine

ChaosMachine is a tool to do chaos engineering at the application level in the JVM. It concentrates on analyzing the error-handling capability of each try-catch block involved in the application by injecting exceptions.

• Code: chaosmachine
• Paper: [TSE] A Chaos Engineering System for Live Analysis and Falsification of Exception-handling in the JVM (Long Zhang, Brice Morin, Philipp Haller, Benoit Baudry and Martin Monperrus)

TripleAgent

TripleAgent is a system for fault injection for Java applications. The unique feature of this system is to combine automated monitoring and automated perturbation injection. It outputs concrete hints to improve the resilience against unhandled exceptions.

• Code: tripleagent
• Paper: [ISSRE] TripleAgent: Monitoring, Perturbation and Failure-obliviousness for Automated Resilience Improvement in Java Applications (Long Zhang and Martin Monperrus)

Chaos-NS-3

We seek to attain a simplified illustration about chaos engineering applied on a simulated Netflix environment in ns-3 with the intention to provide some enlightenment for the principles of chaos engineering and in addition to this we will also present a suggestion about how to infer an unknown system as a possible application, derived from the knowledges acquired from our chaos journey.

• Code: chaos-ns-3
• Paper: Simulation of Chaos Engineering for Internet-scale Software with NS-3 (Zubayer Anton, Luong Tai)

ChaosOrca

ChaosOrca is a tool for doing Chaos Engineering on containers by perturbing system calls for processes inside containers. Where monitoring/observability is a key part of the system to be able to reason about the given perturbations effect on the container. The system utilises strace built in system call fault injections, as such it can add delays, return error codes, do so intermittenly and more. Metrics recorded are System calls, HTTP, Logs and Performance related ones.

• Code: chaosorca
• Paper: [FGCS] Observability and Chaos Engineering on System Calls for Containerized Applications in Docker (Jesper Simonsson, Long Zhang, Brice Morin, Benoit Baudry and Martin Monperrus)

POBS

POBS is an approach that automatically augments Docker images to have improved observability and fault injection capabilities for Java applications.

• Code: pobs
• Paper: Automatic Observability for Dockerized Java Applications (Long Zhang, Deepika Tiwari, Brice Morin, Benoit Baudry, Martin Monperrus)

Phoebe

Phoebe is a fault injection framework for reliability analysis with respect to system call invocation errors. First, Phoebe enables developers to have full observability of system call invocations. Second, Phoebe generates error models that are realistic in the sense that they resemble errors that naturally happen in production. With the generated error models, Phoebe automatically conducts a series of experiments to systematically assess the reliability of applications with respect to system call invocation errors in production.

• Code: phoebe
• Paper: [TDSC] Maximizing Error Injection Realism for Chaos Engineering with System Calls (Long Zhang, Brice Morin, Benoit Baudry and Martin Monperrus)

ChaosETH

ChaosETH is a chaos engineering framework that intercepts an Ethereum client's system call invocations and actively injects error codes into these system call invocations in production. The source code of the Ethereum client is not necessary. Developers can also apply various workload or directly use production traffic to conduct chaos engineering experiments at the system call invocation level.

• Code: chaoseth
• Paper: Chaos Engineering of Ethereum Blockchain Clients (Long Zhang, Javier Ron, Benoit Baudry and Martin Monperrus)

royal-chaos's Issues

The path to the dockerfiles may be incorrect

Hi @Deee92 , I just find that some of the Dockerfile paths may be incorrect. Take the following one as an example (line 505-574 in output_1570903438.json):

"path": "./questionanswering/OpenEphyra/Dockerfile"

should be ./lucida/questionanswering/OpenEphyra/Dockerfile.

Could you please fix this and upload a new data set? Thanks!

  {
    "current_timestamp": 1570903645,
    "name": "lucida",
    "full_name": "claritylab/lucida",
    "fork": false,
    "clone_url": "https://github.com/claritylab/lucida.git",
    "stargazers_count": 4863,
    "language": "Java",
    "number_of_dockerfiles": 6,
    "info_from_dockerfiles": [
      {
        "path": "./Dockerfile",
        "base_images": [
          "FROM ubuntu:14.04"
        ],
        "cmds": [],
        "entrypoints": [],
        "args": []
      },
      {
        "path": "./tools/Dockerfile",
        "base_images": [
          "FROM ubuntu:14.04"
        ],
        "cmds": [],
        "entrypoints": [],
        "args": []
      },
      {
        "path": "./questionanswering/OpenEphyra/Dockerfile",
        "base_images": [
          "FROM lucida_base"
        ],
        "cmds": [],
        "entrypoints": [],
        "args": []
      },
      {
        "path": "./speechrecognition/kaldi_gstreamer_asr/Dockerfile",
        "base_images": [
          "FROM lucida_base"
        ],
        "cmds": [],
        "entrypoints": [],
        "args": []
      },
      {
        "path": "./commandcenter/Dockerfile",
        "base_images": [
          "FROM lucida_base"
        ],
        "cmds": [],
        "entrypoints": [],
        "args": []
      },
      {
        "path": "./imagematching/opencv_imm/Dockerfile",
        "base_images": [
          "FROM lucida_base"
        ],
        "cmds": [],
        "entrypoints": [],
        "args": []
      }
    ],
    "build_tools": [
      "Ant",
      "Gradle"
    ]
  }

Annotation Processor Error

When trying to implement the Annotation Processor in our code, a syntax error is shown stating that the annotation is "disallowed for this location". It does not matter if the annotation is written in the correct location or some other random location in the code, the error appears every time.

c# support

Is there any possibility to use the tool for c# code as well ?

Which open source licence is this project under?

I am considering to use this project, but we are just allowed to just use licenses that allow closing parts of the code later if we need/want. Like Apache 2.0, LGPL, MIT, and others.
Is the project under an open-source license yet?

new ideas for TripleAgent