Sascha Möllering discusses how his company moved from manual server setup and deployment to automated deployments using infrastructure as code and continuous delivery. They now deploy whenever needed using tools like Chef and JBoss to configure servers. Previously they faced challenges like manual processes, difficult rollbacks, and biweekly deployment windows. Now deployments are automated, safer, and can happen continuously.

1. Sascha Möllering | ZANOX.de AG
Continuous Delivery and Infrastructure
as Code

2. About me
Sascha Möllering
Software Engineering Team Lead
sascha.moellering@zanox.com
http://www.der-maschinenstuermer.de/
@sascha242

3. TABLE OF CONTENTS
•
•
•
•
•
•
Problem?
Solution!
Continuous Delivery
Infrastructure as Code
Chef and JBoss
Q&A

4. TABLE OF CONTENTS
•
•
•
•
•
•
Problem?
Solution!
Continuous Delivery
Infrastructure as Code
Chef and JBoss
Q&A

6. Problem?
• Situation two years ago:
– Manual server setup
– Manual deployment
– Deployed files contain a lot of changes
– Rollbacks difficult
– Time slots for deployments (biweekly)
– Windows environment
– ...

8. TABLE OF CONTENTS
•
•
•
•
•
•
Problem?
Solution!
Continuous Delivery
Infrastructure as Code
Chef and JBoss
Q&A

9. Solution!
• Now:
– Automated deployments
– Infrastructure as Code
– Only small changes
– Rollbacks are easy
– Deploy whenever you want!
– Linux environment
– ...

11. DELIVER
HIGH QUALITY SOFTWARE
AT LOW RISK
FAST,
ANYTIME
BY THE PRODUCT
TEAMS THEMSELVES!!!

12. Solution!
•
•
•
•
•
Etsy
Github
Flickr
Facebook
Amazon
25 deployments / day
40 deployments / day
60 deployments / day
Up to 100 deployments / day
Deployment every 11.6 sec

13. TABLE OF CONTENTS
•
•
•
•
•
•
Problem?
Solution!
Continuous Delivery
Infrastructure as Code
Chef and JBoss
Q&A

14. Continuous Delivery
„Reduce the cost, time, and
risk of delivering
incremental changes to
users“
(Jez Humble, Adopting continuous
delivery)

15. Continuous Delivery
Releasing frequently =>
Reduce the risk of release
(John Allspaw, Ops Meta-Metrics)

17. Continuous Delivery
• Standardize
– Naming conventions
– Platform
– Infrastructure
• Fully automated release processes to
Live-System
• Empower teams to release by
themselves

18. Continuous Delivery
•
•
•
•
Automate all the tests
Introduce ATDD/BDD patterns
Static code analysis
Automated quality gates

19. Continuous Delivery

20. Continuous Delivery

21. Continuous Delivery
Metrics
Monitoring
Alerting

22. Continuous Delivery
Metrics
Monitoring
Alerting

23. Continuous Delivery
Monitoring

24. Continuous Delivery
Monitoring

25. TABLE OF CONTENTS
•
•
•
•
•
•
Problem?
Solution!
Continuous Delivery
Infrastructure as Code
Chef and JBoss
Q&A

26. Infrastructure as Code
• Infrastructure is treated like code
– tag, branch and release
– testing
• Predictable outcome
• Removing manual steps
• Tools like Chef or Puppet

28. Infrastructure as Code
"Chef is like a little system admin
robot ... you tell it how you want your
system configured, and it will do all
the dirty work.”

29. Infrastructure as Code

30. Infrastructure as Code

31. Infrastructure as Code

32. Infrastructure as Code

33. Infrastructure as Code

34. TABLE OF CONTENTS
•
•
•
•
•
•
Problem?
Solution!
Continuous Delivery
Infrastructure as Code
Chef and JBoss
Q&A

35. Chef & JBoss
Java Magazin 11.12:
Automatisierung nach Chef-Rezept
Automatisiertes Deployment von
JBoss Middleware
AWSAktuell:
Elastic JBoss AS 7 clustering in
AWS using EC2, S3, ELB and Chef

36. Chef & JBoss
• Automatic deployment of JBoss AS using
Chef
• Components:
•
•
•
•
•
JBoss EAP 5/6 preconfigured in SVN
Jmxtrans for monitoring
DataSources managed in SVN
Stage is a system-property
Twiddle is used to apply node-specific
configurations

37. Chef & JBoss

38. Chef & JBoss

39. Chef & JBoss
EAP 5:
EAP 6:

40. Chef & JBoss
• Wrapper around twiddle.sh
• Parameters piped into a txt-file
• After server-start:
• Txt-file analyzed
• If file contains twiddle-commands
• Twiddle-commands executed

41. Chef & JBoss
Fabric

42. Chef & JBoss
• Fabric
– Python library and command-line tool
– Streamlining the use of SSH
– Application deployment
– Used to deploy apps from Nexus
– https://github.com/fabric/fabric

43. Lessons learned
•
•
•
•
•
•
Infrastructure as Code is hard
Continuous Delivery is hard
But: mindset change is even harder
Safety net is necessary
Continuous improvement
There is no „silver bullet“