devops kc meetup_5_20_2013

46
December 5, 2012 Kansas City DevOps Meetup

Upload: aaron-blythe

Post on 17-Nov-2014

181 views

Category:

Documents


0 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Devops kc meetup_5_20_2013

December 5, 2012

Kansas City DevOps Meetup

Page 2: Devops kc meetup_5_20_2013

Agenda

•5:30 – 6:15 – Meet, greet, and eat

•6:15 – 6:45 – Google Fiberspace Presentation

•6:45 – 7:00 – Agenda and Introductions

•7:00 – 7:30 – Meetup group logistics

•7:30 – 7:45 – Presentation – Aaron (Cerner) and Stathy (OpsCode)

•7:45 – 8:00 – Volunteers and next meeting decisions

•8:00 Q&A and Wrap-up

Page 3: Devops kc meetup_5_20_2013

“We are at our most productive when we share our thinking. One night of crazy brain-storming over a few beers is more likely to produce more exciting results than 20 years’ solitary study in the lab.”–Professor Howard Trevor Jacobs, Descartes Prize Winner

Read more at redmonk.com - http://goo.gl/FEJyIhttp://redmonk.com/jgovernor/2004/12/15/the-pub-is-the-place-for-creativity-and-innovation/

Page 4: Devops kc meetup_5_20_2013

Who am I?

Area Director

My agenda

Bootstrap Meetups

Learn more

Share experiences with people from diverse backgrounds

Introductions …

~ 1m round the room brief intro, don’t be too shy

Page 5: Devops kc meetup_5_20_2013

“Rules of Engagement”

3 Rules of DevOps Meetup

Page 6: Devops kc meetup_5_20_2013

“Rules of Engagement”

1st Rule:Talk about DevOps Meetup

Page 7: Devops kc meetup_5_20_2013

“Rules of Engagement”

Collaboration&

Community

Page 8: Devops kc meetup_5_20_2013

“Rules of Engagement”

2nd Rule:TALK about DevOps Meetup

Page 9: Devops kc meetup_5_20_2013

“Rules of Engagement”

3rd Rule:No Assholes

Page 10: Devops kc meetup_5_20_2013

“Rules of Engagement”

Collaborate and debateNO disrespect

Page 11: Devops kc meetup_5_20_2013

Seriously…

Page 12: Devops kc meetup_5_20_2013

“Rules of Engagement”

DevOps = Community

Page 13: Devops kc meetup_5_20_2013

Logistics

•Topic coverage? topic focus?

•Lightning talks, 4-5, 5-10m each

•Unmeeting – Larger group

•Presentations – Intro & Advanced

•Demo & Tutorial

•Case studies and experience sharing.

•Monthly? Bi-monthly? Quarterly?

Page 14: Devops kc meetup_5_20_2013

“Infrastructure As Code” 101

Page 15: Devops kc meetup_5_20_2013

Infrastructure is Complex

Page 16: Devops kc meetup_5_20_2013

•Nodes

•Networking

•Files

•Directories

•Symlinks

•Mounts

•Routes

•Users

•Groups

•Packages

•Services

•Filesystems

Items of Manipulation (resources)

Page 17: Devops kc meetup_5_20_2013

Application

See Node

Page 18: Devops kc meetup_5_20_2013

Application

Application Database

See Nodes

Page 19: Devops kc meetup_5_20_2013

Application

App Databases

See Nodes Grow

Page 20: Devops kc meetup_5_20_2013

App Servers

App Databases

See Nodes Grow

Page 21: Devops kc meetup_5_20_2013

App LB

App Servers

App Databases

See Nodes Grow

Page 22: Devops kc meetup_5_20_2013

App LBs

App Servers

App Databases

See Nodes Grow

Page 23: Devops kc meetup_5_20_2013

App LBs

App Servers

App DB Cache

App DBs

See Nodes Grow

Page 24: Devops kc meetup_5_20_2013

App LBs

App Servers

App DB Cache

App DBs

Infrastructures have topology

Page 25: Devops kc meetup_5_20_2013

Round Robin DNS

App Servers

App DB Cache

App DBs

Floating IP?

Yours is a snowflake

Page 26: Devops kc meetup_5_20_2013

App LBs

App Servers

NoSQL

DB slaves

Cache

DB Cache

DBs

Complexity increases quickly

Page 27: Devops kc meetup_5_20_2013

USA

EUR

AUS

It increases globally...

Page 28: Devops kc meetup_5_20_2013

Traditional Thinking Won’t Make the Grade …

Before discussing the future,

Let’s review the past.

More importantly why “traditional” enterprise technologies will not cut it.

Page 29: Devops kc meetup_5_20_2013

1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 20151980198119821983198419851986198719881989

Unprecedented Growth AND Complexity …

1980Mainframe

1990Client/Server

2000Datacenter

2010+Cloud

Scale x Complexity > Skills

Inflection point forces disruption.

Page 30: Devops kc meetup_5_20_2013

Inflection Point Inspires …

Mainframe

Client/Server

Datacenter

Cloudy

1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 -

20,000,000

40,000,000

60,000,000

80,000,000

100,000,000

120,000,000

Physcial Hardware Virtual Nodes

30

Traditional, data model

driven applications.

Traditional, domain model

driven applications.

“Infrastructure As Code”

“Infrastructure As Code”

Page 31: Devops kc meetup_5_20_2013

USA

EUR

AUS

How can this be abstracted AND represented?

Page 32: Devops kc meetup_5_20_2013

1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015

Maturity of “Infrastructure As Code”

Page 33: Devops kc meetup_5_20_2013

“In God we Trust, all others bring DATA!!!”

http://radar.oreilly.com/2007/10/operations-is-a-competitive-ad.html

VS

Page 34: Devops kc meetup_5_20_2013

•A configuration management system (DSL)

•A library for configuration management

•A community, contributing to library and expertise

•A systems integration platform (API)

http://www.flickr.com/photos/asten/2159525309/sizes/l/

“Infrastructure As Code”

Page 35: Devops kc meetup_5_20_2013

Some Samples

package { "apache2":

ensure => latest

}

service { "apache2":

ensure => running,

require => Package["apache2"],

subscribe => File[httpdconf],

}

Page 36: Devops kc meetup_5_20_2013

Some Samples

package "apache2" do

  package_name node[:apache][:package]

  action :install

end

template "/etc/www/configures-apache.conf" do

  notifies :restart, "service[apache2]”

end

service “apache2”

Page 37: Devops kc meetup_5_20_2013

The players

Metaphor Attribution – Andrew Shafer, now of Rackspace

Dev Ops&

Page 38: Devops kc meetup_5_20_2013

Meet Dev

• Little bit weird• Sits closer to the boss• Thinks too hard

Don’t hate the player …

Metaphor Attribution – Andrew Shafer, now of Rackspace

Page 39: Devops kc meetup_5_20_2013

Meet Ops

• Pulls levers & turns knobs

• Easily excited• Yells a lot in

emergenciesWhy you be hatin ? ! ?

Metaphor Attribution – Andrew Shafer, now of Rackspace

Page 40: Devops kc meetup_5_20_2013

Traditional Process

Dev’s job is to add new features.

Ops’ job is to keep the site stable and fast

Page 41: Devops kc meetup_5_20_2013

Load Balancer

App Server

Database

Dev (shared) Dev - QA - UAT - Prod

Load Balancer

App Server App Server

Database

Load Balancer

App Server

Database

QA

Agility - Design vs Manufacturing

How ?

Page 42: Devops kc meetup_5_20_2013

Dev ProdQA

Goal = Increase Velocity

Agility - Design vs Manufacturing

Load Balancer

App Server

App Server

Database

Load Balancer

App Server

App Server

Database

Load Balancer

App Server

App Server

Database

What ?

Page 43: Devops kc meetup_5_20_2013

“Infrastructure As Code” + Continuous Deployment

Value of Continuous Deployment?

•Visibility and Accountability

•Reduce Risk

•Increase Productivity

•Innovate Faster

•Business Agility

Page 44: Devops kc meetup_5_20_2013

Thank You!

Stathy Touloumis

[email protected]

Twitter | IRC | github:

stathyinc

Page 45: Devops kc meetup_5_20_2013

Thank You!

Aaron [email protected]

Twitter: ablythe

Github: aaronblythe

Page 46: Devops kc meetup_5_20_2013

Topic Brainstorming

•7:45 – 8:00 – Volunteers and Topics

•Frequency of meeting – 5th of every month?

•Solidify next few topics to cover

•Pick topic(s) and speaker(s) for the next meeting