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)
“sites” service
Drupal
Drupal
Drupal
Drupal
OS
OS
OS
OS
Shared or Separate DBs
VM
VM
VM
VM
VM
VM
AWS Hypervisor Cluster Magic
Unlimited, geo diverse physical servers
• 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
Containers are a game-changer
•
•
•
•
Application consistency
Portability
Rapid prototyping, testing, deployment
Disposable servers
State of the art, 2015
(Containerized computing)
• 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
Any Docker Container Platform
• Docker supported on AWS,
Google Compute, OpenStack and
soon Microsoft Azure
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