Getting Faster, Continuous Lifecycle 2013

How we got from a release every six month to daily releases.

Transcript

1. getting faster How we got from a release every six month TO daily releases Continuos Lifecycle 11.11.2013
2. AndrÉ von deetzen @vdandre Oliver Wehrens @owehrens
3. Migration what’s next Status Agenda one stack Lessons learned
4. Status How we started
5. 150 DEV / QA / OPS
6. > 100 SOURCE REPOSITORIES
7. 1 RELEASE EVERY SIX MONTH
8. 1 TEAM TO RELEASE & DELIVER
9. 1 DEPLOYMENT IN PRODUCTION
10. Technology stack PHP JAVA RUBY LINUX puppet tomcat C++ C SQL perl python jboss httpd
11. development & production different installer other os bare metal vs virtualisation different puppet versions other ways of monitoring
12. Wait whaT? How did we GET here? Features, Features, Features faster, faster, faster (not really) solved the scaling problem upfront
13. Transition What did we do?
14. Time to market Analysis 6 Months 2 Weeks daily
15. Squeeze The existing
16. Automate as much as we can
17. From 6 to 3 Months
18. scrum no more waterfall
19. From 3 to 1 Month
20. optimize agile + automation
21. From 1 Month to 2 weeks
22. Still a monolith
23. Still nightly deployments
24. New Functionality?
25. We can do better!
26. One Stack (with variations)
27. new platform simplify unify loosely coupled daytime deployment disaster recovery !
28. Three areas to change
29. Architecture (many) small services stateless independently deployable stable interfaces
30. Deployment MAKE RPM NOT WAR PUPPET with HIERA automatic vm setup
31. Workflow staging build chain empower teaMs infrastructure
32. create virtual machine install yum, rpm, centos reboot smoketest lifecycle configure puppet operate €€€
33. technology stack JVM Tomcat Centos 6 YUM & RPM Puppet 3 REST
34. deployment pipeline development release candidate certified release reference production
35. started with one new service and one team
36. Approach became very popular
37. existing services ? anti corruption Layer refactoring rewrite (better not do it)
38. > 200 Deployments STAGED TO PRE-PRODUCTION ON OUR BEST DAY IN 2013
39. 2014 What’s next?
40. Automate all the things! Puppet for network components Automate firewalls Increase visibility Infrastructure self service evaluate container based approach instead of VMs
41. lessons learned
42. Same environment & Tools Everywhere is essential
43. don’t get too fast, we could not deploy every delivery
44. had not enough Capacity for VMs in Development
45. Rewrite = Long time no roi
46. Spreading Knowledge can’t be fast enough
47. need to recreate any Machine automatically
48. Questions ? And yes, we’re hiring too! come talk to us.
49. Thanks for your attention!