This is a webinar presentation I did with Daniel Aragao for the ThoughtWorks Continuous Delivery series. We focus on 3 common impediments to implementing continuous delivery and our 3 step process to overcoming them. Given our target audience, this presentation was not very technical, but focuses on ideas and concepts rather than working code. You can listen to and watch the presentation here: http://continuous-delivery.thoughtworks.com/events/delivery-cloud

1. We’ll begin shortly...

2. May 2012
Continuous Delivery
and the Cloud
Daniel Aragao and Nigel Fernandes pairing

3. ThoughtWorks Office
We’re Here!

4. daniel.aragao@thoughtworks.com
linkedin.com/in/danielaragao

5. nigel@thoughtworks.com
github.com/nigelfds

6.  Impediments to Continuous Delivery
 Three step cloud strategy to beat them
 Summary
 Questions

7. This Webinar is not
Continuous Delivery 101
About tools and vendors
Actual Code

8. Implementing
Continuous Delivery…

9. “How? Fast, automated feedback on
the production readiness of your
applications every time there is a
change whether code, infrastructure,
configuration or database.”
Jez Humble

10. Understanding the path to production

11. Provision Provision Provision
Build Configure Configure Configure
Deploy Deploy Deploy
Validate Validate Validate
✔ ✔ ✗

12. Accidental > Necessary
Inconsistency

13. Environment provisioning shouldn’t be a project

14. Snowflake Environment

15. Quick Recap
 Accidental inconsistency > Necessary inconsistency
 High turn around time per environment
 Environments that can’t be rebuilt from scratch

17. Step 1
Configuration as Code

18. Provision Provision Provision
Build Configure
Configure Configure
Configure Configure
Configure
Deploy Deploy Deploy
Validate Validate Validate

19. What is configuration in this context
Everything that is needed to convert a vanilla
Operating System into a useable state for a
given application.

20. Declarative
Executable
Versioned

21. Run
Sheets
Manual
Config

22. Anti-pattern ahead

23. The first time a configuration
item is executed is on production

24. Step 2
Automation

25. Automate machine provisioning
Provision Provision Provision
Build Configure Configure Configure
Deploy Deploy Deploy
Validate Validate Validate

26. Virtualization

27. Cloud and on-demand capacity

28. Automate deployments
Provision Provision Provision
Build Configure Configure Configure
Deploy Deploy Deploy
Validate Validate Validate

29. Automating deployments
 Command distribution frameworks
 Push over SSH
 Message bus based

30. Anti-pattern ahead

31. Automate the creation of unique
environments all the way to production

32. Step 3
Build and promote environments

33. What are environments in this context?
 Support apps and frameworks
 Databases and data included
 Specific validation or audiences

34. Putting step 1 and 2 together
Promote Promote
Build Provision
Configure
Deploy Validate Validate
Validate
✔ ✔ ✔

35. Towards minimum configuration
across environments

36. Getting the most out of the
cloud and elastic capacity

37. Summary
Step 1
Automation
Step 2
Configuration as Code
Step 3
Build and promote environments

38.  continuous-delivery.thoughtworks.com
 github.com/nigelfds/configuration-master
 Release It! - Nygard
 Continuous Delivery - Humble
and Farley
 The Visible OPS Handbook - Behr,
Kim and Spafford

39. “Fast, automated feedback on
the production readiness of your
applications every time there is a
change whether code, infrastructure,
configuration or database.”
Jez Humble

40. “Build and promote whole environments using
automation that treats every configuration as code.”