DevelopingtheFuture* - IPMA-WAipma-wa.com/sites/default/files/page/2015/03/IPMA_Oracle...your%code!% It'snotmy code,it'syour* machines!* Copyright©201 5,Oracleand/oritsaﬃliates.Allrightsreserved.**|*

Developing the Future Adap%ng IT Skill Sets to a Dynamic Technology Landscape

Robin Geddes Infrastructure Architect Public Sector, State and Local May, 2015

Copyright © 2015, Oracle and/or its affiliates. All rights reserved. |


AdapKng IT skill sets: Topics

Culture – AdopKon of DevOps

AutomaKon – Many, many, new Tools

Making it happen

1

2

3



Culture – adopKon of DevOps

AutomaKon -‐ New Tools

Making it happen

1

2

3


Familiar? DevOps seeks to solve this

It's not my machines, it's your code!

It's not my code, it's your machines!


Dev and Ops Constantly Argue “Code is wri*en...it’s your problem now”

Hey Ops -‐ Here’s our code...good luck!


DevOps Principles 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


Capital + AutomaKon Always Win Over Labor


DevOps = Culture + Technology Movement Culture is what’s behind DevOps; technology is the enabler

Culture

Technology

Constrained By


DevOps Tenet #1: Culture

Discuss Respect

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/escalaKon plans • Ops should give devs access to systems

• No fingerpoinKng! • Dev’s responsibility ends when it’s in producKon • “Throwing it over the wall” is dead


DevOps Tenant #2: Technology

Shared Version Control

Infra as Code

One Step Build/Deploy

Don’t Fix Anything

• Use config mgmt to build environments • Scripts checked in and managed as src

• Single system for code and build arKfacts • Every Kme someone commits a change it triggers a build and automated build verificaKon tests • Ship trunk • Enable features through flags

• One bugon build/deploy (manual) • Scheduled builds/deploys • If verificaKon fails, stop and alert

• If something breaks, re-‐deploy. Don’t fix • Fix environment setup scripts


DevOps Is In the Eye of the Beholder What’s important is that you adhere to principles that lead to business value


Culture and Principles

People Processes Tools > > Are more

important than Are more

important than

are important!


Old Culture and ExpectaKons Don’t Work! Commonly overheard in offices

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 sikng 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?





Making it happen

1

2

3


Resources are Available to Help Make the Change


PaaS / IaaS Now Allows Resources to be Easily Provisioned

Network

Storage

Compute

Hypervisor

OperaKng System

JVM

App Server

ApplicaKon

PaaS IaaS

Past: Ops manually provisioned each layer

Today: Developers can provision enKre stacks of hardware + somware through REST API


Good Technology is Now Available DevOps technology all < 10 years old

Capital + mechanical automaKon always win over labor

§  Puppet §  Git

2005

§  Chef §  New Relic §  SOASTA

2008

§  SaltStack §  Jenkins

2011

§  Ansible §  Vagrant §  Gradle

2012

§  Docker

2013


Investment in DevOps Shows No Signs of Slowing DevOps-‐related technology solves real business problems

0

10

20

30

40

50

60

70

80

90

Cumula%

ve $ Raised ($m)

Cumula%ve Investments in Puppet and Chef, 2009 -‐ 2014

Puppet

Chef


Popular DevOps Technology Remember: You can't get DevOps by buying a single product

§  Ansible §  Jenkins / Hudson §  Rundeck

§  Git §  Perforce §  Subversion

§  Ansible §  Puppet §  Chef §  SaltStack

§  Gradle §  Jenkins / Hudson §  Robot §  Arquillian

§  ArKfactory §  Nexus

§  Docker §  Vagrant

Version Control

Build & Func%onal Tes%ng Binary Management Virtualiza%on

Con%nuous Integra%on Con%nuous Delivery Configura%on Management


Did We MenKon Docker?

22

Google Trends – Interest Over Time





Making it happen

1

2

3


•  Development Lifecycle

•  OperaKons – mointoring, metrics, showback

•  Plauorm-‐as-‐a-‐Service •  Infrastructure-‐as-‐a-‐Service

Oracle is serious about Cloud


Using Developer Cloud Service for DevOps

25

How Does it Support DevOps?

§  Offers shared version control, one step build/deploy and collaboraKon tooling as a hosted service

§  Features include a dashboard, tasks, one-‐step build, code reviews, one-‐step deploy, wiki, integraKon with IDEs

§  Facilitates discussion

§  Supports “done” means released ethos

§  Prevents you from having to do it on your own

What Problems Does it Solve?

§  Hosted offering for sekng up development infrastructure

§  Integrates Hudson, Git, Maven, Eclipse, JDeveloper, and Netbeans to offer a complete development environment as a service

What is It?


Using Enterprise Manager for DevOps

26


§  ApplicaKon performance management

§  ApplicaKon quality management

§  Manage/monitor cloud, applicaKons, middleware, databases, and hardware

§  Support infrastructure as code by allowing for enKre environments to be hydrated, stored, and dehydrated

§  Centrally manage and monitor all hardware and somware


§  Manage/monitor cloud, applicaKons, middleware, databases, and hardware

§  Agent/controller-‐based system

§  Best for on premises workloads What is It?


Using Oracle PaaS for DevOps

27


§  Offers a ready-‐built plauorm for deploying your applicaKons to. You deploy your applicaKon -‐ Oracle worries about provisioning and managing

§  Same code powers both private and public versions; very easy portability

§  Prevents you from manually sekng up and provisioning a plauorm

§  Full lifecycle is built in to the soluKon

§  Save costs -‐ pay for what you use


§  Java-‐based PaaS offered on premises (Oracle Exalogic) and off premises (Oracle Cloud). Whether deployed on/off premises, it’s called Java Cloud Service

§  Includes automaKc provisioning of applicaKon server, infrastructure, storage and database

What is It?


Using IaaS for DevOps

28


§  Offers ready-‐built infrastructure for you to install your somware to -‐ Oracle worries about provisioning and managing

§  Same code powers both private and public versions; very easy portability

§  Prevents you from manually sekng up and provisioning infrastructure

§  Infrastructure lifecycle is built in to the soluKon

§  Save costs -‐ pay for what you use


§  Comprehensive IaaS soluKon offered on (Oracle Exalogic) and off (Oracle Cloud) premises

§  Includes secure provisioning of hardware, network and operaKng system What is It?


Oracle Can Help You Lead Change in Your OrganizaKon

29

But real change begins with you

Your responsibility

Respect


Discuss

Avoid Blaming



Infrastructure as Code


Culture

Technology

DevOps Tenet #1:

DevOps Tenet #2:

Your responsibility,

can help but

How Oracle Can Help with DevOps

Simplify

Shrink RunKme

Simplify InstallaKon

Simplify Provisioning

Support Lifecycle


Oracle is Serious About DevOps

30

Oracle products support DevOps

Respect


Discuss

Avoid Blaming



Infrastructure as Code


Culture

Technology

DevOps Tenet #1:

DevOps Tenet #2:

Light | Fast | Modular | M

odern | Easy


More deployment choice should not equal more complexity

• Cloud shouldn’t mean you should have a different set of of tools and processes •  You should be able to use the same tools, same APIs in-‐cloud or on-‐premise

Automate. Automate. Automate.

Oracle Public Cloud On Premise Private

Cloud 3rd Party

Public Cloud

DEPLOY ANYWHERE


Oracle 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

32

Suppor%ng enterprise, development IT, cloud and managed hos%ng at Oracle

924 Oracle Products 135,000 Employees

Copyright © 2015, Oracle and/or its affiliates. All rights reserved. | 33

PDIT is Modernizing Using Oracle Products

0 50 100 150

Q4 FY12

Q1 FY13

Q2 FY13

Q3 FY13

Q4 FY13

Q1 FY14

Servers per System Admin

0 20 40 60

Q4 FY12

Q1 FY13

Q2 FY13

Q3 FY13

Q4 FY13

Q1 FY14

Storage Devices per Storage Admin

0 1000 2000 3000

Q4 FY12

Q1 FY13

Q2 FY13

Q3 FY13

Q4 FY13

Q1 FY14

TB of Storage per Storage Admin

2.2x 2.8x 3.6x


How Did PDIT Improve Efficiency by > 2x in 18 Months? Culture changes enabled by technology

34

powered by

powered by

Culture (Campbell Webb, Sr. VP, Oracle)

+ + Cloud

The Same Products Oracle Sells Infrastructure Automa%on


Other PDIT Changes

35

Standardize Hardware Comprehensive Monitoring

Standardize Somware (N, N-‐1) CMDB / Asset Management

IaaS (Nimbula/OpenStack) ProacKve Monitoring

Symmetric Test/Prod/DR Environments Offshoring (1 x US + 2 x IDC shims)

Nearline Backups, Compression, Dedup Maximize DepreciaKon

VLAN’s => VxLAN’s Defense in Depth Security Posture

Big Data Security AnalyKcs (Hadoop) Centralized IdenKty Management

ElasKcsearch+Logstash+Kibana AnalyKcs Config Management (Chef/Puppet)

OrchestraKon (McollecKve)


Oracle Cloud is Provisioned Using Chef

Database Services

Java Services

Analy%cs Services

Mobile Services

Developer Services

Collabora%on Services

Caching Services

Messaging Services

No%fica%on Services

Storage Services

Applica%on Store

Iden%ty Services

Powered By

36

Oracle Cloud is run on Chef


So what about you?


AcKvely Build Trust Trust is the #1 ingredient to a successful DevOps culture

Dev + Ops + Social AcKvity Outside Work + Time = Trust


PracKcal steps -‐ How to get there Start small. Prototype. Sponsor bolom-‐up change and Evangelize.

•  Start with a small team with a mix of experience

•  Include seasoned veterans that yours teams respect and will listen to

•  Include “new blood” to focus on new processes who doesn’t need to “unlearn” how things have historically been done •  Longer Kme to market (iniKally) due to work required to

automate •  High up-‐front costs due to automaKon work •  AutomaKon always pays off over Kme


Steps Required to Change Culture

40

§  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 §  Flagen org chart to reduce fiefdoms

§  Let Dev + Ops collaborate to find soluKons §  Let Dev + Ops jointly pick tools. Limit corporate mandates §  Don’t restrict the choice of public cloud soluKons

§  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 Bogom Up


OrganizaKonal Misalignment Leads to DysfuncKon Pre-‐DevOps org structure

43

CEO

CIO CFO

VP of OperaKons

Developer

VP of Development

Layers of Middle

Management

Layers of Middle

Management

Sys Admin

VP of Finance

Layers of Middle

Management

Accountant

Ops and developers report to CIO through different tracks, have opposing management, and opposing incenKves

IncenKvized to keep systems up

IncenKvized to innovate

IncenKvized to keep ops busy by building each layer the old way

Wants a fix to business problem ASAP. Can’t wait for Kme required to automate

Full stack developers cost a lot of money -‐ don’t fit into exisKng salary bands

IncenKvized to keep developers developing. Ops is someone else’s job


Change Your OrganizaKon’s Structure Incen%ves drive behavior

44

CIO

VP of OperaKons

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. IncenKvized to work together to develop and release

IncenKvized to innovate and release


Time •  Longer Kme to market (iniKally) due to work required to automate

•  More builds / faster Kme-‐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 automaKon work

•  Low ongoing costs because rouKne operaKons is automated

•  Lower capex, higher opex as workloads shim to cloud

45

Culture •  ConKnues to empower developers

•  AutomaKon increases operaKonal efficiencies •  Distracts developers from developing code

•  Movement eschews “rockstars” but that’s naturally what happens

DevOps ImplicaKons To Business

Documents

Developing*the*Future* - IPMA-WAipma-wa.com/sites/default/files/page/2015/03/IPMA_Oracle...your%code!% It's*notmy* code,*it's*your* machines!* Copyright©*201 5,*Oracle*and/or*its*aﬃliates.*All*rights*reserved.**|*

DevelopingtheFuture* - IPMA-WAipma-wa.com/sites/default/files/page/2015/03/IPMA_Oracle...your%code!% It'snotmy code,it'syour* machines!* Copyright©201 5,Oracleand/oritsaﬃliates.Allrightsreserved.**|*