Maintenance is Dead! A path to a New Paradigm

Transcription

1

2 Maintenance is Dead! A path to a New Paradigm

3 Ali Hashmi Director - Expresscommerce

4 Today s Plan Maintenance is Dead! The paradigm Shift Your website is a living thing Role of DevOps in website Maintenance Our Journey

5 Maintenance is Dead!

6 What do you mean it s not fixed yet?? I told him we needed that new button three weeks ago!!

7

8 Maintenance is Dead the way it is currently practiced Maintenance is a chore, even a hassle. Reactive instead of proactive Working in a Silo approach Assigned to the B Team Lack of familiarity with project history Lack of communications with PM, Account Manager or original Dev team Not integrated with marketing, BA or other departments Interruptions in service or features Random approach with no guiding methodology

9 Innovate or die!!

10 Maintenance reframed becomes an opportunity.

11 New Paradigm Cultivate Your website is a living Entity

12 ...Maintenance reframed becomes an opportunity. Don t be reactive Be proactive

13 ...Maintenance reframed becomes an opportunity. Breaking Barriers A new mentality and corporate culture that makes development work in an integral way with operations

14 ...Maintenance reframed becomes an opportunity. Traditional Approach Continuous Delivery Risk/Cost V1.0 Release V2.0 Release Risk/Cost Release with Ease Time Keep a reactive approach to maintenance and you ll see a periodic increase on costs and risks. Reframe it to continuous and smaller releases and your development risk and cost will remain constant Time

15 DevOps A working philosophy to handle Change better, faster and cheaper

16 ...Maintenance reframed becomes an opportunity. Keyword: DevOps Source: Google Trends

17 DEVOPS Opposing or Complementary? Systems Thinking - Holistic vs Silos - More Visibility - Process vs Individual Continual Learning - Iterate and Learn - Experiment and fail fast Feedback - Interdependence - Mutual Feeds - Meta culture Socio-technical system - A mindset change - Common objective

18 CAMS John Willis & Damon Edwards

19 Adoption Barriers 0% 10% 20% 30% 40% Organizational Culture Lack of Integrated Development and Operations Technical Hurdles Lack of Understanding Business Readiness Source: DevOpsGuys.com

20 What DevOps is not? DevOps is not only for born on the web companies DevOps is not only for internal teams and not for outsourced partner DevOps only works in cloud environment DevOps is not only about communication DevOps doesn t mean that you are doing continuous change deployment

21 "The hardest part is getting the business culture right, particularly when trying to transplant these DevOps ideas into a larger company. You may have to deal with stakeholders at different levels who may not like this idea of relinquishing some power or giving people access to systems they previously haven t had" Jon Cowie, Etsy

22 From our journey Using DevOps to Reach Goals

23 DevOps challenges in maintaining your site Issues Staging mirror Production Works on development but not on staging/production Manual work in moving changes across environment Which features to move which not to? Are we doing enough testing? Solutions Use tools for Continuous integration and Continuous Delivery No manual interaction Builds should be self contained Use Feature toggle Unit tests, Integration tests and Regression tests

24 Continuous Integration Code Done Unit Tests Integrate Acceptance Test DEPLOY TO PRODUCTION AUTO AUTO AUTO MANUAL Continuous Delivery Code Done Unit Tests Integrate Acceptance Test DEPLOY TO PRODUCTION AUTO AUTO AUTO AUTO

25 Adopting DevOps Bringing Development and Operations together Get the process on the paper Identify your constraints Identify roles and fill in the gaps Develop a feedback loop Team Accountability vs Individual Automation Development environment setup Streamline build process Staging and Production environments Establish Metrics to monitor and provide feedback Dev + Ops Code Quality More Code Uptime, Security Delivering new capabilities quickly and safely

26 Think Big, Start Small, Move Fast - Automation

27 DevOps Tools 2016 Trends Overall DevOps adoption rises from 66 to 74 percent, with enterprises reaching 81 percent.

28 CI/CD Tools that works well with Magento Develop, Build, Test, Deploy and Release Docker Vagrant Jenkins Travis CI Puppet Chef Bamboo Selenium And the list goes on Monitor Development Deploy Build Test

29 Tools Selection

30 Who is Docker For? It is designed to benefit both developers and system administrators. Developers:- Can focus on writing code without worrying on which platform application will run on. No worry of Dependencies. System Administrators:- (Infrastructure as a code) Docker gives flexibility and potentially reduces the number of systems needed because of its small footprint and lower overhead

31 Features of Docker and Docker registry Lightweight Containers running on a single machine sharing same OS Provides instant start, efficient use of RAM. Images are constructed from layered filesystems so they can share common files, making disk usage and image downloads much more efficient. Open Standards Containers to run on all major Linux distributions and Microsoft operating systems. Security Containers isolate applications the underlying infrastructure to provide additional security layer. Docker registry Docker registry is used to store docker images from where you can pull and push images from docker on servers. Several hundred Magento repository images available on

32 Building and Testing - Jenkins An Open source Mature Continuous Integration tool with 1000s of plugins Database Dump Media Directory

33 Building and Testing - Jenkins Deployment Pipeline

34 Continuous Testing Static Code Analysis (php-pmd, php-depend, codesniffer, etc) Unit Tests (php-unit, MTF (Magento Testing Framework)) Integration Testing (MTF, conflict checker, link checker, etc) Stress Test (Jmeter, Selenium, etc)

35 Continuous Monitoring Monitoring is essential to cultivate your site Monitoring provides data to Development, Operations, QA, lines of business personnel and other stakeholders. Monitoring should be done in all environments from development to production Quality metrics should be defined in the planning phase Insights and alerts You can t manage what you can t measure

36

37

38 Knitting the DevOps Fabric Begin with the end in Mind Start with People Identify Burning areas Don t overkill with tools Don t Maintain --- Cultivate

39 Thank You Visit us at: