The Salt Route
summary
PeopleDoc uses SaltStack on OpenStack to provision and configure a multi-team Django service landscape (two Django teams plus Java and Ember teams) from a single Git repo and a key operations group of ~40 people across Paris and New York. Centralizing states creates a bottleneck and version conflicts, so operational responsibility moves to teams, using reusable formulas and a Jenkins workflow with Jenkins + LXC to test deployments; the team reports this decentralized formula + container testing has worked in production for about five months.
AI-written summary · about
chapters (11)
- 0:00The Salt Route EuroPython 2015
- 1:12Helping the HR community increase productivity and employee satisfaction
- 1:571 Java/Scala team
- 3:23Openstack cloud instances
- 4:58SALTSTACK WHY? Python
- 11:39IT WORKS, BUT NOT FOR LONG...
- 12:22COMPLEXITY
- 14:25Split states by team USE THE FORMULA, LUKE
- 15:22"Untested code is broken code" think about infrastructure as code
- 16:29Jenkins + LXC
- 19:05Thank you!
related talks
40mSalt: How to be Truly Lazy
51mBuilding Web Scale Using Open Source on the Internet Assembly Line
39mBeyond Open Source Configuration Management: Rapidly Building Any Cloud at Scale
29mLive Demo
19mWhy did I create Salt?
52mScalable Systems Management with Salt
58mIntroduction to
41mDjango Deployments Done Right