DevOps: Why you should care Bruce Vincent Senior Technology Strategist and IT Architect

DevOps: Why you should care and how we’re approaching it…rev. 0.9 Bruce Vincent and Scotty Logan, Stanford University

How do we reconcile?... Continuous functional improvement desired Need for efficient deployment workflow Platform variations desire for portability Expectation of zero service disruption

Service on outage windows “No, Thursday doesn’t work… How about never? Does never work for you?”

State of the art, 2011 (Cloud implementation) VM Shared or Separate DBs “sites” service Version upgrades can be done site by site, as desired All resources discrete, no spillover impact on other websites Only run number of instances needed Supports auto-scaling Some waste on individual VM level Proprietary stack Inherent geo-diversity Essentially limitless computing resources Audit-worthy platform Unlimited, geo diverse physical servers VM AWS Hypervisor Cluster Magic OS Drupal OS Drupal OS Drupal OS Drupal

Containers are a game-changer Application consistency Portability Rapid prototyping, testing, deployment Disposable servers

Version upgrades can be done discretely, tested and staged Orchestration builds entire environment automatically Container OS is tiny and disposable, so almost no sysadmin or patching is required Very cost effective and no hypervisor overhead Docker supported on AWS, Google Compute, OpenStack and soon Microsoft Azure Any Docker Container Platform State of the art, 2015 (Containerized computing)

Your whole stack as code Programming professionals are driving DevOps as new standard in software engineering practice. Continuous Integration Blue-Green deployment You get more productivity from your developers with DevOps As a nice additional benefit, good developers want to work in your shop.

What’s enabling our DevOps Docker, CoreOS, Jenkins, Puppet, Terraform