Deploy like nobody is watching

Re-Run of my »Deployment« Talk for RubyShift Munich.

Transcript

1. Deploy like nobody is watching. March 11th, 2015 @bascht
2. Ye olde DevOps
4. Silos
5. Distribution of roles
6. Creative Commons Attribution 4.0 International (http://commons.wikimedia.org/wiki/File:The_Devil_and_Dr._Faustus_meet._Wellcome_L0031469.jpg)
7. …the »old world« software developer…
8. …the »old world« system administrator…
9. So – let's swap roles. (Can't be that hard, no?)
10. * { /* No idea what I'm cascading here… */ color: 'Kornblumenblau' !important; }
11. $$('I'){ $('will#wrap').each(function('until'){ return this.self._self.that['crap'].works; }); };;;; // eat ._this, jslint!
12. $ sudo sudo su -c "sudo do --what 'I want'"
13. Small castles CC BY-NC-ND 2.0 — Jos van Wunnik
14. Galileo Galilei - 1636
15. nginx::resource::upstream { 'here_be_dragons': members => [ 'lolcathost:8080', 'lolcathost:8081', 'lolcathost:8082', ], } nginx::resource::vhost { 'app.yournextstartup.com': proxy => 'http://here_be_dragons', }
16. Tools ansiblebcfg2cdistchefcfengineisconfjujulcfg ocsinventoryngwithglpiopsipikt puppetquattorradmindrex rundecksmartfrogsaltspacewalk
17. docker docker docker docker docker docker docker docker docker docker docker docker docker docker
18. Being responsible for the artefact that is shipped. Every step of the pipeline.
20. MANAGEMENT = :mediocre CUSTOMER = :opinionated def my_little_farm(requirements) engineering = :truly_optimistic trap("SIGINT") { ignore_those_admins } pray_for(some.kind_of? Wonder) ship! end
21. Releases.
22. Imagine… …it's friday.
23. Your deployment plan… …doesn't scale very well.
24. gut metrics Who truly understands every base / helper / tools / domain class? Who understands your deployment process?
25. busnumber
26. Why not… deploy as often as possible? let the new employee deploy on her first day? deploy when nobody is watching?
27. 2015 Infrastructure code is code as well!
28. Are your problems bubbling up… …from app code? …from your server configuration? …during rollout? …because of poor orchestration?
29. © 2013 — theprofoundprogrammer.com
30. No more excuses. Infrastructure problem? File an issue Infrastructure change? Hand in a story App Changes need infrastructure changes? Orchestrate your rollouts.
31. No commit without an issue id / feature branch. No major release without documentation in an issue.
32. Do code reviews. Yes. for infrastructure. Yes. Even for infrastructure.
33. Sorry, but there is no one-size-fits-all solution. Quelle: GFDL image by user Fanghong. Creative Commons Attribution-Share Alike 3.0 Unported
34. Well, turns out there is.
35. Documentation (imagine rolling thunder)
36. CLI > Code > Wiki $ bin/deploy --wat?
37. Actually use your Wiki! New employees? Old hostnames? Cross references! Macros? Copy / Paste commands?
38. Your toolchain? in version control useful names well documented self-explanatory independent from the environment
39. Use some nice wrapping.
40. #!/bin/(da|ba)sh #nope
41. #!/usr/bin/env ruby
42. --Chet Ramey “ ... there are dark corners in the Bourne shell, and people use all of them. ”
43. Build for the worst. Do your error pages cover every layer? Will every layer fail gracefully? Can you roll back? Should you roll back? Can you deactivate features? Can you afford to deliver stale content?
44. restore > backup
45. employee of the month
46. Updating artefacts isn't the last step!
47. Monitor every deployment. Gather health checks.
48. Steal good ideas! $ curl -XGET 'lolcathost:9200/_cluster/health?pretty=true' { "cluster_name" : "prism_europe", "status" : "green", "timed_out" : false, "number_of_nodes" : 242, "number_of_data_nerds" : 242 "active_primary_shards" : 50, "active_shards" : 100, "people_actually_reading_this_slide": 1, "relocating_shards" : 0, "initializing_shards" : 0 }
49. Use obvious tools. var casper = require('casper').create(); var baseurl = casper.cli.get("baseurl") || 'http://bascht.com'; casper.start(baseurl, function() { this.capture('shots/homepage.png'); this.test.assertTitle('bascht.com'); this.test.assertExists('input[action$="/search"]', 'Yay!'); this.clickLabel('Blog', 'a'); });
50. — Timothy Fitz (IMVU) “Treat staging failures like as if they were production failures.”
51. We're almost done.
52. -- Robert A. Heinlein “Specialization is for insects.”
53. See how things work out. # ~/.bash_login rm ~/.bash_history && sync; echo "They never fail who die, In a great cause! Lord Byron"; echo "Welcome to $(hostname).";
54. Sebastian Schulze (@bascht / @bscht) , 29.years Software- & infrastructure developer Vogtland, Leipzig, Köln, Berlin, Munich Thank you! Twitter / Github / ADN: @bascht