Entrega Contínua - 2º Encontro Rational de Desenvolvimento de Software
•Descargar como PPT, PDF•
1 recomendación•1,013 vistas
O documento discute a entrega contínua de software na prática. Apresenta os desafios em adotar DevOps nas empresas, como ambientes heterogêneos e desenvolvimento em silos. Defende que DevOps promove a inovação através do feedback contínuo entre desenvolvimento, testes e operações. Demonstra ferramentas da IBM como o UrbanCode e o Jazz.net para automatizar a implantação e release de aplicações.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a Entrega Contínua - 2º Encontro Rational de Desenvolvimento de Software
Similar a Entrega Contínua - 2º Encontro Rational de Desenvolvimento de Software (20)
Más de Felipe Freire
Más de Felipe Freire (10)
Entrega Contínua - 2º Encontro Rational de Desenvolvimento de Software
- 1. © 2012 IBM Corporation 2º Encontro Rational de Desenvolvimento de Software Building better software Entrega Contínua de Software na Prática Felipe Freire – pfreire@br.ibm.com 2º Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 – São Paulo
- 2. © 2013 IBM Corporation 2o Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 2 Agenda DevOps Entrega Contínua Demonstração –Cenário de Entrega Contínua com ferramenta IBM
- 3. © 2013 IBM Corporation 2o Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 Inovação através de software é um diferencial competitivo 3 86% Acreditam que a entrega de software é crítica ou muito importante 25% Lidam com software com eficiência Mas apenas… Source: “The Software Edge: How effective software development drives competitive advantage,” IBM Institute of Business Value, March 2013 69% superam seus concorrentes ineficientes Das eficientes
- 4. © 2013 IBM Corporation 2o Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 A ausência da entrega contínua impacta o negócio como um todo Costly, error prone manual processes and efforts to deliver software across an enterprise CHALLENGES Upgrade risk due to managing multiple application configurations and versions across servers Slow deployment to development and test environments leave teams waiting and unproductive DESAFIOS Operations/ Production Development/ TestCustomers Business Owners Software glitch costs trading firm Knight Capital $440 million in 45 minutes A bad software upgrade at RBS Bank left millions unable to access money for four days New Zealand’s biggest phone company, Telecom paid out $2.7 million to some 47,000 customers who were overcharged after a software glitch
- 5. © 2013 IBM Corporation 2o Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 Desafios em adotar DevOps nas empresas Ambientes heterogêneos Múltiplas tecnologias, múltiplos fornecedores Desenvolvimento e implantação em silos Segregação Dev – Ops Equipes distribuídas Modelos de subcontratação (terceirização) Water-Scrum-fall 5 Heterogeneous Environments Public Cloud Private Cloud Data Warehouse Mainframe Enterprise Service Bus Directory Identity File systems Collaboration Mobile App Routing Service Third-party Services Portals Content Providers EJB Shared ServicesArchives Business Partners Messaging Services
- 6. © 2013 IBM Corporation 2o Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 Diferenças entres os ambientes de DESENV e PROD causam falhas Backlog de entregas que o tipe de Ops não consegue lidar Processos manuais (tribais) que não são repetítiveis (ou rápidos) Falta de feedback e de métricas de qualidade leva a falhas nos objetivos Daily Build Monthly Delivery Quem fez da última vez? O Davi… Mas ele não está aqui… Dev Prod Cenários (exemplos) de dificuldades
- 7. © 2013 IBM Corporation 2o Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 77 Ciclo de vida DevOps Operações / Produção Desenvolvimento e Testes Clientes Áreas de Negócio Inovação, Feedback e Melhorias contínuas Acelerar a entrega de Software Equilibrar velocidade, custos, qualidade e riscos Reduz o tempo para feedback do cliente
- 8. © 2013 IBM Corporation 2o Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 8 Desenvolver e testar em ambientes similares ao de produção Desenvolver e testar em ambientes similares ao de produção Implantações frequentes e iterativas Implantações frequentes e iterativas Processo de implantação confiável e repetitivo Processo de implantação confiável e repetitivo Monitoração contínua e validação de características operacionais de qualidade Monitoração contínua e validação de características operacionais de qualidade Ciclos de feedback rápidosCiclos de feedback rápidos Pessoas Processo Ferramentas Pessoas Processo Ferramentas
- 9. © 2013 IBM Corporation 2o Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 DevOps na prática no Jazz.net 9 https://jazz.net/products/devops/whats-happening#activity
- 10. © 2013 IBM Corporation 2o Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 Entrega contínua corporativa – Enterprise continuous delivery INTERMEDIÁRIO Build no commit Repositório de dependências Configuração segura INICIAL Auto-serviço de build Builds noturnos Armazenamento dos artefatos de build BÁSICO Scripts de build Máquina de build AVANÇADO Builds ativados por gatilhos Cluster de build EXTREMO Build a partir de snapshots de VM Commits com verificações (gates) INTERMEDIÁRIO Auto-serviço para Teste e Produção Processos para todos ambientes padronizados INICIAL Auto-serviço para implantar em Teste Implantações autom. no 1’ ambiente Implantações padron. BÁSICO Scripts de implatação AVANÇADO Promoção entre ambientes verificada por testes Implantações complexas banco de dados e multi-camadas EXTREMO Implantações contínuas para Produção INTERMEDIÁRIO Alguma análise estática Testes funcionais automatizados norturnos INICIAL Os testes mais importantes executados em tempo de construção BÁSICO Alguma automação de Testes AVANÇADO Alta cobertura de código Verificações de segurança Testes manuais baseados em risco EXTREMO Implantações contínuas para Produção BUILDIMPLANTAÇÃOTESTES http://www.urbancode.com/html/resources/white-papers/Enterprise_Continuous_Delivery_Maturity_Model/
- 11. © 2013 IBM Corporation 2o Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 Urbancode, an IBM Company 11 Years Build, Release and Deployment Experience Global Customers Enterprise scalability, security, compliance and automation Training, consulting and implementation services Based in Cleveland, OH “One key benefit of UrbanCode is how quickly it can be implemented and used for deployments.” 11
- 12. © 2013 IBM Corporation 2o Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 12 Onde estão as mudanças? App. Con gfi . App. Mid. Con gfi . Mid. OS Con gfi . OS Hardware ARA: uDeploy Layers Change Frequency Tools RAF / Mid-vision Chef / Puppet Cloud / SCP / VMWare Aplicação (binários, configurações, schemas) Plataforma (middleware, banco de dados, serviços comuns) Infraestrutura (Sistema operacional, rede, armazenamento, segurança)
- 13. © 2013 IBM Corporation 2o Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 13 uDeploy – Automação do Deploy Implantação de aplicações entre ambientes Mapas (blueprints) para modelar aplicações complexas Gerenciamento de configurações por ambientes Conformidade: auditoria e segurança Facilidade de uso: designer de processos Inventário: o que está aonde Artefatos Versionados Ambiente de Qualidade Ambiente de Produção Ambiente de Desenvolvimento Artefatos Artefatos Artefatos Executado em Executado em Executado em Deploy ou Rollback Deploy ou Rollback Deploy ou Rollback Blueprint de Aplicação
- 14. © 2013 IBM Corporation 2o Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 uDeploy trabalha em ambientes heterogêneos Fontes de deploys – Build servers – Source control tools – Maven repositories Integração IBM – RTC / ClearCase / Synergy – WebSphere Application Server – MQ – Message Broker Outras plataformas Java – WebLogic, Tomcat, Jboss, etc Gestão de Qualidade e Testes – QualityCenter – ServiceNow Plataforma Microsoft – IIS – SharePoint & Biztalk Infraestrutura – Clouds Públicas ou Privadas – Balanceadores de carga – Bancos de dados 9
- 15. © 2013 IBM Corporation 2o Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 15 uRelease – Planejando e organizando entregas uRelease provê: Planejamento do release Acompanhamento da execução Comunição de status Alocação de ambientes à releases Associa release complexos ao desenvolvimento Simplesmente porque planilhas são horríveis ou apenas normais...
- 16. © 2013 IBM Corporation 2o Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 Automação e Gestão uDeploy uRelease Automação do Release de Aplicações Automatiza a implantação Desenho visual do processo de implantação Ações automatizadas através de plugins para servidores de aplicações, servidores web, dispositivos de rede, bancos de dados, etc. Modelar aplicações, ambientes e alvos de implantações Gerenciamento de Releases Reforçar barreiras de qualidade para ambientes Orquestrar mudanças que impactam várias aplicações Gerenciar mudanças na infraestrutura em conjunto com as aplicações Status em tempo real para implantações de longa duração Acompanhar a alocação de ambientes para releases
- 17. © 2013 IBM Corporation 2o Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 17 Application Release Management Cloud Provisioning Application Deployment Automation Conjunto de soluções para suportar DevOps Rational Team Concert (CLM) Rational Test Workbench SmartCloud Control Desk Rational Build Forge Jenkins SmartCloud Continuous Delivery SmartCloud Provisioning SmartCloud Orchestrator Rational Automation Framework Chef
- 18. © 2013 IBM Corporation 2o Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 18
- 19. © 2013 IBM Corporation 2o Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 19
- 20. © 2013 IBM Corporation 2o Encontro Rational de Desenvolvimento de Software – 24 de setembro de 2013 20
Notas del editor
- Author Notes: This is the IBM Rational standard template for internal and external Rational presentations. It was created in Microsoft PowerPoint Standard Edition 2003. This template is also converted and provided in Lotus Symphony v3.0. Additional IBM Rational presentation assets and resources can be found on Rational’s Managing the Brand W3 Intranet site : https://w3-03.ibm.com/software/marketing/marksite.nsf/AllMarketingPages/Brand-Rational-rt_rtb?opendocument?opendocument IBM Rational Brand Overview slides, as well as other important brand messaging assets, can be found on the Rational Brand Content Page : http://w3-103.ibm.com/software/xl/portal/content?synKey=R789607U42052O71 If internal presentations are confidential, please add: “IBM Confidential” to the slide masters Select: View / Master / Slide Master and add “IBM Confidential” to both the title master and slide master Use sentence case capitalization for presentation titles, slide titles, category labels and bullets: Format / Change Case / Sentence Case. Initial capitalization is limited to our products and offerings. Applying this template to your existing presentation Task Pane needs to be viewable: Select View / Task Pane Select Slide Design - Design Templates from the Task Pane pull-down menu Select “Browse” at the bottom, and find “Rational_Standard_Template.pot” on your hardrive and click Apply Please note that not all slides will reformat appropriately once template is applied. Some reformatting will be necessary Printing your presentation on a black and white printer Prior to printing your presentation, view the slides in grayscale mode: Select View / Color/Grayscale / Grayscale Select problem graphics or text and right-click and select Grayscale Setting Select the grayscale setting that displays the problem graphic/text the best Note: Changing the greyscale setting does not affect the color view Return to Normal View by selecting View / Color/Grayscale / Color
- Author notes: Note that the contents/agenda items are written in sentence case. Initial caps are reserved for IBM-branded solution names. When referring to IBM products, use the correct full name, (e.g., IBM Rational ClearCase). Title the page “Table of contents” if the document is meant to be read or is a “leave behind.” Use “Agenda” if the document will be presented formally This page should appear at the beginning of each section, with the highlighted section appearing in blue and bold
- Main Point: We know organizations have a gap between the software delivery capabilities they need to succeed and the ones they have in house currently. Successful organizations know that when they improve their abilities in this area, they increase their success. In fact a recent IBV study where organizations self-reported that... Insights from 435 executives in 58 countries, spanning 18 industries 85% realize and reported it is important to critical Only 25% say they are able to fully leverage software delivery effectively So there is a gap -- but when companies that can close the resulting execution gap stand to benefit. Almost 70 percent of the companies currently leveraging software development for competitive advantage outperform their peers from a profitability standpoint TRANSITION – so there is a huge opportunity for our clients to close that gap…let ’s move to the next slide and talk about how -------------------------------------------------------------------------------------------------- Note: Outperformers were determined by a self-assessment of profitability against peers in the industry, ranging from 1 (Significant underperformers) to 5 (Significant outperformers) Significant outperformers were ranked as a 5, Average performers a 3-4 and Underperformers 1-2 new Rational/WebSphere IBV Study "The Software Edge - How effective software development drives competitive advantage" This study examined the correlation between software delivery competency and industry competitive advantage Insights from 435 executives in 58 countries, spanning 18 industries Roles included executives at director level and above in IT and other software organizations Software delivery refers to all areas of development, operations, and support within IT and other development / engineering organizations “ There was 54% of the companies who said they believe software is critical and 32 percent who called it moderately important – so that’s 86 percent of the respondents say software is either critical or moderately important and that points to the need for better tooling for software development and delivery.” said Randy Newell, director of capabilities marketing for IBM Software Group with a focus on the Rational brand.
- http://gizmodo.com/5931284/software-glitch-costs-trading-firm-440-million-in-45-minutes http://www.theregister.co.uk/2012/06/25/rbs_natwest_what_went_wrong/ http://business.scoop.co.nz/2011/10/19/telecom-makes-2-7m-settlement-for-incorrect-meter-readings/
- Main Point: So the idea is to build a continuous delivery pipeline , from ideas through to delivery. Products, services, apps, and infrastructure flow through the pipeline as software and related artifacts, This way, you can get to the speed needed to meet those ever-increasing rates of market shifts and customer demand. You need to consider and leverage to your best use – Mobile, Cloud, Big Data, Social, etc… And there are key intermediate stages of specialized tasks in the delivery pipeline workflow which you can associate as discrete sources of customer pain that can be entry points for targeted solution capabilities – Develop and Test, Release and Deploy, Monitor and Optimize. How do they address the challenges of today’s complexities and get to market faster with a quality product, service or application? The most forward thinking companies will establish an enterprise capability for accelerated delivery of software that enables them to seize market opportunities and reduce time to customer feedback, improve governance while balancing quality and cost. They can do this by taking a lean and agile approach but expanded AND fully automated across an expanded lifecycle that includes customers, LOB / business owners, development / test and operations / production and really focus on achieving: Accelerate Software Delivery Expanding collaboration to include customers, LOB and others to eliminate organization silos Balance speed, cost, quality and risk Automating manual processes across delivery lifecycle to eliminate waste/delays and compliance tracking Reduce time to customer feedback Enabling a customer feedback loop for continuous improvement So let’s look at an IT team that is leveraging a DevOps approach: Customers using new apps pass requirements to the business, which clarifies customer need Business constantly passes requirements to development team, which builds, tests, and demos code Development continuously releases new apps to operations, which continuously monitors them for effectiveness TRANSITION… So this approach to DevOps is ideal but how does an organization get from where they are today to this “new normal,”
- 2001 we delivered the first Build Management Server, in 2006 we extended build and delivered AHP, the first Continuous Delivery Server Many of our customers look to us for services around best practices in deployment, CI, CD, and release orchestration – we have the most experienced services and support team in the business We have been profitable for the last 10 year Good opportunity to tell one “story” about the value a customer gets from our products
- Author Note: Optional Rational slide. Graphic is available in English only.
- Author Note: Optional Rational slide. Graphic is available in English only.
- Author Note: Mandatory Rational closing slide (includes appropriate legal disclaimer). Graphic is available in English only.