DevOps by examples - Azure Meetup Frankfurt 06-2017
Download as PPTX, PDF1 like252 views
The document provides an overview of DevOps, emphasizing its cultural significance and the collaboration between software developers and IT professionals. It outlines key concepts such as continuous delivery, infrastructure-as-code, and application monitoring while introducing essential tools and practices involved in DevOps implementations. Additionally, it discusses the automation of software delivery processes and the importance of agile principles in enhancing IT service delivery.
DevOps by examples - Azure Meetup Frankfurt 06-2017
- 1. DevOps by examples Giulio Vian http://blog.casavian.eu/ giulio.dev@casavian.eu @giulio_vian http://www.getlatestversion.it/
- 2. 1990 1992 1999 2014 2010 2016 1995 freelance 2014 2015 TFS Aggregator ?
- 3. Most recent project © 2016 IMG Universe, LLC. All Rights Reserved 3
- 4. This Session 100/200-level Grasp the essentials of the DevOps approach. (well …, some essentials) Leave open questions to the end Something Olde, Something New, Something Borrowed, Something Blue 4
- 5. What we will talk about? DevOps intro Demos Environment hosting the app The Application itself Deployment Dynamic configuration Monitoring Wrap-up 5 OpsDev
- 6. Your turn Azure Visual Studio Team Services (VSTS) ASP.NET Linux (Ubuntu) Developers Infra Engineers Architects Managers 6
- 8. DevOps is a job? 8
- 9. DevOps is a product? 9
- 10. DevOps is a culture, movement or practice DevOps is a term used to refer to a set of practices that emphasizes the collaboration and communication of both software developers and other information- technology (IT) professionals while automating the process of software delivery and infrastructure changes. DevOps represents a change in IT culture, focusing on rapid IT service delivery through the adoption of agile, lean practices in the context of a system-oriented approach. DevOps emphasizes people (and culture), and seeks to improve collaboration between operations and development teams. DevOps implementations utilize technology — especially automation tools that can leverage an increasingly programmable and dynamic infrastructure from a life cycle perspective. DevOps is the union of people, process, and products to enable continuous delivery of value to our end users. Wikipedia (2017) Gartner Microsoft (Donovan Brown) 10
- 11. Continuous Delivery evolution… Source: Jez Humble © 2010 11
- 12. …rooted in Agile Principles Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan http://agilemanifesto.org/
- 13. «Main course» Where? Infrastructure-as-Code What? Build & Package How? Deploy 13
- 14. Execution environment Operating System O.S. Modules Local Services, Libraries Application Network & External Services Data 14
- 15. Execution environment (alt) Base container Custom Container Application (in container) Network & External Services (e.g. Kubernetes) Data 15
- 16. Execution environment – Comments Setup times vs. launch times Capacity planning Running costs (Buy vs. Make) 16
- 17. Infrastructure-as- Code Azure Resource Manager • Code • Automation 17
- 18. Infrastructure-as-Code – Comments Declarative vs. Imperative Version Control Continuous Integration Dynamic vs. Static Azure Resource Manager Declarative Json-based Extensible (script, DSC) Entire infrastructure AWS CloudFormation Declarative Json-based Terraform Docker Not much declarative Single container Swarm, Kubernetes, Mesos, … Ansible, Puppet, Chef, CFEngine, … 18
- 19. Application Web page showing DB data • Environment • Configuration 19
- 20. Build & Packaging Collect everything 20
- 21. Build & Packaging – Comments Version Control Continuous Integration Semantic Versioning Artifacts Images (Docker, AMI, Azure VM images) 21
- 22. Deploy VSTS Release Management • Controlled Automation 22
- 23. Secrets Build time Signing Deploy time Credentials Run time Tokens Avoid exposures git push hook Static analysis .gitignore Centralized Version Control Distinct repositories Azure Key Vault, AWS Key Management Service, etc. 23
- 24. Deploy – Comments Category Dev / QA / Prod Integrated (dynamic) Release cadence Feature toggles 24 Source: Pete Hodgson
- 26. So far 26 OpsDev
- 29. Troubleshooting & Feedback loop Access to production Read-only Debug Sensitive production data Design/architecture Quality of data Those Precious PDBs 29
- 30. More VSTS – Azure Links DevTest labs Deployment Load testing 30
- 31. «Dessert» 31
- 35. Call to action 35 (Photo: Francesco Canu)
- 37. To know more Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation — J.Humble, D.Farley (Addison-Wesley) https://www.amazon.com/Continuous- Delivery/dp/0321601912/ The Phoenix Project — G.Kim, K.Behr, G.Spafford (IT Revolution Press) https://www.amazon.com/Phoenix-Project- DevOps-Helping-Business/dp/0988262509/ 37
- 38. To know more (cont’d) The DevOps Handbook — G.Kim, P.Debois, J.Willis, J.Humble (IT Revolution Press) https://www.amazon.com/DevOps- Handbook-World-Class-Reliability- Organizations/dp/1942788002/ Continuous Delivery with Visual Studio ALM 2015 — M.Olausson, J.Ehn (Apress) http://www.amazon.com/Continuous- Delivery-Visual-Studio-2015/dp/1484212738/ 38
- 39. Partial checklist Where is configuration stored? How is configuration updated? Is production configuration isolated and secured? Where are the secrets and who can access them? How versions are tracked? Who authorizes changes and how? How data is preserved on updates? How data schema and module interfaces updates? Using environment images or scripts? How big is the deploy window? How are the tracked activities and errors? How are operational data is collected from production? 39
- 43. Azure Portal
- 44. Resource Groups
- 46. Visual Studio Team Services – Project home 46
- 47. Visual Studio Team Services Release Management
- 49. Install packages
- 50. Environment creation in progress
- 52. Application 52
- 53. Version Control
- 54. Home page 54
- 55. Query “C” 55
- 59. App build script
- 60. Deploy 60
- 61. App deploy script – Database
- 62. App deploy script – Copy files to Target
- 63. App deploy script – Run final setup script
- 64. App deploy – configuration data
- 65. App deploy – source packages
- 67. Deploying the app – pick a version
- 68. App deploy log
- 69. App deployed 69
- 71. Toggle feature script – generate new config files
- 72. Toggle feature deploy script – deploy config changes
Editor's Notes
- #11: http://www.gartner.com/it-glossary/devops/ DevOps is a term used to refer to a set of practices that emphasize the collaboration and communication of both software developers and information technology (IT) professionals while automating the process of software delivery and infrastructure changes. It aims at establishing a culture and environment, where building, testing, and releasing software can happen rapidly, frequently, and more reliably. Wikipedia (2017)
- #15: The 1975 book _Algorithms + Data Structures = Programs_ of Turing Award winner Niklaus Wirth is still relevant.
- #25: http://martinfowler.com/articles/feature-toggles.html
- #42: Nota con VSTS cloud non significa pubblico!
- #75: Nota con VSTS cloud non significa pubblico!
- #76: http://www.gartner.com/it-glossary/devops/ DevOps is a term used to refer to a set of practices that emphasize the collaboration and communication of both software developers and information technology (IT) professionals while automating the process of software delivery and infrastructure changes. It aims at establishing a culture and environment, where building, testing, and releasing software can happen rapidly, frequently, and more reliably. Wikipedia (2017)