Move Fast and Don’t Break Things: Pre-Deployment Validation
summary
An offline, config-driven validator called Batfish analyzes normalized device configs and builds routing, forwarding and abstract behavior models to prove safety properties before deployment. It integrates into CI (example: GitHub → Travis) and runs reachability simulation and ACL/firewall audits, flagging concrete failures: a static null route that drops flows, a stray passive-interface that breaks redundancy, and an unintended SMTP 2525 exposure; fixes are validated interactively or in the pipeline.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:12Intentionet: Who are we?
- 2:30What is pre-deployment validation?
- 4:42How can you implement pre-deployment validation? Use Batfish!
- 5:25What can Batfish do?
- 7:17How it works?
- 10:00Network Policies
- 12:01How can you use Batfish?
- 13:18Today's Demo
- 13:39Continuous Integration
- 19:54Network maintenance MOP validation
- 25:59Security policy change validation
- 31:35recap
- 32:07Getting started with Batfish is easy
related talks
36mBuild infrastructure as a code (IaC) using test-later...
41m0Flake - Reaching reliable non-flaky tests
18mPreview: Verification (Correctness & Debugging)
28mChaos Validation Made Easy
12mMetha: Network Verifiers Need To Be Correct Too!
40mBullet-proof projects
21mI Don’t Always Test My Code, but When I Do It’s in Production
01h 15mTaking Control Of Your Test Environment