Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Luiz Fernando Testa Contador - Aplicando DevOps em grandes corporações

359 views

Published on

Assunto que será abordado:
Por onde e como começar aplicar DevOps em grandes corporações?
Diferenças entre DevOps para Start-Ups vs Grandes Corporações
Principais barreiras a serem quebradas
Mudança de MindSet Corporativo
Principais ganhos para a corporação

Published in: Technology
  • Be the first to comment

Luiz Fernando Testa Contador - Aplicando DevOps em grandes corporações

  1. 1. Agile Trends 2017 Aplicando DevOps em Grandes Corporações Agile Trends São Paulo 2017 Luiz Fernando Testa Contador lcontador@ciandt.com
  2. 2. Who am I? #sobrinhas #F1 #senna #cerva#familia #Fé #amor #tennis #TechCareer #TI Jaú Campinas São Paulo
  3. 3. What is DevOps? (In different views) Is a new position ? or is a new department? Is a methodology? a philosophy? A concept? or a culture? Is a developer specialist who understands infra/operations? Or it is a sysadmin that have code develop skills? DevOps only works on start-ups or also fit on big corporation? Business/Process Dept RH/Hiring Dept Development/TI Dept All Dept #DevOps
  4. 4. Lets try choose the best answer for that
  5. 5. Certification Tools Role DevOps is NOT just ...
  6. 6. Source: xebialabs.com/periodic-table-of-devops-tools/ DevOps is NOT just tools ...
  7. 7. Enterprises have discovered DevOps and know the benefits of this transformation EnterprisesStart-ups Enterprises vs Start-ups ... ...
  8. 8. Infra/Ops Team Business Team Dev/Arch Team Q&A Team Security Team PM, SM, BI, Executives Owner Dev, Arch, DBAs, Spcist Q&A Security Analyst TI Analyst, SysAdmin Measured Goal Challenges to adopt DevOps in Enterprises Value Activated Feature Delivered Quality Metrics Security Vulnerability Stability Conflict of interest (each dept) Increase the Business Increase the Business Protect the Business Protect the Business Protect the Business DevOps is NOT just tools ...
  9. 9. Challenges to adopt DevOps in Enterprises Business Area - DevOps Applicability (Effort)CriticalSystems DevOps Applicability eCommerces Portals Websites Microservices Mobile Apps Hospital/Health Systems Financial/Main Systems Airplane/Traffic Systems Security Systems Legacy Systems Monolithic Systems Easy Hard
  10. 10. ciandt.com In such a dynamic scenario, large companies and their rigid structures have the challenge of answering a single question.
  11. 11. ciandt.com Is it possible to be big & agile? #yesewecan
  12. 12. How Enterprises can start? 1 - Culture changes start at the Top The implementation of DevOps is not simply about the fast deployment and IT department It must be treated as a company-wide transformation—one that incorporates process and governance considerations as well as technology-related ones.
  13. 13. How Enterprises can start? 2 - Change the team organization Business Team Dev/Arch Team Q&A Team Security Team Infra/Ops Team . . . . . . . . . . . . . . . . . . . . . . . . . . . Current scenario: ● Large Organization ● "Vertical" Departments ● Hard Silos and Legacy Systems
  14. 14. How Enterprises can start? 2 - Change the team organization New scenario: ● Make a Small Multi-Funcional Team ● Share de same physical location or incorporate video streaming ● Bring/Gather All Dept Representatives into the same agile team Business Goal Dev/Arch Goal Q&A Goal Security Goal Infra/Ops Goal Team 1 Team 2 Team 3 . . . . . . . . . . . . . . . . . . . . . . . . . . .
  15. 15. How Enterprises can start? 2 - Change the team organization (Avoid mistakes)
  16. 16. How Enterprises can start? 3 - Share Technical Skills ● Be an agent for change; ● Technical DOJOs; ● Hackatons and TechTalks; ● Create a Sandbox environment - Define a "Shared Play" area; ● Create a "DevOps Day" for the Company with more visibility as you can; ● Invest in External Events (workshops/summits/meetups/webinars)
  17. 17. ciandt.com 4 - Invest in Elastic Infrastructure and New Architecture How Enterprises can start? ● Microservices (avoid monolithics systems) ● APIs/Services (integrate different system) ● Containerization (Docker) ● Infrastructure as Code (Puppet, Chef, Ansible) ● Cloud (Public / Private) ● IaaS (OpenStack, AWS, Google, Microsoft Azure) ● Paas (OpenShift, IBM Bluemix, Cloud Faundry) ● SaaS (Google, Salesforce, Office365)
  18. 18. ciandt.com 5 - Higher frequency of deployments • Continuous Deployment (Avoid code stock) • Lower time to market (Reduce Lead Time) • Lower complexity and risk (Avoid Big Bang) • Blue Green Deployment / Feature Toggle (Reduce Down Time) How Enterprises can start?
  19. 19. 6 - Make all things visible for everybody How Enterprises can start? • Continuous Feedback (Prior/Easy defect identification) • Continuous Monitoring (Focus on the production environment)
  20. 20. 7 - Automate manual / boring process How Enterprises can start? Start automating manual process like: ● Status Reports ● Docs Requires ● Release Notes ● Manual Validation
  21. 21. 8 - Focus on tech career progression How Enterprises can start? Source: itigocloud.com
  22. 22. Continuous Integration -> Delivery -> Deployment -> OperationHow Enterprises can start? 9 - Start Small and with the Goal in Mind Define a MVP Concept (Minimal Viable Product) ● MVP 1 (Camp1) ○ Define a Small Team (New Non-Critical Project) ○ Create the first Microservices ○ Use Self Hosting (Virtualization) ○ Apply Continuous Integration ● MVP2 (Camp2) ○ Apply Continuous Delivery/Testing ○ Implement Feature Toggle ○ Use Cloud Hosting (IaaS) ● MVP3 (Camp3) ○ Apply Continuous Deployment ○ Implement Infra Auto-Scaling ○ End-to-End Monitoring Camp1 Camp2 Camp3 Camp4
  23. 23. Continuous Integration -> Delivery -> Deployment -> OperationHow Enterprises can start? 10 - Evaluate DevOps Maturity
  24. 24. CI&T - DevOps Maturity Evaluation Continuous Monitoring Continuous Deployment Continuous Testing Source Code Version Control Environments Build Automation Source Code Quality Unit & Acceptance Tests Automation Infrastructure Monitoring Infrastructure as a Code Culture Process Performance & Load Tests Automation Database Version Control Security Test Automation Platform Monitoring Application Monitoring Business Monitoring Continuous Integration Deployment Automation
  25. 25. DevOps Assessment Form ciandt.com CI&T - DevOps Maturity Evaluation
  26. 26. Nível 3 - IdealNível 0 Nível 2 - TargetNível 1 - Transição DevOps practices are not minimally enforced Some minimum practices apply, but there are essential practices not applied Essential practices are applied The most advanced practices on the market are applied Exemple: Build Automation Nível 1: - Build automatizada em um servidor específico - Controle de dependências (ex: maven, nuget, npm, bower) - Status da build visível (email-feedback do status da build e/ou monitor de build) Nível 2: - Build commit com testes unitários - Falhas nos testes unitários quebram a build - Build de commit rápida (ex: não ultrapassa 15 minutos) - Fluxo de integração controlado, utilizando pipeline ou equivalente Nível 3: - Tempo de build não demonstra aumento gradativo - Quando existe dependência e reuso entre módulos, os componentes do projeto são publicados em um repositório de artefatos (ex: nexus, artifactory ou equivalente) Nível 0: - Não completa o nível 1 Level and Criteria for each practice CI&T - DevOps Maturity Evaluation
  27. 27. Continuous Monitoring Continuous Deployment Continuous Testing Source Code Version Control Environments Build Automation Source Code Quality Unit & Acceptance Tests Automation Infrastructure Monitoring Infrastructure as a Code Culture Process Performance & Load Tests Automation Database Version Control Security Test Automation Platform Monitoring Application Monitoring Business Monitoring Continuous Integration Deployment Automation Continuous Monitoring Continuous Deployment Continuous Testing Source Code Version Control Environments Build Automation Source Code Quality Unit & Acceptance Tests Automation Infrastructure Monitoring Infrastructure as a Code Culture Process Performance & Load Tests Automation Database Version Control Security Test Automation Platform Monitoring Application Monitoring Business Monitoring Continuous Integration Deployment Automation Initial Evaluation Final EvaluationRoadmap Transformation CI&T - DevOps Maturity Evaluation
  28. 28. Luiz Fernando Testa Contador Technical Specialist lcontador@ciandt.com dudu.contador@gmail.com duducontador The Phoenix Project: The Phoenix Project tells the story of an IT manager who has ninety days to rescue an over-budget and late IT initiative. By Gene Kim, George Spafford, and Kevin Behr Luiz Fernando Testa Contador Luiz Fernando Testa Contador The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations By Gene Kim, Jez Humble, and Patrick Debois

×