Continuous Delivery and the Cloud

713 views

Published on

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

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
713
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
23
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • What you’re looking for when capturing environment configuration as code is that it should be Declarative : Easy to follow, documentation, should not need testingExecutable: living specification, does not go out of date like run sheetsVersioned: to evolve along side the application, changes auditable and traceable.
  • Remember the aim is to get rid of the configuration sections in Run-sheets
  • Continuous Delivery and the Cloud

    1. 1. We’ll begin shortly...
    2. 2. May 2012 Continuous Delivery and the CloudDaniel Aragao and Nigel Fernandes pairing
    3. 3. ThoughtWorks Office We’re Here!
    4. 4. daniel.aragao@thoughtworks.com linkedin.com/in/danielaragao
    5. 5. nigel@thoughtworks.com github.com/nigelfds
    6. 6.  Impediments to Continuous Delivery Three step cloud strategy to beat them Summary Questions
    7. 7. This Webinar is not Continuous Delivery 101 About tools and vendors Actual Code
    8. 8. ImplementingContinuous Delivery…
    9. 9. “How? Fast, automated feedback onthe production readiness of yourapplications every time there is achange whether code, infrastructure,configuration or database.” Jez Humble
    10. 10. Understanding the path to production
    11. 11. Provision Provision ProvisionBuild Configure Configure Configure Deploy Deploy Deploy Validate Validate Validate ✔ ✔ ✗
    12. 12. Accidental > Necessary Inconsistency
    13. 13. Environment provisioning shouldn’t be a project
    14. 14. Snowflake Environment
    15. 15. Quick Recap Accidental inconsistency > Necessary inconsistency High turn around time per environment Environments that can’t be rebuilt from scratch
    16. 16. Step 1Configuration as Code
    17. 17. Provision Provision ProvisionBuild Configure Configure Configure Configure Configure Configure Deploy Deploy Deploy Validate Validate Validate
    18. 18. What is configuration in this context Everything that is needed to convert a vanilla Operating System into a useable state for a given application.
    19. 19. DeclarativeExecutableVersioned
    20. 20. Run SheetsManualConfig
    21. 21. Anti-pattern ahead
    22. 22. The first time a configurationitem is executed is on production
    23. 23. Step 2Automation
    24. 24. Automate machine provisioning Provision Provision ProvisionBuild Configure Configure Configure Deploy Deploy Deploy Validate Validate Validate
    25. 25. Virtualization
    26. 26. Cloud and on-demand capacity
    27. 27. Automate deployments Provision Provision ProvisionBuild Configure Configure Configure Deploy Deploy Deploy Validate Validate Validate
    28. 28. Automating deployments Command distribution frameworks Push over SSH Message bus based
    29. 29. Anti-pattern ahead
    30. 30. Automate the creation of uniqueenvironments all the way to production
    31. 31. Step 3Build and promote environments
    32. 32. What are environments in this context? Support apps and frameworks Databases and data included Specific validation or audiences
    33. 33. Putting step 1 and 2 together Promote PromoteBuild Provision Configure Deploy Validate Validate Validate ✔ ✔ ✔
    34. 34. Towards minimum configuration across environments
    35. 35. Getting the most out of the cloud and elastic capacity
    36. 36. SummaryStep 1AutomationStep 2Configuration as CodeStep 3Build and promote environments
    37. 37.  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
    38. 38. “Fast, automated feedback onthe production readiness of yourapplications every time there is achange whether code, infrastructure,configuration or database.” Jez Humble
    39. 39. “Build and promote whole environments usingautomation that treats every configuration as code.”

    ×