Surviving Chaos
  • Surviving Chaos
  • A Brief Intoduction to Chaos
    • Principles of Chaos
    • Kinds of Failure
    • Goals and Non-goals
  • Infrastructure Familiarization
    • Service Resilience
    • Monitoring and Logging
    • Generating Work & Data
  • Assembling Your Kit
    • Using a Cloud Node
    • Using a Private Node
  • A Menagerie of Tools
    • 1000 Ways to Die (`kill`)
    • Failing the Network (`ip`)
    • Controlling Traffic (`tc`)
    • Isolating and Parititioning (`iptables`)
    • A Fuzzy Schedule (`nmz`)
    • A Disfunctional Docker (`pumba`)
  • Failure as a Feature
  • Continous Chaos (CI/CD)
    • Example: Schrödinger
  • Resources / References
Powered by GitBook
On this page
  1. Continous Chaos (CI/CD)

Example: Schrödinger

PreviousContinous Chaos (CI/CD)NextResources / References

Last updated 6 years ago

At PingCAP we have a system called Schrödinger which we use for our Chaos Testing.

It has a web UI for configuration, here you can see our dashboard of current tests:

Here you can see the interface for creating the cases:

We refer to particular checkouts to be tested as 'cats':

Managing resources and cases: