Mastering Complex Application Deployments

2,360 views

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,360
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
51
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Mastering Complex Application Deployments

  1. 1. Mastering the Complex Application Deployment Eric Minick, Lead Consultant1
  2. 2. Your Deployments might be hard if….• You have long deployment• The business complains about long outage windows• Numerous planning meetings• You spend all weekend at the office• Deployments are seen as risky• We celebrate when we are successful2
  3. 3. The GoalProduction releases should be a non-event3
  4. 4. From “Hard” to a “Non-Event”• Why deployments are so complex• Where basic automation helps• Coordinating deployments• Increasing consistency4
  5. 5. From “Hard” to a “Non-Event”• Why deployments are so complex• Where basic automation helps• Coordinating deployments• Increasing consistency5
  6. 6. Modern systems have many pieces• Complex Architecture: Tiers, SOA, busses…• Inter-related systems mean changes have wide impact.6 Image from ischool.tv
  7. 7. Componentized applications are staying• Agile encourages smaller teams• Conway’s Law tells us that smaller teams, cooperating on a big system will produce more components. – And to deploy, we need all their expertise• 84% of Global 2000 using SOA by end of 2010 (Forrester)7
  8. 8. Lots of steps and people• Manual releases require lots of… – Steps to do the work – People to execute the steps – People on call to fix it when things break• Deployment document example from a Fortune 100 customer – ~15 components – 148 People – 600 lines in Excel• We’ve seen the 10,000 step deployment plan8
  9. 9. Our releases are inconsistent• Many components in the system, but they don’t change all at once – Most changes involve more than one, but less than all pieces• We write a new plan for each release9
  10. 10. From “Hard” to a “Non-Event”• Why deployments are so complex• Where basic automation helps• Coordinating deployments• Increasing consistency10
  11. 11. Automation is great…• A basic script can turn 10 steps into 1 or 2 steps.• Distributed workflow engines can easily model a component deployment• With environment modeling, you can consistently deploy through environments.11
  12. 12. Automation works with people• People are good at creative work and problem solving• People are bad at “consistency”.• Good plan: – People design automation and troubleshoot – Computer consistently runs a process.• See our webcast “Death to Manual Deployments”12
  13. 13. …but we still have a coordination problem• Distributed automation or runbook can deploy components or even systems• But what exactly do I deploy? What goes together?13
  14. 14. From “Hard” to a “Non-Event”• Why deployments are so complex• Where basic automation helps• Coordinating deployments• Increasing consistency14
  15. 15. How do we know what goes together?• We want: – Components with changes ready to release – No components with changes not ready – All components needed by the components we need (deployment dependencies)15
  16. 16. How do we know what goes together?• “All components needed by the components we need” is a tough requirement• Traditionally satisfied by asking Dev and trusting their omniscience • Works most of the time– Or we trust the ALM (Source + Bug Tracking) tools • Could work if people were perfectly disciplined • People are not16
  17. 17. How do we know what goes together?• Test it! – ALM tools and developer oral histories suggest what to test together – Once verified, the stuff in Test is the stuff we want in Production17
  18. 18. Model basedDeployment Strategy• Model the system in a test environment• Promote the model across environments• Model includes: – applications, app configuration, databases, infrastructure, settings – Aware of environment specifics as well18
  19. 19. Requirements for Model Promotion• Inventory – what is where• Recording inventory as a Model• Testing that we can trust19
  20. 20. Model Promotion: Inventory• To promote what is in Test to Production, we must know what is in test• To know the extent of the change, we must know what is in production• Inventory of all environments • What versions of each component make up the system • Where appropriate, treat configuration as a component• Bonus: Inventory helps with visibility and audit20
  21. 21. Model Promotion: Model Snapshots• Need to be able to snapshot the inventory to define a desired state• Approaches: – Spreadsheets listing component versions – Change management tickets with components as attachments – Build it into your deployment product (we did)21
  22. 22. Model Promotion: Testing we can trust• Testing validates compatibility• Must leave adequate time to test• With more automated tests, we can: – Test quicker – Test more creatively• Automated tests should run in ALL environments22
  23. 23. From “Hard” to a “Non-Event”• Why deployments are so complex• Where basic automation helps• Coordinating deployments• Increasing consistency23
  24. 24. Each deployment is different• Only a subset of components change in a release• Sometimes we change configuration24
  25. 25. Have a single deployment process• Define the process for releasing the entire system• Note which steps are associated with what components• Execute only the steps for the components that are changing (which your inventory tells you)25
  26. 26. Relentlessly remove variation• Developers and architects contribute to repeatable releases• “Special” events (like adding a new data stream) must fit into any automation or defined process26
  27. 27. Use the same process in Test and Live• The earlier the process is used, the better – It will be tested more – Earlier environments have less tolerance for slowness• The process or automation must take into account environmental differences27
  28. 28. Key Takeaways1. Releases are complex, and the business needs them done rapidly28
  29. 29. Key Takeaways1. Releases are complex, and the business needs them done rapidly2. Traditional methods for determining what is released together should be used in Test29
  30. 30. Key Takeaways1. Releases are complex, and the business needs them done rapidly2. Traditional methods for determining what is released together should be used in Test3. Only components tested together should be released together30
  31. 31. Key Takeaways1. Releases are complex, and the business needs them done rapidly2. Traditional methods for determining what is released together should be used in Test3. Only components tested together should be released together4. Simple deployment automation is very helpful, but coordination is key31
  32. 32. Key Takeaways1. Releases are complex, and the business needs them done rapidly2. Traditional methods for determining what is released together should be used in Test3. Only components tested together should be released together4. Simple deployment automation is very helpful, but coordination is key5. Getting this right is easier if you have help from developers, testers, operations and release management32
  33. 33. References http://urbancode.com/resources• Death to Manual Deployments!• Build & Deployment Automation for the Lean Economy• ITIL Release Management and AutomationUrbancode.com/blogs/Twitter.com/UrbanCodeSoftFacebook.com/UrbanCodeSoft33
  34. 34. Yes, UrbanCode sells products for this• AnthillPro is now the DevOps Platform• DevOps Platform – Automated build, test and deployment. Includes UrbanDeploy.• UrbanDeploy – Application Release Automation34
  35. 35. Questions?35

×