Chaos Heidi vs. Orchard: Self-Disruption and Healing in a Cloud Foundry-Based Service Environment
summary
Swisscom builds Orchard, a backend health-management platform that centralizes Consul checks, Riemann rules, Splunk and InfluxDB storage, and can trigger automated healing actions; Orchard already automates simple fixes and exposes dashboards for end-to-end service state. A companion tool Chaos Heidi runs scripted attacks via agents (RabbitMQ control) to simulate failures — VM kills, BOSH job outages and network partitions (e.g. iptables deny) — to train Orchard and reproduce a ghosted VM caused by the BOSH resurrector.
AI-written summary · about
chapters (5)
- 0:00Introduction and overview
- 3:00Swisscom and Cloud Foundry
- 10:48Orchard monitoring system
- 16:38Chaos Heidi disruption framework
- 20:10Future plans and Q&A
related talks
57mChaos Engineering Primer
55mChaos Engineering for Cloud Foundry Platform
18mFostering Chaos Engineering Culture
13mKeynote: Chaos Engineering on Cloud Foundry
28mRevealing Resilience Vulnerabilities in Spring Boot Architectures
39mPracticing Cloud-Native Resliency Is a Challenge: Decoding It with Chaos...
37mBringing order to the chaos!
30mBringing Order to Chaos: Make Your Systems More Resilient with Chaos Engineering