from devops to operations science

31
From DevOps to Operations Science Christopher Brown, CTO, Opscode

Upload: weareesynergy

Post on 10-May-2015

257 views

Category:

Technology


0 download

DESCRIPTION

By Christopher Brown, CTO, Opscode

TRANSCRIPT

Page 1: From DevOps to Operations Science

From DevOps to Operations Science

Christopher Brown, CTO, Opscode

Page 2: From DevOps to Operations Science

• Christopher Brown• Chief Technology Officer• Twitter: @skeptomai, Email: [email protected]

From DevOps to Operations ScienceA business transformation in 3 acts…

Page 3: From DevOps to Operations Science

3

http://dlutzy.wordpress.com/2011/06/16/velocity-2011-day-1/

CTO

Page 4: From DevOps to Operations Science

What is Chef?

Recipes and Cookbooks that describe and deliver code.

Chef enables people to easily build & manage complex & dynamic applications at massive scale.

• Model for describing infrastructure that promotes reuse

• Programmatically provision and configure

• Reconstruct business from code repository, data backup, and bare metal resources

Chef is an IT automation platform for developers & systems engineers to continuously define, build, and manage infrastructure.

CHEF USES:

“”

Page 5: From DevOps to Operations Science

http://www.flickr.com/photos/mikepd/240903973/

People

Page 6: From DevOps to Operations Science

Business

Page 7: From DevOps to Operations Science

Technology

Page 8: From DevOps to Operations Science

http://www.flickr.com/photos/mikepd/240903973/

People

Page 9: From DevOps to Operations Science

http://www.flickr.com/photos/timyates/2854357446/sizes/l/

Software EngineeringSystems Adminstrators

“Business” People?DevOps

Page 10: From DevOps to Operations Science

Hey Ops! Do I have to fire you?

...the site’s down again

Page 11: From DevOps to Operations Science

“I was hired to roll back code”

Page 12: From DevOps to Operations Science

DevOps is supposed to fix this, right?

Page 13: From DevOps to Operations Science

That favor complexity, and discourage transparent competition based on price or quality.”

http://www.theatlantic.com/magazine/archive/2009/09/how-american-health-care-killed-my-father/307617/

“Accidentally, but relentlessly, America has built a health-care system with incentives that inexorably generate terrible and perverse results.

Incentives that emphasize health care over any other aspect of health and well-being. That emphasize treatment over prevention.

That disguise true costs.

Page 14: From DevOps to Operations Science

http://www.flickr.com/photos/baerchen57/5609858075/sizes/l/in/pool-809956@N25/

Developer Duck

Ops Beaver

http://www.biokids.umich.edu/critters/1995/Castor_canadensis/pictures/

http://www.amamoorlodge.com.au/images/platypus-03-swimming.jpg

DevOps Platypus

Page 15: From DevOps to Operations Science

“The demographic seems to be experienced, talented 30-something sysadmin coders with a clear understanding that writing software is about making money and shipping product.”

“If you're a developer, go and make friends with your sysadmins. Don't view them as lower life forms, or as people to lob problems to. ... If they're using Puppet or Chef, get involved - start contributing to their codebase.”

How does DevOps help?

http://www.jedi.be/blog/2010/02/12/what-is-this-devops-thing-anyway/

- Patrick Debois

Page 16: From DevOps to Operations Science
Page 17: From DevOps to Operations Science

Business

Page 18: From DevOps to Operations Science

“In ten years, I’m certain every COO worth their salt will have come from IT. Any COO who doesn’t

intimately understand the IT systems that actually run the business is just an empty suit, relying on someone else to do their job.”

Kim, Gene; Behr, Kevin ; Spafford, George (2013-01-10). The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win (Kindle Locations 5805-5807). IT Revolution Press. Kindle Edition.

The Back Office Becomes The Front Office

Page 19: From DevOps to Operations Science

• IT was historically a source of internal efficiency

• As more and more customers prefer digital consumption, that role shifts to one that is increasingly customer centric – the front of the business, not the back– Every technology that

previously impacted only internal business functions now directly supports customer interactions!

Page 20: From DevOps to Operations Science

Software is the interface for consumption

http://www.flickr.com/photos/ebatty/467581939/sizes/l/in/photostream/

Page 21: From DevOps to Operations Science

Applications became customer service vehicles

“If you make customers unhappy in the physical world, they might each tell 6 friends. If you make customers unhappy on the Internet, they can each tell 6,000 friends.” – Jeff Bezos (Amazon.com)

“The goal as a company is to have customer service that is not just the best, but legendary.” – Sam Walton (Walmart)

Page 22: From DevOps to Operations Science

• Is the cultural and professional movement that grew directly from the collective experience of the pioneers of this transition

• It’s application to traditional IT is 1:1• The business adaptations encapsulated in

Devops will eventually be ubiquitous– ....At least, if you want to be great at the next couple decades of global economic growth

DevOps

Page 23: From DevOps to Operations Science

• Businesses must deliver better customer experience as quickly and safely as possible.

• Safety matters! • Failure to do so will have

serious impacts on customer satisfaction and loyalty – just like it did when Sam Walton was the Ghengis Kahn of rural retail.

http://www.flickr.com/photos/huffstutterrobertl/5088855119/lightbox/

Continuous Delivery

Page 24: From DevOps to Operations Science

Every success story we’ve found shares some common traits

Every failure lacks one or more of them

Page 25: From DevOps to Operations Science

• Focus on responsibility and accountability, rather than authority

– Functional teams have responsibility for design, implementation, and administration of their products and services – cradle to grave.

– Architecture, Security, Systems Administration, and QA become universal responsibilities, with experts who set standards and build tools to enable the business to do the right thing.

– Business leaders set priorities and direction, and have close communication loops with teams doing implementation work.

Build a culture of personal empowerment and accountability

Page 26: From DevOps to Operations Science

Have a strong reliance on centralized decision making and environmental gates.

Cannot ever point at individuals who are responsible for outcomes

Have few, if any, capable “full stack” engineers

“Architects” responsible for high level design, but no real commitment to implementation

Companies that get this wrong…

Page 27: From DevOps to Operations Science

“Progress on safety coincides with learning from failure.

This makes punishment and learning two mutually exclusive activities

Treat failure as a learning opportunity

Organizations can either learn from an accident or punish the individuals involved in it, but hardly do both at the same time. ... Learning challenges and potentially changes the belief about what creates safety. Moreover, punishment emphasizes that failures are deviant, that they do not naturally belong in the organization...”

Sidney W.A. Dekker, Ten Questions about Human Error: A New View of No blame post-mortems

Page 28: From DevOps to Operations Science

http://www.flickr.com/photos/lighttable/4981112645/sizes/o/in/photostream/

“The number 1 thing we can’t do is get in people’s way.”

Phil Dibowitz, Facebook

Become allergic to things that make you slow

Page 29: From DevOps to Operations Science

Re-enforce culture with technology, and vice versa

“Tooling is culture institutionalized”

- Adam Jacob

Page 30: From DevOps to Operations Science

Still with me?

Page 31: From DevOps to Operations Science

• Christopher Brown• Chief Technical Officer• Twitter: @skeptomai, Email: [email protected]