Dev ops: Continuous delivery and Windows Azure

3,546 views

Published on

Dev ops: Continuous delivery and Windows Azure

Published in: Technology

Dev ops: Continuous delivery and Windows Azure

  1. 1. DevOps: Continuous Delivery and Windows Azure Ibon Landa Plain Concepts
  2. 2.   
  3. 3. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Principles behind the Agile Manifesto
  4. 4. How long would ittakeyour organizationto deploya changethat involvesjust one singleline ofcode? Doyou dothis on arepeatable,reliable basis? Mary& Tom Poppendieck Implementing Lean Software Development
  5. 5. Done means "released". This implies ownership of a project right up until it’s in the hands of the user,and working properly. There’s noneof this "I’ve checked in my code so it’s done as far as I’m concerned". James Betteley
  6. 6. SOFTWARE DELIVERY MODELS
  7. 7. #1: No model, or random delivery.
  8. 8. #2: Let the operations guys figure out.
  9. 9. #3: Defined and collaborative approach.
  10. 10. DELIVERY PRACTICES
  11. 11. Version everything
  12. 12. Automate everything
  13. 13. Tokenize configurations
  14. 14. Use one-click deployments
  15. 15. Deploy to a copy of production
  16. 16. Deploy the same way to every environment
  17. 17. Have always a rollback mechanism in place.
  18. 18. Lock down the environments.
  19. 19. Build only once
  20. 20. Measure the delivery process
  21. 21. 26 Optimización de despliegues 1 2 3 Weeks Provisioning new HW SW Install/ config QA Certif. On-premises Windows Azure From 1-3 weeks to 30 minutes Every machine certified separately Basic checks prior to switch from staging QA Certif.
  22. 22. Bring the pain forward
  23. 23. Practice DevOps!
  24. 24. Build a release pipeline
  25. 25. Virtual Networks (10.0.0.0/16) (10.2.0.0/16) (10.1.0.0/16) 10.0.0.10 10.0.0.11 131.57.23.120 10.2.2.0/24 10.2.3.0/24 10.2.2.0/24 10.2.3.0/24 65.52.249.22 10.1.0.4 10.1.1.4
  26. 26. Continuous Delivery
  27. 27. Recipes and Cookbooks thatUSEE: Recipes and Cookbooks that describe and deliver code. Chef enables people to easily build & manage complex & dynamic applications at massive scale. • New model for describing infrastructure that promotes reuse • Programmatically provision and configure • Reconstruct business from code repository, data backup, and bare metal resources What is Chef? Chef is an IT automation platform for developers & systems engineers to continuously define, build, and manage infrastructure. CHEF USES:
  28. 28. Organizations Environments Roles Nodes Recipes Resources Cookbooks Run-lists Chef Concepts
  29. 29. ■Azure plugin for Chef ■Request new VM from Azure API ■Bootstrap it over WinRM ■Install and start Chef ■Register with Chef server ■Run through the “run list” ■Instant infrastructure with one command Provisioning with Chef
  30. 30. ■Easy to configure, reproducible, and portable work environments ■VirtualBox, Hyper-V, VMware, AWS, or any other provider. Windows Azure is not supported now. ■Shell scripts, Chef, or Puppet, can be used to automatically install and configure software on the machine ■Vagrant uses a base images: Boxes ■This Vagrant plugin allows you to standup Windows guests using WinRM instead of SSH Why vagrant?
  31. 31. ■Automate your OpenStack cloud infrastructure ■Juju Charms define applications as services ■An Ubuntu, OSX or Windows machine to install the client on ■GUI or command-line Ubuntu juju
  32. 32. Charms for everything you need
  33. 33. juju generate-config
  34. 34. ALM your way
  35. 35. ■A continuous deployment solution for .NET teams ■Automates the deployment process ■Simplifies managing multiple environments ■Improves collaboration throughout the process ■Provides release analytics and reporting ■History ■Originally launched in 2009 as InRelease by InCycle Software ■InRelease 2.0 launched in 2010, 3.0 in 2013 ■Acquired by Microsoft in 2013 Release Management
  36. 36. Automation
  37. 37. Collaboration
  38. 38. Team Foundation Server integration
  39. 39. Analytics & reporting
  40. 40. What about your own patterns & practices? Think about some delivery practice not covered in the session. Thanks @jlsoriat! http://aka.ms/ReleasePipeline
  41. 41. Thanks!
  42. 42. Madrid 29 de Marzo
  43. 43. http://spain.windowsazurebootcamp.org

×