Why Ansible vs. Salt vs. Nornir is the Wrong Question to be Asking
summary
Argues that picking between Ansible, Salt, Nornir (or Terraform or custom code) is the wrong question and instead scores platforms against concrete requirements: examples include sub-minute failover vs. batch 24-hour threshold jobs, a 10-minute expectation for routine change management, and a 100 devices per minute connectivity example. Recommends a checklist approach, notes evaluations are often 80/20 technical evaluation versus commercial, finds ease of getting started often wins a poll, and praises programming with handcuffs to learn and constrain solutions.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:58Current Landscape (per social media)
- 3:19Technical Evaluation
- 3:50Use Cases and Requirements
- 6:28Speed Requirements
- 7:36Actual Drivers
- 10:09Parting Thoughts
related talks
51mFrom Ansible to SaltStack — How and Why
50mJust Enough Network Automation to Get You Started
34mIs that an Ansible? Stop holding it like a Puppet
39mBeyond Open Source Configuration Management: Rapidly Building Any Cloud at Scale
28mNo Compromise: Use Ansible properly or stick to your scripts
19mWhy did I create Salt?
52mScalable Systems Management with Salt
49mWhen PowerShell Is Better Than Ansible? Recipes for Managing 1,000+ Servers