+ All Categories
Home > Technology > The DevOps Way of Delivering Results in the Enterprise

The DevOps Way of Delivering Results in the Enterprise

Date post: 14-Sep-2014
Category:
View: 15,234 times
Download: 0 times
Share this document with a friend
Description:
Delivering Software as a Service in the cloud requires agility and speed. Sadly, those are two attributes that big companies aren’t usually good at doing. Instead of organizing to deliver results, companies tend to build silos where development, operations, QA and security operate as separate entities. DevOps unites these groups to deliver services faster and provide results that matter. This talk will arm you with the DevOps patterns to follow as well as point out specific anti-patterns to avoid. To show you how to implement DevOps in your org, this talk will cover sample architectures and Open Source tooling. Come hear how to start delivering results with increased agility and speed.
Popular Tags:
102
mentor.com/embedded Android is a trademark of Google Inc. Use of this trademark is subject to Google Permissions. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. James Wickett [email protected] twitter: @wickett The DevOps Way of Delivering Results in the Enterprise
Transcript
Page 1: The DevOps Way of Delivering Results in the Enterprise

mentor.com/embedded

Android  is  a  trademark  of  Google  Inc.  Use  of  this  trademark  is  subject  to  Google  Permissions.

Linux  is  the  registered  trademark  of  Linus  Torvalds  in  the  U.S.  and  other  countries.

James [email protected]

twitter: @wickett

The DevOps Way of Delivering Results in the Enterprise

Page 2: The DevOps Way of Delivering Results in the Enterprise

I want you to be successful and make a difference

Page 3: The DevOps Way of Delivering Results in the Enterprise

James WickettSr. DevOps Engineer

Mentor Graphics Embedded Software Division

regular blogger at: theagileadmin.comruggeddevops.org

CISSP, GWAPTCCSK, GSEC, GCFW

@wickett

[email protected]

Page 4: The DevOps Way of Delivering Results in the Enterprise

Experience

• Started using AWS cloud in early 2008

• 2.5 years working on a DevOps team

• History of working in the enterprise and in startups and in startups inside the enterprise

• DevOps Days Austin Organizer

Page 5: The DevOps Way of Delivering Results in the Enterprise

ConclusionsThe cloud necessitates a new approach to our operations (business and tech)

DevOps has worked for startups and can work for the enterprise

Rugged DevOps fills some of the needs of the enterprise

Use a Behavior Driven Infrastructure approach

Page 6: The DevOps Way of Delivering Results in the Enterprise

DevOps Antipatterns• Rebrand your Ops team as the DevOps team• Use a machines to people hiring ratio to

determine headcount• Deploy software manually• Believe chef/puppet/cfengine will solve all your

problems• Test only the application code• Deploy to a production-like environment only

after development is complete• Rely on the standard logs for metrics• Hide stuff from your team

Page 7: The DevOps Way of Delivering Results in the Enterprise

before devops and enterprise, lets start with cloud

Page 9: The DevOps Way of Delivering Results in the Enterprise

“Cloud? I’ve been doing that since 1988. It’s just the same old thing with a new

name." - Technohipster

“Rugged DevOps will help you build your cloud” - http://bit.ly/rugged-devops

Page 10: The DevOps Way of Delivering Results in the Enterprise

OSSMOn-DemandScalableSelf-serviceMeasured

Dave Nielsen > http://www.rackspace.com/blog/on-definitions-keeping-it-simple-with-ossm/

Page 11: The DevOps Way of Delivering Results in the Enterprise

we sell time now

Page 12: The DevOps Way of Delivering Results in the Enterprise

“I don’t want you to send me an

installation disc”- your customer

Page 13: The DevOps Way of Delivering Results in the Enterprise

we sell social and friendships

Page 14: The DevOps Way of Delivering Results in the Enterprise

New landscape

Are New Skills Required for Cloud Computing?

Cloud computing requires new skills - 74%Cloud computing does not require new skills - 26%

source: The 2011 (ISC)2 Global Information Security Workforce Study

Page 15: The DevOps Way of Delivering Results in the Enterprise

Specific New Skills Required for Cloud Computing

A detailed understanding of cloud computing - 92% agreeEnhanced technical knowledge - 82% agreeContract negotiation skills - 49% agree

source: The 2011 (ISC)2 Global Information Security Workforce Study

Page 16: The DevOps Way of Delivering Results in the Enterprise

Code is social

Page 17: The DevOps Way of Delivering Results in the Enterprise

Delivery is King

courtesy of dbaron: http://www.flickr.com/photos/dbaron/2437975928/

Page 18: The DevOps Way of Delivering Results in the Enterprise

Time To Market is Crucial

Page 19: The DevOps Way of Delivering Results in the Enterprise

SaaS and PaaS

Page 20: The DevOps Way of Delivering Results in the Enterprise

New World of Services

Page 21: The DevOps Way of Delivering Results in the Enterprise

Give me API or

Give me Death-@littleidea

Page 22: The DevOps Way of Delivering Results in the Enterprise

the old way is broken

Page 23: The DevOps Way of Delivering Results in the Enterprise

DevOps is the new hotness for startups

Page 24: The DevOps Way of Delivering Results in the Enterprise

DevOps is a movementpredicated by:

cloud, startups, SaaS, consumerization of IT

Page 25: The DevOps Way of Delivering Results in the Enterprise

“there is nothing to suggest that devops can’t work in the enterprise”

-Patrick Debois

Cutter IT Journal, Vol. 24, No. 12, pg 3

Page 26: The DevOps Way of Delivering Results in the Enterprise
Page 27: The DevOps Way of Delivering Results in the Enterprise

DevOps?

Page 30: The DevOps Way of Delivering Results in the Enterprise

source: Gene Kim, “When IT says No” @SXSW 2012

Page 31: The DevOps Way of Delivering Results in the Enterprise

DevOps

Page 37: The DevOps Way of Delivering Results in the Enterprise
Page 38: The DevOps Way of Delivering Results in the Enterprise

CultureAutomationMeasurementSharing

source: John Willis (@botchagalupe) and Damon Edwards (@damonedwards)

Page 39: The DevOps Way of Delivering Results in the Enterprise

DevOps is Culture

Page 40: The DevOps Way of Delivering Results in the Enterprise

Culture is the most important aspect to DevOps succeeding in the enterprise

Page 41: The DevOps Way of Delivering Results in the Enterprise

Culture

Eliminate the blame game

Open post-mortems

Rewarding failure (and emphasis on testing)

Release often

Page 42: The DevOps Way of Delivering Results in the Enterprise

DevOps Antipattern:Rebrand your Ops team as the DevOps team

Page 43: The DevOps Way of Delivering Results in the Enterprise

DevOps Antipattern:Use a machines to people hiring ratio to determine

headcount

Page 44: The DevOps Way of Delivering Results in the Enterprise

DevOps is Automation

Page 45: The DevOps Way of Delivering Results in the Enterprise

Automation

Deploy

Control

Monitoring

Config Management

Orchestration

Page 46: The DevOps Way of Delivering Results in the Enterprise

Unique bits

OS Image (AMI)

Software (RPM)

Page 47: The DevOps Way of Delivering Results in the Enterprise

DevOps Antipattern:

Deploy software manually

Page 48: The DevOps Way of Delivering Results in the Enterprise

DevOps Antipattern:Test only the application code

Page 49: The DevOps Way of Delivering Results in the Enterprise

DevOps Antipattern:

Manual configuration of production environments

Page 50: The DevOps Way of Delivering Results in the Enterprise

DevOps Antipattern:Believe chef/puppet/cfengine will solve all your

problems

Page 51: The DevOps Way of Delivering Results in the Enterprise

DevOps Antipattern:Deploy to a production-like environment only after

development is complete

Page 52: The DevOps Way of Delivering Results in the Enterprise

DevOps is Measurement

Page 53: The DevOps Way of Delivering Results in the Enterprise

Measurement

Performance metrics

Logs

Metrics mapped to business goals

Integration with people

Page 54: The DevOps Way of Delivering Results in the Enterprise

DevOps Antipattern: Rely on the standard logs for metrics

Page 55: The DevOps Way of Delivering Results in the Enterprise

DevOps is Sharing

Page 56: The DevOps Way of Delivering Results in the Enterprise

Sharing

Feedback loops

Enables the Automation and Measurement

Significantly impacts Culture

Page 58: The DevOps Way of Delivering Results in the Enterprise

DevOps Antipattern:Hide stuff from your team

Page 59: The DevOps Way of Delivering Results in the Enterprise

Don’t forget Lean

Page 60: The DevOps Way of Delivering Results in the Enterprise

and Kanban

courtesy of fright42: http://www.flickr.com/photos/fright42/5329361800/sizes/l/in/photostream/

Page 61: The DevOps Way of Delivering Results in the Enterprise

The DevOps Library

Page 62: The DevOps Way of Delivering Results in the Enterprise

Enterprise?

Page 63: The DevOps Way of Delivering Results in the Enterprise

the perception of The Enterprise

Page 64: The DevOps Way of Delivering Results in the Enterprise

slow

Page 65: The DevOps Way of Delivering Results in the Enterprise

innovation starved

Page 66: The DevOps Way of Delivering Results in the Enterprise

process obsessed

Page 67: The DevOps Way of Delivering Results in the Enterprise

compliance and conformity as first order goals

Page 68: The DevOps Way of Delivering Results in the Enterprise

control

Page 69: The DevOps Way of Delivering Results in the Enterprise

DevOps and Enterpriseare unlikely

traveling companions

Page 70: The DevOps Way of Delivering Results in the Enterprise

“there is nothing to suggest that devops can’t work in the enterprise”

-Patrick Debois

Cutter IT Journal, Vol. 24, No. 12, pg 3

Page 71: The DevOps Way of Delivering Results in the Enterprise

“The main challenge will be reevaluating the existing people and processes from a constant collaboration viewpoint, keeping the business goals in mind.”

-Patrick Debois

Cutter IT Journal, Vol. 24, No. 12, pg 3

Page 72: The DevOps Way of Delivering Results in the Enterprise

Startups need

Cash

Customers (stakeholders)

Experimentation

Risk

Page 73: The DevOps Way of Delivering Results in the Enterprise

The Enterprise has different needs

Page 74: The DevOps Way of Delivering Results in the Enterprise

The Enterprise needs

Longevity

Stakeholders

Revenue

Compliance

Safeguards (data, legal, ...)

Page 75: The DevOps Way of Delivering Results in the Enterprise

HTTP://BIT.LY/RUGGED-DEVOPS

Page 76: The DevOps Way of Delivering Results in the Enterprise

THE INEQUITABLE DISTRIBUTION OF LABOR IN SECURITY MIMICS THAT IN DEV/OPS

Page 77: The DevOps Way of Delivering Results in the Enterprise

2% of an engineering dev team are working on security

- BSIMM 2012 data, http://bsimm.com/

Page 78: The DevOps Way of Delivering Results in the Enterprise
Page 79: The DevOps Way of Delivering Results in the Enterprise

I recognize that my code will be attacked by talented and persistent adversaries who threaten our physical,

economic, and national security.

I am rugged, not because it is easy, but because it is necessary... and I am up for the challenge.

I recognize that my code will be used in ways I cannot anticipate, in ways it was not designed,

and for longer than it was ever intended.

Page 80: The DevOps Way of Delivering Results in the Enterprise
Page 81: The DevOps Way of Delivering Results in the Enterprise

Current Software

slide from http://bit.ly/rugged-devops

Page 82: The DevOps Way of Delivering Results in the Enterprise

Rugged Software

slide from http://bit.ly/rugged-devops

Page 83: The DevOps Way of Delivering Results in the Enterprise

Current Software

slide from http://bit.ly/rugged-devops

Page 84: The DevOps Way of Delivering Results in the Enterprise

Rugged Software

slide from http://bit.ly/rugged-devops

Page 85: The DevOps Way of Delivering Results in the Enterprise

Current Software

slide from http://bit.ly/rugged-devops

Page 86: The DevOps Way of Delivering Results in the Enterprise

Rugged Software

slide from http://bit.ly/rugged-devops

Page 87: The DevOps Way of Delivering Results in the Enterprise

ADVERSITY REQUIRES RUGGED SOLUTIONS

slide from http://bit.ly/rugged-devops

Page 88: The DevOps Way of Delivering Results in the Enterprise

RUGGEDIZATION THEORY

Building solutions to handle adversity will cause unintended, positive benefits that will provide value that would have been unrealized otherwise.

slide from http://bit.ly/rugged-devops

Page 89: The DevOps Way of Delivering Results in the Enterprise

NO PAIN, NO GAIN

slide from http://bit.ly/rugged-devops

Page 90: The DevOps Way of Delivering Results in the Enterprise

slide from http://bit.ly/rugged-devops

Page 91: The DevOps Way of Delivering Results in the Enterprise

Rugged DevOpsrepeatable – no manual steps

reliable - no DoS here

reviewable – aka audit

rapid – fast to build, deploy, restore

resilient – automated reconfiguration

reduced - limited attack surface

slide from http://bit.ly/rugged-devops

Page 92: The DevOps Way of Delivering Results in the Enterprise

Rugged DevOps Testing

unit tests

smoke tests

security tests (gauntlt)

outside-in tests (cucumber, aruba)

monitoring (created from your tests)

Page 93: The DevOps Way of Delivering Results in the Enterprise

What about the toolchain?

Page 94: The DevOps Way of Delivering Results in the Enterprise

Paul Hammond, Scaling Typekit Infrastructure for Startups, Velocity 2012

Page 95: The DevOps Way of Delivering Results in the Enterprise

Paul Hammond, Scaling Typekit Infrastructure for Startups, Velocity 2012

Page 96: The DevOps Way of Delivering Results in the Enterprise

Our Toolchain and Software Stack

chef

Datadog

pingdom

loggly

PagerDuty

JIRA

ubuntu

mongodb

nginx

tornado

haproxy

IRC

AWS (ec2, s3)

cucumber

aruba

gauntlt

CloudWatch

github

Page 97: The DevOps Way of Delivering Results in the Enterprise

Behavior Driven Infrastructure

Write failing tests describing the infrastructure you wish you had

Make them pass by writing infrastructure automation code (chef/puppet)

Repeat

Page 98: The DevOps Way of Delivering Results in the Enterprise

In summary

Page 99: The DevOps Way of Delivering Results in the Enterprise

Culture is the most important aspect to DevOps succeeding in the enterprise

-me, 30 minutes ago

Page 100: The DevOps Way of Delivering Results in the Enterprise

ConclusionsThe cloud necessitates a new approach to our operations (business and tech)

DevOps has worked for startups and can work for the enterprise

Rugged DevOps fills some of the needs of the enterprise

Use a Behavior Driven Infrastructure approach

Page 101: The DevOps Way of Delivering Results in the Enterprise

DevOps Antipatterns• Rebrand your Ops team as the DevOps team• Use a machines to people hiring ratio to

determine headcount• Deploy software manually• Believe chef/puppet/cfengine will solve all your

problems• Test only the application code• Deploy to a production-like environment only

after development is complete• Rely on the standard logs for metrics• Hide stuff from your team

Page 102: The DevOps Way of Delivering Results in the Enterprise

mentor.com/embedded

Android  is  a  trademark  of  Google  Inc.  Use  of  this  trademark  is  subject  to  Google  Permissions.

Linux  is  the  registered  trademark  of  Linus  Torvalds  in  the  U.S.  and  other  countries.

James [email protected]

twitter: @wickett

The DevOps Way of Delivering Results in the Enterprise


Recommended