3. ‹#›
The Agile Manifesto
• Customer satisfaction by rapid delivery of useful software.
• Working software is delivered frequently.
• Working software is the principal measure of progress.
• Sustainable development, able to maintain a constant pace.
• Continuous attention to technical excellence and good design.
4. ‹#›
The Problems
• We need to be able to deploy quickly.
• Consistently.
• Across a wide range of devices.
• With minimal downtime.
• Rollbacks.
10. ‹#›
Found out what we need to update
Found out where we need to deploy to
Made a check list
Make the process easy as possible
Now, make it easy
11. ‹#›
Infrastructure as Code
• Lowers cost of server administration
• Reliable deployments
• Code is the documentation
• Agility
• Continuous integration and deployment
• Development / Testing / Production
17. ‹#›
Make it happen
Take a deep breath
Turn your deployment into a checklist
Checkout new tools
Automate build process
Automate deployment process
Enjoy stress free deployments!
worked at sl for 10 years
started off as level 1 tech support,
worked in professional services,
technical account management,
developement, and now as a Evangelis
“No cowboys, pit crews.”
“Looked at other high risk industries, construction, aviation, all had checklists. Tools to make experts better. Complication fell 35%, death rates fell 47%.”
“Humility, Discipline, teamwork. VS Independence, self sufficiency, autonomy"
— Atul Gawande
Dr. Pronovost’s checklist
Pause points. Before deploy, after deploy, etc.
Talk about pause points, Pre/deployment/post
Think about how you deploy, make a step for everything you did, ESPECIALLY for things you missed.
trello.com
each step has more details
which servers to deploy on, who is responsible, etc
hers my checklist for things I wanted to tell you to do
now that we have a checklist, lets view some projects that can make the list shorter
talk about SL automation,
API, this is our factory floor
disposable servers