Grandma's recipe for DevOps adoption
- 1. Grandma‘s Recipe for DevOps Adoption Andrés García García, Fujitsu Enabling Software Technologies
- 2. 2 Who are we? Fujitsu Enabling Software Technology GmbH (EST) •Based in Munich, ~50 employees. •Development of innovative middleware and applications for public, private, and hybrid cloud. •SUSE partnership: -Monasca monitoring. •Dr. Andrés García García, DevOps Consultant, Partner Projects. •Experience helping internal and external projects to migrate to DevOps.
- 3. 3 DevOps is… “DevOps is the union of people, process, and products to enable continuous delivery of value to our end users. You cannot buy DevOps and install it. DevOps is not just automation or infrastructure as code. DevOps is people following a process enabled by products to deliver value to end users.” Microsoft “DevOps is an approach based on lean and agile principles in which business owners and the development, operations, and quality assurance departments collaborate to deliver software in a continuous manner that enables the business to more quickly seize market opportunities and reduce the time to include customer feedback.” IBM 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. Wikipedia
- 4. 4 Grandma‘s cooking... is like DevOps! There are recipes but… no ‘one size fits all’. Be open and flexible: Try different quantities, swap ingredients… Get and evaluate feedback. Practice, strive to improve, you are never done. Each dish is different and requires new learnings. Experience makes you better, Grandma’s cooking tricks. Cooking is not only utensils, it is also ingredients, steps… Recipes are still important! Guidelines for best practices. DevOps is a framework, methodology, mindset, or just a collection of IT best practices.
- 5. 5 Dish n.1: PICCO Brand new internal project. Cloud Native service. Technology moves fast. We wanted to operate ourselves. General interest on this “DevOps” thingy.
- 6. 6 Dish n.1: Results from first year Implement and use a DevOps environment in one project. • Stable and motivated team with DevOps culture. • Working deployment pipeline up to Google Cloud. • Features supporting DevOps in the product. • Increasing awareness for DevOps and operations topics. Provide quantitative evidence (KPIs) for the effects. Collect practical experience to spread to others. • Continuous assessment and improvement. • Projects/workshops within Fujitsu and for customers. • Articles and conferences. 03/2015 2016 2017 Consulting DevOps Workshops DevOps in production with PICCO Docker Artifactory Kubernetes RunonGCP Autodeploy Development And Staging Go Live 27.02.2016 Autodeploy GCP Slack TomEE SeleniumGrid SystemTest
- 7. 7 Dish n.2: Self Service Cloud platform. Large company in the financial sector. Large IT department for internal operations. Old operations model. • Machines are provisioned and configured by hand. • Delivery of a machine takes days, or even weeks. • Results are inconsistent. New operations model. • Machines are provisioned and configured automatically. • Delivery takes a few hours. • Results are consistent. Always get the same software. PMG HPOO Cloudify Chef Open Stack VMWare Software stack Services
- 8. 8 Dish n.2: Pain Points Pain points identified. • Low confidence in code quality. (CT) - Little or no testing. - Failing tests forever. - No QA process in place. • Manual end to end and integration tests. (CI) - Long and time consuming. - Low reliability. • Handcrafted production environment. (AD) - No knowledge on what software is running. - No traceability or auditability.
- 9. 9 Dish n.2: Results from the first quarter Set up of Jenkins server. End-to-end test using Selenium and Inspec. • Selenium GUI test to interact with PMG and Inspec to verify infrastructure configuration. • Result: Test and verify a lifecycle activity automatically in ~30 min. Integration tests using Kitchen and Docker. • Run cookbook tests in a Docker container and verify with Chefspec tests. • Runtime < 2:30 min. Unit/component tests using Rubocop, Foodcritic and Tox. • Result: Dashboards for Chef cookbooks including the following KPIs - Static code analysis and warnings. - Number of tests and failing tests. - Code coverage.
- 10. 10 Dish n.3: Web App Legacy, monolithic, waterfall project management tool. Impossible to develop new features. Very hard to maintain. Pilot DevOps project for the business unit. • Agile methodologies. • DevOps. • Microservices. Not touching the monolith!
- 11. 11 Dish n.3: Results so far Very heavy work in “basic practices”. Tons of Agile coaching: • How to write user stories. • How to scope sprints. • Specific advice on impediments. Set up and configuration of KPIs. Technology specific consulting: • CT/CI. • Automated build. • Delivery to a public Cloud (PaaS).
- 12. 12 Grandma’s recipe for DevOps 1. Assess current maturity. 2. Identify pain points. 3. Categorize and prioritize. 4. Determine next action item. 5. Study new technologies. Implement prototype. Write documentation. 6. Presentation. Coaching. Knowledge transfer. 7. Iterate. 0 0.5 1 1.5 2 2.5 3 3.5 4 4.5 5 Topic 1 Topic 2 Topic 3 Topic 4 Topic 5 Maturity assessment
- 13. 13 Grandma’s recipe for DevOps 1. Assess current maturity. 2. Identify pain points. 3. Categorize and prioritize. 4. Determine next action item. 5. Study new technologies. Implement prototype. Write documentation. 6. Presentation. Coaching. Knowledge transfer. 7. Iterate. Pain point 1 Pain point 2 Pain point 3 Pain point 4 Pain point 5
- 14. 14 Grandma’s recipe for DevOps 1. Assess current maturity. 2. Identify pain points. 3. Categorize and prioritize. 4. Determine next action item. 5. Study new technologies. Implement prototype. Write documentation. 6. Presentation. Coaching. Knowledge transfer. 7. Iterate. Pain point 2. Topic 1. High. Pain point 4. Topic 3. High. Pain point 1. Topic 4. Medium. Pain point 3. Topic 4. Low. Pain point 5. Topic 4. Low.
- 15. 15 Grandma’s recipe for DevOps 1. Assess current maturity. 2. Identify pain points. 3. Categorize and prioritize. 4. Determine next action item. 5. Study new technologies. Implement prototype. Write documentation. 6. Presentation. Coaching. Knowledge transfer. 7. Iterate. Pain point 2. Topic 1. High. Pain point 4. Topic 3. High. Pain point 1. Topic 4. Medium. Pain point 3. Topic 4. Low. Pain point 5. Topic 4. Low.
- 16. 16 Grandma’s recipe for DevOps 1. Assess current maturity. 2. Identify pain points. 3. Categorize and prioritize. 4. Determine next action item. 5. Study new technologies. Implement prototype. Write documentation. 6. Presentation. Coaching. Knowledge transfer. 7. Iterate.
- 17. 17 Grandma’s recipe for DevOps 1. Assess current maturity. 2. Identify pain points. 3. Categorize and prioritize. 4. Determine next action item. 5. Study new technologies. Implement prototype. Write documentation. 6. Presentation. Coaching. Knowledge transfer. 7. Iterate. 0 1 2 3 4 5 Topic 1 Topic 2 Topic 3 Topic 4 Topic 5 Maturity assessment +1
- 18. 18 Grandma’s recipe for DevOps 1. Assess current maturity. 2. Identify pain points. 3. Categorize and prioritize. 4. Determine next action item. 5. Study new technologies. Implement prototype. Write documentation. 6. Presentation. Coaching. Knowledge transfer. 7. Iterate. Pain point 2. Topic 1. Medium. Pain point 4. Topic 3. High. Pain point 1. Topic 4. Medium. Pain point 3. Topic 4. Low. Pain point 5. Topic 4. Medium. Pain point 6. Topic 3. Low. Pain point 7. Topic 3. Low.
- 19. 19 Grandma’s cooking tips for engineers Tie practices to business needs. Find allies. Identify pain points and requirements. Make clear and well defined proposals. Practice what you preach. Copy from others. Create prototypes. Measure outcomes. Don’t tell, prove. Seduce your opponents. €
- 20. 20 Grandma’s cooking tips for managers Do not hire DevOps engineers! Hire for cultural fit and aptitudes, not for skills. Break down silos. Ask for volunteers. Look for a pilot project. Select what works for you (but don’t Cherrypick). Define measurable outcomes for the whole team, not individuals. Set and communicate priorities. Allow failures. Acknowledge achievements. Empower people. Do not interfere.
- 21. 21 Grandma’s cooking tips for everyone Evangelize. Become a “DevOps Champion”. Persevere. Start small. Create awareness. Create demand. Prioritize and address pain points first. Proceed step by step. Continuously question processes, tools, architecture, organization. Share and spread. Prepare for rejection and failure.
- 22. 23 Grandma‘s cooking tips: Levels of maturity Level 1: Absent. • Monolithic software, waterfall model. Level 2: Practiced. • Individual teams apply some practices. Level 3: Consistent. • Enterprise wide standards. Level 4: Reliable. • Mentoring, best practices, knowledge transfer, coaching. Level 5: Scaled. • Institutionalized adoption, optimization of the practice itself.
- 23. 24 Grandma‘s cooking tips: Project timeline Stages: Consulting Mentoring Handover Autonomous
- 24. 25 Grandma‘s cooking tips: DevOps heatmap Module Phase Plan Code Build Test Release Deploy Operate Monitor Development process Agile Configuration management Cont. Testing Cont. Integ. Cont. Deploy. KPI Tools Microservices Containers OSS Relevance High Medium Low
Editor's Notes
- #26: Development process assessment Review of current processes and procedures. Comparison with past successful experiences. Possible improvement points are identified and further actions defined. Agile development Evaluate the current status of Agile methodologies adoption. Optimization actions are identified based on past experiences and industry best practices. Some of the topics reviewed are the following. Scrum methodology (Sprints, standups, planning, retrospect). Development procedures (SCR, feature branches, code reviews). Collaboration tools (Issue tracking, User stories, product management). Configurtion Management Automatize the provisioning and configuration of the software runtime environment. By using the appropriate tool stack we adapt the “Infrastructure as Code” paradigm. Operational aspects such as infrastructure deployment and configuration is written as code and procedures are automated. We increase speed of development, reliability, accountability and knowledge sharing. Continuous testing Reduce development iterations by providing developers continuous and quick feedback to their changes. Developers know when there is a problem with their changes as soon as they push them. Keep builds stable by only accepting changes that do not make tests fail. Continuous integration Increase software quality and reliability by continuously testing the integration of your components. Run heavy test suits and check the interaction between components periodically instead of waiting until release time. Run these tests in a separate environment as similar as possible to production to avoid “it works in my computer” problems. Continuous / Automated Delivery Reduce deployment time and increase reliability by removing manual steps in the release process. Introduce accountability by being able to check exactly what software is running in production. Allow to rollback to previous versions quickly in case of failures. Key Performance Indicators Identify valuable Key Performance Indicators that can be used to evaluate your processes and guide your decision making. Tool Chain Evaluate your current tool chains. Possible improvements are identified and cost/benefit calculations performed. Micro-services and Container Advice on how to use containers efficiently in product development and operation. Practical examples deploying applications using Docker in Kubernetes clusters. Examples of decisions made in the adoption of these technologies. OSS development, OSS usage Experience on how to contribute to Open Source Software. Open Source philosophy, community and tools.