DevOps. Deploy. Code Plan. Release. Operate. Build CI. Monitor. Identify

Size: px
Start display at page:

Download "DevOps. Deploy. Code Plan. Release. Operate. Build CI. Monitor. Identify"

Transcription

1 DevOps Code Plan Release Deploy Build CI Identify Monitor Operate

2 DevOps Amalgamation of people, processes and technology help you achieve your goals Knowing that technology in a nutshell is difficult to be absorbed, thanks to its infinite possibilities, seamless ways and means of integration with several technologies etc. Looking at far how we have come, new solutions are always being developed and are being utilised by several organizations, as to how far would it go and also, serving the best solutions possible. Operation A long time ago, when technologies were revamping or taking a new shape of its own, and when we all were looking at various forms of it, there were more queries to understanding the same and trying to simplify it. Some technologies were up-graded, some were fixed with newer versions and some were still being a part of the inception stage. That s precisely when the need for getting connected, or if we can say that various processes needed a common integrated platform and thus, this need gave rise to DevOps. In brief, DevOps is basically a complete set of practices, which help emphasize the complete collaboration and communication between the software development and operation s team, whilst automating the process of software delivery through structured processes and collaboration. Development DevOps Quality Assurance We study these Devops, more ahead in details as follows: As innovation, takes a complete new turn and speeds up the entire IT process, making industries prosper, one thing they need to be reminded is to become more and more agile. Over the years, the software development lifecycles have drastically moved on from waterfall to agile models of development. These improvements are moving downstream toward IT operations with the evolution of DevOps. IT organizations and the software development teams that deliver business critical systems, must be able to adapt quickly and respond to change in order to be successful and stay relevant. It is equally important to ensure operational systems and the services they provide are stable and available at all times. As we can rightly say - Implementing DevOps practices essentially requires a huge cultural shift in terms of People, Processes and Technologies who are involved in development, testing and operations. Many organizations encounter significant challenges when adopting DevOps, particularly when adopting it in legacy areas.

3 What exactly is DevOps? Patrick Debois, who s often called the father of DevOps, coined the word DevOps in As the word depicts, it was formed by combining two words: development and operations. DevOps is a collaborative way of developing and deploying software. DevOps is a set of principles and practices - both technical and cultural - that can help organizations deploy better software, faster. While it is not a fixed methodology, automation and a collaborative culture are the foundation for accepted DevOps practices such as: DevOps is an approach based on agile and lean principles in which business owners, development, operations, and quality assurance team collaborate to deliver software in a continuous stable manner DevOps is an environment that promotes cross practicality, shared business tasks and belief DevOps is a movement that improves IT service delivery agility DevOps is a culture that promotes better working relationship within the company DevOps is a set of practices that provides rapid, reliable software delivery Collaborative Development Increased collaboration between teams Continuous Integration & Continuous Testing Integration of software testing with deployment and operations Continuous Release and Deployment Increased delivery speed and frequency Continuous Monitoring Improved quality by monitoring production performance

4 Why do we need DevOps to run our businesses? Well, you can easily argue on the fact stating that since when did technologies come into the picture of being responsible for businesses to grow and expand? Or let us frame in this way will DevOps be a game changer when it comes to the success of organizations? And the answer is YES! It does and hence DevOps not only reduces the gap between the ongoing development and operations team, but also breaks the barriers between the development and operations team, creating better outputs. What Drives the Need for DevOps? Performance If we actually look at the results or the report findings and the actual benefits of using DevOps as an important tool, one can easily say that DevOps enables continuous software delivery, easing out minimal complex difficulties, resolving problems faster. This essentially means that you can deploy faster and more effectively in more stable operating environments and add value rather than just fixing or maintaining. The need for greater collaboration between development and operations terms A greater need for simultaneous deployment across different platforms Pressures from the business to rlease apps more quickly to meet customer demand or enter new markets Need to improve the end customer experience 47% 41% 41% 39% Security Organizations that adopt DevOps practices are known to have better information security. Higher performance is not only the core output in the culture of DevOps, but also as mentioned in the 2016 State of DevOps Report, which mentions - Organizations that integrate information security objectives into daily work spend 50 % less time remediating security issues, than low performers, which has a positive impact on IT performance and security outcomes. The increasing use of mobile devices (smartphones/tablets) The increasing need to develope or deploy cloud based applications An increasingly complex IT infrastructure that is part physical, part virtualised and part cloud Need to reduce IT costs 35% 31% 28% 16% Source : CA.com

5 Difference between Agile & DevOps Agile DevOps Agile is about software development DevOps is about software deployment & management Test as early and as often as possible Testing is a continuous process Automate testing as much as possible Automate almost everything Continuous integration and testing is a step forward Continuous integration and testing is mandatory Potentially shippable code at the end of a sprint Potentially shippable code following every integration

6 Project Execution Methodologies Waterfall Design Code Test Deploy Agile Design Code Test Code Test Code Test Deploy DevOps Design DevOps AGILE Start Coding End Coding Release Production Support Development Testing Operations

7 How does DevOps work? Culture Focus on People Embrace Change & experimentation Automation Continuous Delivery Infrastructure as Code Lean Focus on producing value for the end-user Small batch sizes Measurement Measure everything Show the improvement Sharing Open information sharing Collaboration & Communication DevOps combines the best possible Develops and verifies against production-like systems Reduces cost/time to deliver - Deploy often, deploy faster with repeatable, reliable process Increases Quality - Automated testing, Reduce cost/time to test Reduces Defect cycle time - Increase the ability to reproduce and fix defects Increases Virtualize Environments utilization Reduces Deployment related downtime Minimizes rollbacks

8 Trends of DevOps As companies seek to drive digital business by delivering new software applications and features more quickly, they look to both DevOps and Cloud as key enablers. DevOps is now being adopted by 74% of the organizations, up from 66 % in DevOps Adoption Up in 2016 Enterprise vs. SMB DevOps Adoption % 16% 10% Enterprise 81% 12% 7% % 19% 15% SMB 70% 19% 11% Adopting DevOps Not adopting Don t know Adopting DevOps Not adopting Don t know Source: RightScale 2016 State of the Cloud Report Source: RightScale 2016 State of the Cloud Report Don t know Not adopting DevOps 7% 21% Adopting DevOps company-wide 12% Adopting DevOps for projects or teams 29% 31% Adopting DevOps for BUs or divisions

9 DevOps Where it can be implemented Automated build & testing 68% Configuration management CI/CD Monitoring and metrics 64% 63% 62% Collaboration between Dev & Ops Infrastructure as code Cloud application management 49% 54% 53% Security & compliance 41% Containerization 36% Micro service management 29% High performance activities What activity or activities makes your IT org high-performing? 38% 53% 66% 54% 46% 38% Engineers can self-service environment build needs We follow continuous integration and continuous delivery We automate a lot of manual processes Out IT responds rapidly to the needs of the business We release software often IT provides what is requested on time and on budget

10 Mobinius Maturity Model Key Achievement People Sustainable Environment Process Techology Continuous Delivery Quality Scripting Automation 8C s of DevOps Continuous Deployment Manual Continuous Testing Continuous Monitoring Continuous Governance Communication Collaboration Controlled Process Continuous Integration

11 CONTACT we believe in delivering highly automated software deployment solutions, evolving as rapid as your requirements. By adopting DevOps best practices, organisations can considerably improve the value produced by its business. Visit for more details and get in touch with us at Copyright 2017, Mobinius and/or its All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.