Mais conteĂșdo relacionado Semelhante a What is DevOps? (20) 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
Notas do Editor MTTR = mean time to resolution
MTBF = mean time between failures