Why did I create Salt?

on YouTube ↗19m

" summary

Salt (SaltStack) claims concrete results: benchmarks dramatically faster than competitors, scales to tens of thousands of nodes, and uses an asynchronous communication bus plus a normalized library to manage Linux, Windows, OS X, Docker and LXC and public and private clouds. Configuration is both declarative and deterministic, data-driven, and event‑aware; the platform exposes roughly 18 module insertion points and is credited with rapid mitigation of incidents such as Heartbleed.

AI-written summary · about

" chapters (15)

1. 0:00Intro
2. 1:00Unified approach
3. 3:45Snowflake servers
4. 5:37Minions
5. 6:15Communication
6. 6:52Scale
7. 7:34Normalized
8. 8:33Cross management
9. 8:51Modular layered
10. 9:49Configuration management
11. 10:59Imperative
12. 11:49Declarative
13. 13:08Autonomic
14. 14:24Environments
15. 15:13Events

" related talks

• 19mWhy did I create Salt?Thomas Hatch · dotScale 2013
• 39mBeyond Open Source Configuration Management: Rapidly Building Any Cloud at ScaleThomas Hatch · USENIX Configuration Management Summit 2013
• 51mBuilding Web Scale Using Open Source on the Internet Assembly LineThomas Hatch · LinuxCon + CloudOpen Europe 2013
• 58mIntroduction toMike Place · Rootconf 2015
• 52mScalable Systems Management with SaltSebastian Meyer · FrOSCon 2016
• 30mThe Evolution of DevOps AutomationThomas Hatch · DevOpsDays Salt Lake City 2016
• 40mSalt: How to be Truly LazyLex Hider · PyCon Australia 2013
• 37mSalting things up in the sysadmin's worldJuan Manuel Santos · EuroPython 2015