CampDevOps keynote - DevOps: Using 'Lean' to eliminate Bottlenecks

© 2013 IBM Corporation

DevOps – Adopting Lean Thinking to Eliminate Bottlenecks

Sanjeev Sharma IBM WorldWide Lead – DevOps Technical Sales DevOps Blog: http://bit.ly/sdarchitect Twitter: @sd_architect Author: DevOps For Dummies – http://ibm.co/devopsfordummies



Agenda

•  A ‘Lean’ View of DevOps •  Addressing Bottlenecks with DevOps

o  Shift Left Test o  Full Stack Deployment o  It’s all about the People


DevOps is a Philosophy

Source: http://virtualplatosacademy.blogspot.com/p/great-philosophers.html


DevOps approach: Apply Lean principles accelerate feedback and improve time to value

Line-of-business

Customer

1

3

2

1.  Get ideas into production fast 2.  Get people to use it 3.  Get feedback

Change speed must be an asset, Not an anchor

Non-Value-added waste Value-added production work

DevOps Transformation

© 2013 IBM Corporation 6

DevOps: Using Lean Thinking to Eliminate Bottlenecks

Type of Waste Create Feature Deliver Feature Unnecessary Overhead

Communicating ideas/knowledge Communicating between development and operations

Unnecessary Re-work

Tasks assigned back to developers from testing and usage

Tasks assigned back to developers from production rollbacks

Over-production

Unnecessary functionality produced Unnecessary hardware, data center, personnel

Non-Value-added waste Value-added production work

DevOps Transformation


Map your Bottlenecks

Idea/Feature/Bug Fix/ Enhancement

Production

Development Build QA SIT UAT Prod

PMO

Requirements/ Analyst

Developer

Customers Line of Business

Build Engineer

QA Team Integration Tester User/Tester Operations

Artifact Repository

Deployment Engineer

Release Management

Code Repository

Deploy

Get Feedback

Infrastructure as Code/ Cloud Patterns

Feedback

Customer or Customer Surrogate

Metrics - Reporting/Dashboarding

Tasks

Artifacts


Agenda




Testing too little, too late…

9


Unleashing the Power of Shift Left Testing

What shifts left? Design verification è Integration Testing

§ Why?

Integration Test Investments

Unit Test Investments

Shift Left Shift Right

Unit tests uncover code defects that cause

benign breakage in a single unit

Integration testing uncovers design and architectural defects

that cause malignant breakage across multiple units

© 2013 IBM Corporation Project Delivery Time

Bui

ld P

rogr

ess

40% Rework 15-20%

Rework

•  Waterfall Governance •  Proprietary tools/methods •  Unit test first, then Integration

•  Agile/Lean methods •  Mature commercial tools •  Integration first

Shift Left Testing: Less Rework and Delay

Target Date

Delayed Date


Databases Internal Messages

Third-party Services

virtual components

Simultaneously test across

multiple test stages

Dev QA

IBM Rational Test Virtualization

Server

Deploy

Provision

Test

Deploy what is ready, Virtualize the rest

IBM UrbanCode Deploy

IBM Rational Test Workbench

{ integrated with

Test Environments

Dynamic Infrastructure

Deploy what is ready, virtualize the rest

Continuously test in production-like env.

Test using real world network conditions n Network

Virtualization


Agenda


o  Shift Left Test o  Full Stack Deployment o  People and ‘Shift Left’


Full Stack Deployment

14


Using Patterns to define ‘Full Stack’ Environments

What’s required… What the business wants… What a pattern automates…

Patterns of Expertise:

Proven best practices and expertise learned from decades of client and partner engagements

•  Pre-defined architecture of an application or Cloud service

•  Captures best practices for complex tasks •  Optimized into a deployable form for private

or public cloud •  Repeatable deployment with full lifecycle

management reducing operational costs


OpenStack HEAT: The Future of Cloud ‘Patterns’

16


Introducing Web-based HOT Editor! – visual and textual


o  Provide Software Components right along side infrastructure

o  Represent these resources in HOT documents

o  Once deployed update either from Heat or UrbanCode Deploy

o  Will support Chef, Puppet, etc over time

IBM UrbanCode Deploy & Heat Templates


•  Organic environments

•  Version-aware

•  Full-stack engineering

•  Composable content

•  Cloud agnostic

Cloud Pattern Designer HOT document editor & Environment

lifecycle management tool

A full-stack engineering solution for designing, deploying, and managing environments

Components

Resources

Heat Templates (HOT) Building

Blocks

HOT Executes on

Next generation pattern development and lifecycle management

OpenStack Heat

Tool

Engine

Platforms


Agenda


o  Shift Left Test o  Full Stack Deployment (…or just use a PaaS) o  It’s all about the People


PaaS

21

© www.dilbert.com


DevOps as a Service (Platform as a Service)

Developer

Running Application (Dev Space)

Create & edit

Running Application (test) Running Application

(Prod Space) Running Application (Test Space)

Everything is a service in the Cloud

Deploy & test

Build Publish build

Deploy

Promote

Test as a Service

Test

Monitoring as a Service

Monitor

Dev as a Service Build as a Service Deploy as a Service


Codename: BlueMix – IBM Platform as a Service (PaaS) Delivering a Composable Services development environment

Run Your Apps The developer can chose any language runtime or bring their own. Just upload your code and go.

DevOps Development, monitoring, deployment and logging tools allow the developer to run the entire application with JazzHub and Mobile Quality Assurance

APIs and Services A catalog of open source, IBM and third party APIs services allow a developer to stitch together an application in minutes.

Cloud Integration

Build hybrid environments. Connect to on-premises systems of record plus other public and private clouds. Expose your own APIs to your developers.

Extend SaaS Apps

Drop in SaaS App SDKs and extend to new use cases (e.g,. Mobile, Analytics, Web) !


IBM DevOps Services for Cloud (SaaS)

!

Open, integrated rapid development experience that scales

Try it: Open Beta @ www.bluemix.net

•  Git hosting as a Service •  Web based IDE •  Agile planning & tracking, team

collaboration as a Service (Jazz.net) •  Mobile Quality Assurance (MQA) as

a Service •  Continuous Integration as a Service

(Jenkins as a Service) •  Deployment Automation as a

Service (powered by UrbanCode Deploy)

•  Performance Monitoring as a Service


Agenda




People

26


Building a DevOps Culture •  Everyone is responsible for Delivery

•  Common measures of Success

•  Right People are needed

Product Owner

Team Member

Team Lead

Team Member

Team Member

Senior Executives

Users Domain Experts

Auditors

Gold Owner Support Staff

External System Team

Operations Staff

It’s all about the People/Culture


DevOps Adoption Model

Inefficient Leaner Leaner and Smarter

Efficiency Productive : Waste

Collaborative Silo-ed More Continuous

Process-based

Process-heavy Agile More Predictable

Manual Automated More Transparent

Steer Plan, decide, specify,

architect, sense and respond

Develop/Test Design, code, build,

release internal, test, and verify

Operate Monitor, tune,

and validate

Deploy Build, deliver external,

and validate

Optimizing Product-based …

…

…

…

http://bit.ly/IBMDevOpsAssess


§  DevOps Lean Assessment (Beta): http://bit.ly/IBMLeanAssess

§  IBM DevOps Page: http://ibm.com/DevOps

§  DevOps For Dummies Book: http://ibm.co/devopsfordummies

§  Release and Deploy For Dummies Book: http://ibm.co/1bplaQV

§  IBM DevOps YouTube Playlist: http://bit.ly/1fiDOtl

Resources


© Copyright IBM Corporation 2013. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.


Acknowledgements and disclaimers

31

© Copyright IBM Corporation 2013. All rights reserved. –  U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM, the IBM logo, ibm.com, Rational, the Rational logo, Telelogic, the Telelogic logo, Green Hat, the Green Hat logo, and other IBM products and services are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml If you have mentioned trademarks that are not from IBM, please update and add the following lines: [Insert any special third-party trademark names/attributions here] Other company, product, or service names may be trademarks or service marks of others.

Availability: References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates.

The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are provided for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice to any participant. While efforts were made to verify the completeness and accuracy of the information contained in this presentation, it is provided AS-IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this presentation or any other materials. Nothing contained in this presentation is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.

All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.

CampDevOps keynote - DevOps: Using 'Lean' to eliminate Bottlenecks

Technology

Transcript of CampDevOps keynote - DevOps: Using 'Lean' to eliminate Bottlenecks