SlideShare a Scribd company logo
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. |
What is “DevOps” Anyway?
Kelly Goetsch
Director, Product Management
Cloud Application Foundation
2015
A Pragmatic Introduction
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion of Oracle.
2
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Agenda
3
1 What is DevOps? And why now?
2 How to Change Your Culture
3 How to Change Your Technology
4 Case Study: Oracle’s Internal Embrace of DevOps
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Dev and Ops Constantly Argue
“Code is written...it’s your problem now”
4
Hey Ops - Here’s our
code...good luck!
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Modern DevOps = Culture + Technology Movement
Culture is what’s behind DevOps; technology is the enabler
5
Culture
Technology
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Core DevOps Principles
6
Cultural movement enabled by technology
Paid to add new features
Dev Ops
DevOps
Paid to keep system
stable, fast and available
New goal:
Add new features and keep the
system stable, fast and available
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Characteristics of DevOps Movement
7
Principles have been around for decades
Agile
Methodologies
Open Culture
Cloud-like
Infrastructure
Heavy Automation
Open Source
DevOps
Movement began in startup
community. Use of open source seen
as integral but not technically
necessary
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Old Culture and Expectations Don’t Work!
Commonly overheard in offices
8
It’ll take us three
months to build you
a development
environment
I have to stay up
all night to do a
build
The new switch we
need is sitting on
the loading dock
That code change
will have to wait
for our monthly
build
Uh...that’s not my
problem. Go talk
to Ops
Why does your
code always break
my infrastructure?
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
DevOps Tenet #1: Culture
9
DiscussRespect
Avoid
Blaming
“Done”
Means
Released
•Dev respect for ops
•Ops respect for dev
•Don’t stereotype
•Don’t just say “no”
•Don’t hide things
•Ops should be in dev discussions
•Dev should be in ops discussions
•Shared runbooks/escalation plans
•Ops should give devs access to
systems
•No fingerpointing!
•Dev’s responsibility
ends when it’s in
production
•“Throwing it over
the wall” is dead
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
DevOps Tenant #2: Technology
10
Shared
Version
Control
Infra as
Code
One Step
Build/De
ploy
Don’t Fix
Anything
•Use config mgmt to
build environments
•Scripts checked in
and managed as src
•Single system for code and build
artifacts
•Every time someone commits a
change it triggers a build and
automated build verification tests
•Ship trunk
•Enable features through flags
•One button build/deploy
(manual)
•Scheduled builds/deploys
•If verification fails, stop and alert
•If something breaks,
re-deploy. Don’t fix
•Fix environment
setup scripts
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Faster Time-to-Market
• Increase frequency of
releases
• Increase accuracy of
releases - avoid downtime
• Reduce the time it
actually takes to perform
a release
Cost
• Automate what was
previously done manually.
Reduces OPEX
• Prevent humans from
making costly errors
• Reduce downtime, which
saves money
11
Focus on Business Value
• Allow high value
employees to focus on
higher value activities
• Nobody benefits from
doing low value activities,
like setting up
infrastructure
Business Value Is Driving DevOps
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Time
• Longer time to market
(initially) due to work
required to automate
• More builds / faster time-
to-market for individual
features
• Lower MTTR because
problems are fixed by
rebuilding
• Higher MTBF due to
increased accuracy
Cost
• High up-front costs due to
automation work
• Low ongoing costs
because routine
operations is automated
• Fewer employees wanting
more pay - 10x
developers want 10x pay
• Lower capex, higher opex
as workloads shift to
cloud
12
Culture
• Continues to empower
developers
• Automation increases
operational efficiencies
• Distracts developers from
developing code
• Movement eschews
“rockstars” but that’s
naturally what happens
DevOps Implications To Business
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Agenda
13
1 What is DevOps? And why now?
2 How to Change Your Culture
3 How to Change Your Technology
4 Case Study: Oracle’s Internal Embrace of DevOps
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
How to Build a Successful DevOps Culture
14
DiscussRespect
Avoid
Blaming
“Done”
Means
Released
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Build Respect
• Developers should respect Operations
• Operations should respect Developers
• Don’t just say “no”
• Don’t stereotype!
15
Because the
site breaks
unexpectedly
Because
nobody tells
them anything
Because they
say “no” all
the time
Ops Stereotype
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Discuss
• Don’t hide things! Open communication
on both sides
• Operations should be in Developer
discussions
• Developers should be in Operations
discussions
• Build shared runbooks/escalation plans
• Operations should give Developers direct
access to systems
16
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Avoid Blaming
• No fingerpointing!
• Development should have enough
Operations culpability to share the
blame in an outage
• Operations should have enough
Development culpability to share the
blame in an outage
17
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
"Done" Means Released
• The “throwing it over the wall to ops” model is dead
• Development needs to be involved with operations
• Operations needs to be involved with development
• Joint success/failure
18
Development
Operations
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Steps Required to Change Culture
19
 Hire technical people who are skilled in DevOps
 Set up training for DevOps skills
 Bring in consultants to help get started
 Put Dev + Ops people under same line-level managers
 Change the way you measure/reward performance
 Flatten org chart to reduce fiefdoms
 Let Dev + Ops collaborate to find solutions
 Let Dev + Ops jointly pick tools. Limit corporate mandates
 Don’t restrict the choice of public cloud solutions
 Sponsor teambuilding events
 Give Dev + Ops common goals to work towards
 When there's a failure, don't dwell on Dev or Ops failure
Build Trust
Bring In New Blood
Align Interests
Empower Change From
the Bottom Up
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Change Your Organization’s Structure
Incentives drive behavior
20
CIO
VP of
Operations
Developer
VP of
Development
Layers of
Middle
Management
Layers of
Middle
Management
Sys Admin
CIO
Developer
VP of Product
Layers of
Middle
Management
Sys Admin
Report to same manager. Incentivized to
work together to develop and release
Incentivized to
innovate and release
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Actively Build Trust
21
Trust is the #1 ingredient to a successful DevOps culture
Dev + Ops + Social Activity Outside Work + Time = Trust
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Agenda
22
1 What is DevOps? And why now?
2 How to Change Your Culture
3 How to Change Your Technology
4 Case Study: Oracle’s Internal Embrace of DevOps
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
How to Use a Technology to Enable DevOps
23
Shared
Version
Control
Infra as
Code
One Step
Build/De
ploy
Don’t Fix
Anything
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Infrastructure as Code
24
Manage it as you would any other source code
Base Image
Install Binaries
Configure Software
Make Software Work Together
Patch/Push Config Changes
Step 1
Pick a Tool
Step 2
Script your environment
Step 3
Run your scripts against all hosts
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Humans doing anything manually will introduce errors
Consider Disabling SSH Access
This could alienate ops people, however, as it shows a lack of trust
25
Possible solution: Remove each user’s shell
• All changes should be scripted and QA’d
– This prevents one-off changes (and errors)
– Emergency fixes can still be pushed as required
• Users can still SFTP to retrieve log files
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Shared Version Control
• Single system for code and build
artifacts
• Every time someone commits a
change, consider triggering a
build + automatic verification
tests
• Always ship trunk!
• Enable features through flags
Surprisingly not well adopted
26
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
One Step Build/Deploy
• Manual one button
build/deploy
• Scheduled builds - every
day, every week, etc
• Builds triggered by code
checkins
• If post-build validation fails,
report it
Set it and forget it
27
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Popular DevOps Technology
Remember: You can't get DevOps by buying a single product
28
 Ansible
 Jenkins / Hudson
 Rundeck
 Git
 Perforce
 Subversion
 Ansible
 Puppet
 Chef
 SaltStack
 Gradle
 Jenkins / Hudson
 Robot
 Artifactory
 Nexus
 Docker
 Vagrant
Version Control
Build & Functional Testing Binary ManagementVirtualization
Continuous Integration
Continuous Delivery
Configuration Management
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Agenda
29
1 What is DevOps? And why now?
2 How to Change Your Culture
3 How to Change Your Technology
4 Case Study: Oracle’s Internal Embrace of DevOps
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Product Development IT (PDIT)
• 602 Exadata
• 383 Exalogic
• 69,290 Sun x86 servers
• 6,854 SPARC servers
• 1,768 Sun ZFS appliances
• Thousands of other systems
30
Supporting enterprise, development IT, cloud and managed hosting at Oracle
924 Oracle Products
135,000 Employees
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
How Did PDIT Improve Efficiency by > 2x in 18 Months?
Culture changes enabled by technology
31
powered by
powered by
Culture
(Campbell Webb, Sr. VP, Oracle)
+ +
Cloud
The Same Products Oracle Sells
Infrastructure
Automation
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Oracle Cloud is Provisioned Using Chef
Database
Services
Java
Services
Analytics
Services
Mobile
Services
Developer
Services
Collaboration
Services
Caching
Services
Messaging
Services
Notification
Services
Storage
Services
Application
Store
Identity
Services
Powered By
32
Oracle Cloud is run on Chef
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Other PDIT Changes
33
Standardize Hardware Comprehensive Monitoring
Standardize Software (N, N-1) CMDB / Asset Management
IaaS (Nimbula/OpenStack) Proactive Monitoring
Symmetric Test/Prod/DR Environments Offshoring (1 x US + 2 x IDC shifts)
Nearline Backups, Compression, Dedup Maximize Depreciation
VLAN’s => VxLAN’s Defense in Depth Security Posture
Big Data Security Analytics (Hadoop) Centralized Identity Management
Elasticsearch+Logstash+Kibana Analytics Config Management (Chef/Puppet)
Orchestration (Mcollective)
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Core DevOps Principles
34
Cultural movement enabled by technology
Paid to add new features
Dev Ops
DevOps
Paid to keep system
stable, fast and available
Unified goal:
Add new features and keep the
system stable, fast and available
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
DevOps Is Ultimately In the Eye of the Beholder
What’s important is that you adhere to core principles that lead to business value
35
What is DevOps?

More Related Content

What's hot (20)

PPTX
DOES16 San Francisco - Scott Prugh & Erica Morrison - When Ops Swallows Dev
Gene Kim
 
PPTX
DevOps in your Oracle Stack
Timothy Krupinski
 
PPTX
How We Do DevOps at Walmart: OneOps OSS Application Lifecycle Management Plat...
WalmartLabs
 
PPTX
DOES15 - Ernest Mueller - DevOps Transformations At National Instruments and...
Gene Kim
 
PDF
Dev ops lessons learned - Michael Collins
Devopsdays
 
PDF
eDevOps in HPSW from buzzword to reality
AgileSparks
 
PPTX
Why DevOps Matters To The CIO
benjaminwootton
 
PDF
XebiaLabs Overview Slides
XebiaLabs
 
PPTX
DevOps-as-a-Service: Towards Automating the Automation
Keith Pleas
 
PPTX
Agile DevOps Transformation Strategy
Satish Nath
 
PPTX
DOES14 - Jonny Wooldridge - The Cambridge Satchel Company - 10 Enterprise Tip...
Gene Kim
 
PDF
Integrating Automated Testing into DevOps
TechWell
 
PDF
Next Generation IT Delivery - What it means to deliver atthe speed of the Dig...
Mirco Hering
 
PDF
from 0 to continuous delivery in 30 minutes
AgileSparks
 
PDF
Succeeding with DevOps Transformation - Rafal Gancarz
OpenCredo
 
PDF
DevOps – Don’t Be Left Behind
Capgemini
 
PPTX
DOES16 London - Darren Hague - SAP’s DevOps Journey: From Building an App to ...
Gene Kim
 
PPTX
Continuous Delivery and DevOps at Rabobank
XebiaLabs
 
PDF
Evolution of the DevOps Quality Management Office
Capgemini
 
PDF
Scrum in dev ops teams - Presentation from Scrum Gathering Bangalore
Mirco Hering
 
DOES16 San Francisco - Scott Prugh & Erica Morrison - When Ops Swallows Dev
Gene Kim
 
DevOps in your Oracle Stack
Timothy Krupinski
 
How We Do DevOps at Walmart: OneOps OSS Application Lifecycle Management Plat...
WalmartLabs
 
DOES15 - Ernest Mueller - DevOps Transformations At National Instruments and...
Gene Kim
 
Dev ops lessons learned - Michael Collins
Devopsdays
 
eDevOps in HPSW from buzzword to reality
AgileSparks
 
Why DevOps Matters To The CIO
benjaminwootton
 
XebiaLabs Overview Slides
XebiaLabs
 
DevOps-as-a-Service: Towards Automating the Automation
Keith Pleas
 
Agile DevOps Transformation Strategy
Satish Nath
 
DOES14 - Jonny Wooldridge - The Cambridge Satchel Company - 10 Enterprise Tip...
Gene Kim
 
Integrating Automated Testing into DevOps
TechWell
 
Next Generation IT Delivery - What it means to deliver atthe speed of the Dig...
Mirco Hering
 
from 0 to continuous delivery in 30 minutes
AgileSparks
 
Succeeding with DevOps Transformation - Rafal Gancarz
OpenCredo
 
DevOps – Don’t Be Left Behind
Capgemini
 
DOES16 London - Darren Hague - SAP’s DevOps Journey: From Building an App to ...
Gene Kim
 
Continuous Delivery and DevOps at Rabobank
XebiaLabs
 
Evolution of the DevOps Quality Management Office
Capgemini
 
Scrum in dev ops teams - Presentation from Scrum Gathering Bangalore
Mirco Hering
 

Viewers also liked (18)

PPTX
Building a DevOps organization
Zinnov
 
PPTX
Integrating SDLC, DevOps, and ITSM
Beyond20
 
PPTX
What is devops
Aaron Blythe
 
PPTX
What is DevOps?
Mesut Güneş
 
PPTX
Evaluation for my College magazine
sophiesophxo
 
PDF
Green School Program for Schools
i-dream
 
PPTX
Поспішайте робити добро
Сергій Мацаєнко
 
PPTX
12komunikasisinkron 141009205202-conversion-gate01
Khaminudin
 
PPTX
Digipak Pages
kgivens96
 
PPTX
Media Studies Evaluation 3
wdallo
 
PPTX
evaluation question 1
kgivens96
 
PPTX
վահագն և աստղիկ
Mesrop Onanyan
 
DOCX
Статут навчального закладу
Сергій Мацаєнко
 
DOCX
Evaluation 2
wdallo
 
PPT
Album cover creation task
wdallo
 
PPT
Album cover comparison
wdallo
 
PPTX
поспішайте робити добро
Сергій Мацаєнко
 
Building a DevOps organization
Zinnov
 
Integrating SDLC, DevOps, and ITSM
Beyond20
 
What is devops
Aaron Blythe
 
What is DevOps?
Mesut Güneş
 
Evaluation for my College magazine
sophiesophxo
 
Green School Program for Schools
i-dream
 
Поспішайте робити добро
Сергій Мацаєнко
 
12komunikasisinkron 141009205202-conversion-gate01
Khaminudin
 
Digipak Pages
kgivens96
 
Media Studies Evaluation 3
wdallo
 
evaluation question 1
kgivens96
 
վահագն և աստղիկ
Mesrop Onanyan
 
Статут навчального закладу
Сергій Мацаєнко
 
Evaluation 2
wdallo
 
Album cover creation task
wdallo
 
Album cover comparison
wdallo
 
поспішайте робити добро
Сергій Мацаєнко
 
Ad

Similar to What is DevOps? (20)

PPTX
Mastering DevOps with Oracle
jeckels
 
PDF
DevOps: Retooling the End-to-End IT Model
CA Technologies
 
PPTX
AMIS 25: DevOps Best Practice for Oracle SOA and BPM
Matt Wright
 
PPTX
Dev ops
Gourav Varma
 
PPTX
Melhore o Desenvolvimento do Time com DevOps na Nuvem
Bruno Borges
 
PDF
Scaling DevOps from Ground Zero to Enterprise
matthewabq
 
PDF
OOW15 - case study: oracle application management suite for oracle e-business...
vasuballa
 
PDF
AgileDC15 I'm Using Chef So I'm DevOps Right?
Rob Brown
 
PPTX
Dev Ops for systems of record - Talk at Agile Australia 2015
Mirco Hering
 
PDF
Dev ops concept
Professional Guru
 
PPTX
Choosing Automation for DevOps & Continuous Delivery in the Enterprise
XebiaLabs
 
PPTX
DevOps - Orientation Session
M M Nair
 
PPTX
Hybrid Development Workshop Presentation (San Francisco)
Brian Dawson
 
PPTX
Dg-DevOps_seminar.pptx
ArunRangrej1
 
PPTX
DevOps Culture transformation in Modern Software Delivery
Najib Radzuan
 
PDF
DevOps on Oracle Cloud
Mee Nam Lee
 
PDF
What is DevOps | DevOps Introduction | DevOps Training | DevOps Tutorial | Ed...
Edureka!
 
PDF
Losing Sight of DevOps in an Automation Forest - devopsdays Atlanta 2013
XebiaLabs
 
PPTX
DevOps
Gehad Elsayed
 
Mastering DevOps with Oracle
jeckels
 
DevOps: Retooling the End-to-End IT Model
CA Technologies
 
AMIS 25: DevOps Best Practice for Oracle SOA and BPM
Matt Wright
 
Dev ops
Gourav Varma
 
Melhore o Desenvolvimento do Time com DevOps na Nuvem
Bruno Borges
 
Scaling DevOps from Ground Zero to Enterprise
matthewabq
 
OOW15 - case study: oracle application management suite for oracle e-business...
vasuballa
 
AgileDC15 I'm Using Chef So I'm DevOps Right?
Rob Brown
 
Dev Ops for systems of record - Talk at Agile Australia 2015
Mirco Hering
 
Dev ops concept
Professional Guru
 
Choosing Automation for DevOps & Continuous Delivery in the Enterprise
XebiaLabs
 
DevOps - Orientation Session
M M Nair
 
Hybrid Development Workshop Presentation (San Francisco)
Brian Dawson
 
Dg-DevOps_seminar.pptx
ArunRangrej1
 
DevOps Culture transformation in Modern Software Delivery
Najib Radzuan
 
DevOps on Oracle Cloud
Mee Nam Lee
 
What is DevOps | DevOps Introduction | DevOps Training | DevOps Tutorial | Ed...
Edureka!
 
Losing Sight of DevOps in an Automation Forest - devopsdays Atlanta 2013
XebiaLabs
 
Ad

Recently uploaded (20)

PPTX
Agile Chennai 18-19 July 2025 Ideathon | AI Powered Microfinance Literacy Gui...
AgileNetwork
 
PDF
Build with AI and GDG Cloud Bydgoszcz- ADK .pdf
jaroslawgajewski1
 
PDF
MASTERDECK GRAPHSUMMIT SYDNEY (Public).pdf
Neo4j
 
PDF
Lecture A - AI Workflows for Banking.pdf
Dr. LAM Yat-fai (林日辉)
 
PPTX
The Future of AI & Machine Learning.pptx
pritsen4700
 
PPTX
Agile Chennai 18-19 July 2025 | Workshop - Enhancing Agile Collaboration with...
AgileNetwork
 
PPTX
Applied-Statistics-Mastering-Data-Driven-Decisions.pptx
parmaryashparmaryash
 
PPTX
Dev Dives: Automate, test, and deploy in one place—with Unified Developer Exp...
AndreeaTom
 
PDF
OFFOFFBOX™ – A New Era for African Film | Startup Presentation
ambaicciwalkerbrian
 
PPTX
Agentic AI in Healthcare Driving the Next Wave of Digital Transformation
danielle hunter
 
PDF
How ETL Control Logic Keeps Your Pipelines Safe and Reliable.pdf
Stryv Solutions Pvt. Ltd.
 
PDF
Per Axbom: The spectacular lies of maps
Nexer Digital
 
PDF
Brief History of Internet - Early Days of Internet
sutharharshit158
 
PDF
State-Dependent Conformal Perception Bounds for Neuro-Symbolic Verification
Ivan Ruchkin
 
PDF
Responsible AI and AI Ethics - By Sylvester Ebhonu
Sylvester Ebhonu
 
PDF
The Future of Mobile Is Context-Aware—Are You Ready?
iProgrammer Solutions Private Limited
 
PDF
The Future of Artificial Intelligence (AI)
Mukul
 
PDF
GDG Cloud Munich - Intro - Luiz Carneiro - #BuildWithAI - July - Abdel.pdf
Luiz Carneiro
 
PDF
Presentation about Hardware and Software in Computer
snehamodhawadiya
 
PDF
Economic Impact of Data Centres to the Malaysian Economy
flintglobalapac
 
Agile Chennai 18-19 July 2025 Ideathon | AI Powered Microfinance Literacy Gui...
AgileNetwork
 
Build with AI and GDG Cloud Bydgoszcz- ADK .pdf
jaroslawgajewski1
 
MASTERDECK GRAPHSUMMIT SYDNEY (Public).pdf
Neo4j
 
Lecture A - AI Workflows for Banking.pdf
Dr. LAM Yat-fai (林日辉)
 
The Future of AI & Machine Learning.pptx
pritsen4700
 
Agile Chennai 18-19 July 2025 | Workshop - Enhancing Agile Collaboration with...
AgileNetwork
 
Applied-Statistics-Mastering-Data-Driven-Decisions.pptx
parmaryashparmaryash
 
Dev Dives: Automate, test, and deploy in one place—with Unified Developer Exp...
AndreeaTom
 
OFFOFFBOX™ – A New Era for African Film | Startup Presentation
ambaicciwalkerbrian
 
Agentic AI in Healthcare Driving the Next Wave of Digital Transformation
danielle hunter
 
How ETL Control Logic Keeps Your Pipelines Safe and Reliable.pdf
Stryv Solutions Pvt. Ltd.
 
Per Axbom: The spectacular lies of maps
Nexer Digital
 
Brief History of Internet - Early Days of Internet
sutharharshit158
 
State-Dependent Conformal Perception Bounds for Neuro-Symbolic Verification
Ivan Ruchkin
 
Responsible AI and AI Ethics - By Sylvester Ebhonu
Sylvester Ebhonu
 
The Future of Mobile Is Context-Aware—Are You Ready?
iProgrammer Solutions Private Limited
 
The Future of Artificial Intelligence (AI)
Mukul
 
GDG Cloud Munich - Intro - Luiz Carneiro - #BuildWithAI - July - Abdel.pdf
Luiz Carneiro
 
Presentation about Hardware and Software in Computer
snehamodhawadiya
 
Economic Impact of Data Centres to the Malaysian Economy
flintglobalapac
 

What is DevOps?

  • 1. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | What is “DevOps” Anyway? Kelly Goetsch Director, Product Management Cloud Application Foundation 2015 A Pragmatic Introduction
  • 2. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Safe Harbor Statement The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. 2
  • 3. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Agenda 3 1 What is DevOps? And why now? 2 How to Change Your Culture 3 How to Change Your Technology 4 Case Study: Oracle’s Internal Embrace of DevOps
  • 4. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Dev and Ops Constantly Argue “Code is written...it’s your problem now” 4 Hey Ops - Here’s our code...good luck!
  • 5. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Modern DevOps = Culture + Technology Movement Culture is what’s behind DevOps; technology is the enabler 5 Culture Technology
  • 6. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Core DevOps Principles 6 Cultural movement enabled by technology Paid to add new features Dev Ops DevOps Paid to keep system stable, fast and available New goal: Add new features and keep the system stable, fast and available
  • 7. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Characteristics of DevOps Movement 7 Principles have been around for decades Agile Methodologies Open Culture Cloud-like Infrastructure Heavy Automation Open Source DevOps Movement began in startup community. Use of open source seen as integral but not technically necessary
  • 8. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Old Culture and Expectations Don’t Work! Commonly overheard in offices 8 It’ll take us three months to build you a development environment I have to stay up all night to do a build The new switch we need is sitting on the loading dock That code change will have to wait for our monthly build Uh...that’s not my problem. Go talk to Ops Why does your code always break my infrastructure?
  • 9. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. DevOps Tenet #1: Culture 9 DiscussRespect Avoid Blaming “Done” Means Released •Dev respect for ops •Ops respect for dev •Don’t stereotype •Don’t just say “no” •Don’t hide things •Ops should be in dev discussions •Dev should be in ops discussions •Shared runbooks/escalation plans •Ops should give devs access to systems •No fingerpointing! •Dev’s responsibility ends when it’s in production •“Throwing it over the wall” is dead
  • 10. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. DevOps Tenant #2: Technology 10 Shared Version Control Infra as Code One Step Build/De ploy Don’t Fix Anything •Use config mgmt to build environments •Scripts checked in and managed as src •Single system for code and build artifacts •Every time someone commits a change it triggers a build and automated build verification tests •Ship trunk •Enable features through flags •One button build/deploy (manual) •Scheduled builds/deploys •If verification fails, stop and alert •If something breaks, re-deploy. Don’t fix •Fix environment setup scripts
  • 11. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Faster Time-to-Market • Increase frequency of releases • Increase accuracy of releases - avoid downtime • Reduce the time it actually takes to perform a release Cost • Automate what was previously done manually. Reduces OPEX • Prevent humans from making costly errors • Reduce downtime, which saves money 11 Focus on Business Value • Allow high value employees to focus on higher value activities • Nobody benefits from doing low value activities, like setting up infrastructure Business Value Is Driving DevOps
  • 12. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Time • Longer time to market (initially) due to work required to automate • More builds / faster time- to-market for individual features • Lower MTTR because problems are fixed by rebuilding • Higher MTBF due to increased accuracy Cost • High up-front costs due to automation work • Low ongoing costs because routine operations is automated • Fewer employees wanting more pay - 10x developers want 10x pay • Lower capex, higher opex as workloads shift to cloud 12 Culture • Continues to empower developers • Automation increases operational efficiencies • Distracts developers from developing code • Movement eschews “rockstars” but that’s naturally what happens DevOps Implications To Business
  • 13. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Agenda 13 1 What is DevOps? And why now? 2 How to Change Your Culture 3 How to Change Your Technology 4 Case Study: Oracle’s Internal Embrace of DevOps
  • 14. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. How to Build a Successful DevOps Culture 14 DiscussRespect Avoid Blaming “Done” Means Released
  • 15. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Build Respect • Developers should respect Operations • Operations should respect Developers • Don’t just say “no” • Don’t stereotype! 15 Because the site breaks unexpectedly Because nobody tells them anything Because they say “no” all the time Ops Stereotype
  • 16. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Discuss • Don’t hide things! Open communication on both sides • Operations should be in Developer discussions • Developers should be in Operations discussions • Build shared runbooks/escalation plans • Operations should give Developers direct access to systems 16
  • 17. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Avoid Blaming • No fingerpointing! • Development should have enough Operations culpability to share the blame in an outage • Operations should have enough Development culpability to share the blame in an outage 17
  • 18. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. "Done" Means Released • The “throwing it over the wall to ops” model is dead • Development needs to be involved with operations • Operations needs to be involved with development • Joint success/failure 18 Development Operations
  • 19. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Steps Required to Change Culture 19  Hire technical people who are skilled in DevOps  Set up training for DevOps skills  Bring in consultants to help get started  Put Dev + Ops people under same line-level managers  Change the way you measure/reward performance  Flatten org chart to reduce fiefdoms  Let Dev + Ops collaborate to find solutions  Let Dev + Ops jointly pick tools. Limit corporate mandates  Don’t restrict the choice of public cloud solutions  Sponsor teambuilding events  Give Dev + Ops common goals to work towards  When there's a failure, don't dwell on Dev or Ops failure Build Trust Bring In New Blood Align Interests Empower Change From the Bottom Up
  • 20. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Change Your Organization’s Structure Incentives drive behavior 20 CIO VP of Operations Developer VP of Development Layers of Middle Management Layers of Middle Management Sys Admin CIO Developer VP of Product Layers of Middle Management Sys Admin Report to same manager. Incentivized to work together to develop and release Incentivized to innovate and release
  • 21. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Actively Build Trust 21 Trust is the #1 ingredient to a successful DevOps culture Dev + Ops + Social Activity Outside Work + Time = Trust
  • 22. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Agenda 22 1 What is DevOps? And why now? 2 How to Change Your Culture 3 How to Change Your Technology 4 Case Study: Oracle’s Internal Embrace of DevOps
  • 23. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. How to Use a Technology to Enable DevOps 23 Shared Version Control Infra as Code One Step Build/De ploy Don’t Fix Anything
  • 24. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Infrastructure as Code 24 Manage it as you would any other source code Base Image Install Binaries Configure Software Make Software Work Together Patch/Push Config Changes Step 1 Pick a Tool Step 2 Script your environment Step 3 Run your scripts against all hosts
  • 25. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Humans doing anything manually will introduce errors Consider Disabling SSH Access This could alienate ops people, however, as it shows a lack of trust 25 Possible solution: Remove each user’s shell • All changes should be scripted and QA’d – This prevents one-off changes (and errors) – Emergency fixes can still be pushed as required • Users can still SFTP to retrieve log files
  • 26. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Shared Version Control • Single system for code and build artifacts • Every time someone commits a change, consider triggering a build + automatic verification tests • Always ship trunk! • Enable features through flags Surprisingly not well adopted 26
  • 27. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. One Step Build/Deploy • Manual one button build/deploy • Scheduled builds - every day, every week, etc • Builds triggered by code checkins • If post-build validation fails, report it Set it and forget it 27
  • 28. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Popular DevOps Technology Remember: You can't get DevOps by buying a single product 28  Ansible  Jenkins / Hudson  Rundeck  Git  Perforce  Subversion  Ansible  Puppet  Chef  SaltStack  Gradle  Jenkins / Hudson  Robot  Artifactory  Nexus  Docker  Vagrant Version Control Build & Functional Testing Binary ManagementVirtualization Continuous Integration Continuous Delivery Configuration Management
  • 29. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Agenda 29 1 What is DevOps? And why now? 2 How to Change Your Culture 3 How to Change Your Technology 4 Case Study: Oracle’s Internal Embrace of DevOps
  • 30. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Product Development IT (PDIT) • 602 Exadata • 383 Exalogic • 69,290 Sun x86 servers • 6,854 SPARC servers • 1,768 Sun ZFS appliances • Thousands of other systems 30 Supporting enterprise, development IT, cloud and managed hosting at Oracle 924 Oracle Products 135,000 Employees
  • 31. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. How Did PDIT Improve Efficiency by > 2x in 18 Months? Culture changes enabled by technology 31 powered by powered by Culture (Campbell Webb, Sr. VP, Oracle) + + Cloud The Same Products Oracle Sells Infrastructure Automation
  • 32. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Oracle Cloud is Provisioned Using Chef Database Services Java Services Analytics Services Mobile Services Developer Services Collaboration Services Caching Services Messaging Services Notification Services Storage Services Application Store Identity Services Powered By 32 Oracle Cloud is run on Chef
  • 33. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Other PDIT Changes 33 Standardize Hardware Comprehensive Monitoring Standardize Software (N, N-1) CMDB / Asset Management IaaS (Nimbula/OpenStack) Proactive Monitoring Symmetric Test/Prod/DR Environments Offshoring (1 x US + 2 x IDC shifts) Nearline Backups, Compression, Dedup Maximize Depreciation VLAN’s => VxLAN’s Defense in Depth Security Posture Big Data Security Analytics (Hadoop) Centralized Identity Management Elasticsearch+Logstash+Kibana Analytics Config Management (Chef/Puppet) Orchestration (Mcollective)
  • 34. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Core DevOps Principles 34 Cultural movement enabled by technology Paid to add new features Dev Ops DevOps Paid to keep system stable, fast and available Unified goal: Add new features and keep the system stable, fast and available
  • 35. Copyright © 2015, Oracle and/or its affiliates. All rights reserved. DevOps Is Ultimately In the Eye of the Beholder What’s important is that you adhere to core principles that lead to business value 35

Editor's Notes

  • #13: MTTR = mean time to resolution MTBF = mean time between failures