Surviving Chaos
CtrlK
  • 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

Resources / References

  • Pillars of Chaos: https://principlesofchaos.org/

  • Byzantine Failure: https://blog.cdemi.io/byzantine-fault-tolerance/

  • Watchdogs: http://0pointer.de/blog/projects/watchdog.html

  • Socket Activation: http://0pointer.de/blog/projects/socket-activation.html

  • ip reference: https://access.redhat.com/sites/default/files/attachments/rh_ip_command_cheatsheet_1214_jcs_print.pdf

  • A Stack Overflow discussion with some reccomendations around Network testing: https://stackoverflow.com/questions/614795/simulate-delayed-and-dropped-packets-on-linux

PreviousExample: Schrödinger

Last updated 7 years ago