a devops adoption playbook- achieving business value at scale

38
DTA-1460 : A DevOps Adoption Playbook: Achieving Business Value at Scale Sanjeev Sharma CTO, DevOps Technical Sales and Adoption, Distinguished Engineer Lee Reid Executive IT Specialist | IBM Cloud Unit

Upload: sanjeev-sharma

Post on 12-Jan-2017

956 views

Category:

Software


0 download

TRANSCRIPT

Page 1: A DevOps adoption playbook- achieving business value at scale

DTA-1460 : A DevOps Adoption Playbook: Achieving Business Value at Scale

Sanjeev SharmaCTO, DevOps Technical Sales and Adoption, Distinguished EngineerLee ReidExecutive IT Specialist | IBM Cloud Unit

Page 2: A DevOps adoption playbook- achieving business value at scale

Please Note:

1

• IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s solediscretion.

• Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision.

• The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract.

• The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

• Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

Page 3: A DevOps adoption playbook- achieving business value at scale

Agenda

2

• DevOps refresher• Multi-Speed IT and DevOps• DevOps Adoption Patterns• Culture• Where do I start?

Page 4: A DevOps adoption playbook- achieving business value at scale

DevOps Refresher

Page 5: A DevOps adoption playbook- achieving business value at scale

4 © IBM Corporation

DevOps: Origins

Page 6: A DevOps adoption playbook- achieving business value at scale

What does the Line of Business want from IT?

Product Owner

Senior Executives

Users Domain ExpertsAuditors

Gold Owner Support Staff

External System Team

OperationsStaff

Team MemberTeam Lead

Team MemberTeam Member

Line-of-business CustomerIT

Agility - Velocity - Innovation

Page 7: A DevOps adoption playbook- achieving business value at scale

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

6

People

Process

Line-of-business

Customer

1

3

2

1. Get ideas into production fast2. Get people to use it3. Get feedback

Continuously Improve:I. Application DeliveredII. Environment DeployedIII. Application and Environment Delivery Process

Page 8: A DevOps adoption playbook- achieving business value at scale

The Real World is Multi-SpeedAdopting DevOps for Multi-Speed IT

Page 9: A DevOps adoption playbook- achieving business value at scale

8

Adopting Multi-Speed IT

Industrialized CoreDeliver at regular cadence • Waterfall -> Agile • Stability • Predictability • Lean Delivery pipeline • Core

and LegacyHybrid Infrastructure – Physical, Cloud • IaaS/PaaS

Agile/Innovation EdgeRapid Delivery for Innovation • Agile • Antifragile • Experimentation • New and Innovative

Hybrid Cloud • PaaS

Partner EcosystemAPI Economy • Monetization •

Service providers and consumers

APIs

APIs

APIs

Cloud Enabled/Legacy Systems

Cloud Native Systems

Evolving to an agile enterprise with Hybrid IT: https://ibm.biz/BdHhdg

Page 10: A DevOps adoption playbook- achieving business value at scale

Differing Assumptions: Cloud Ready v Cloud Native

• Industrialized Core (Cloud Ready) Assumptions– The infrastructure provides my NFR’s.– The infrastructure is stable.– The components of my application are co-located.– My ops team controls the production servers.– If a disaster happens, it’s someone else’s responsibility to fix it.

• Innovation Edge (Cloud Native) Assumptions– My application and my services provide my NFR’s.– The infrastructure is constantly changing (elastic).– My application components may be globally distributed.– As a Dev/Ops team member I control the production servers.– If a disaster happens, it’s my responsibility to make sure my app stays up.

Choosing one or the other has an effect on yourteam composition and roles

Page 11: A DevOps adoption playbook- achieving business value at scale

Adopting Multi-Speed IT World – Transformation

Industrialized CoreTraditional Development -> DevOps, Legacy -> Cloud-ready

Traditional Middleware -> Middleware on Cloud, APIs, Software Defined Infrastructure

Agile/Innovation EdgeTraditional Development ->

Cloud Native, 12-factor Apps, DevOps, PaaS

Partner EcosystemPoint-to-Point Integration -> API

Economy

APIs

APIs

APIs

Page 12: A DevOps adoption playbook- achieving business value at scale

Adopting Multi-Speed IT– Implementation

Industrialized CoreUrbanCode • IBM Rational Tools • Middleware Portfolio • API Management

IBM Cloud Orchestrator • IBM PureApplication • Gravitant • Docker

Agile/Innovation EdgeIBM Bluemix Platform • Containers • Microservices

IBM Garage Method

Partner EcosystemAPI management

APIs

APIs

APIs

Page 13: A DevOps adoption playbook- achieving business value at scale

Patterns of DevOps Adoption

Page 14: A DevOps adoption playbook- achieving business value at scale

Three Key Business Drivers

1. Optimization 2. Innovation3. Scaling for Enterprise Value

Page 15: A DevOps adoption playbook- achieving business value at scale

Optimization

Page 16: A DevOps adoption playbook- achieving business value at scale

Where does DevOps Adoption Start?

ProductionDevelop Build Test DeployPlan

By the end of 2015, 75% of large organizations are expected to have adopted agile DevOps practices (IDC)

Agile Adoption

Water-SCRUM-fall

Page 17: A DevOps adoption playbook- achieving business value at scale

Creating a ‘Lean’ Delivery Pipeline

• Reduce Batch size

• Integrated Delivery Pipeline• Agile Product Management• ‘Continuous Funding’• Right Architecture• Continuous Improvement

1 per min 1 per min

4 per min 1 per min

4 per min 4 per min

Page 18: A DevOps adoption playbook- achieving business value at scale

‘Shift Left’ Ops Engagement• Deploying Infrastructure is the biggest

bottleneck for the Delivery Pipeline – Extending the Agile Manifesto: Working software

over comprehensive documentation -> Working software (in Production or production-like environment) over comprehensive documentation

• Software Defined Environments to enable Environment Standardization with pre-defined ‘Patterns’

– Servers are ‘Cattle’, not ‘Pets’

• Practitioner self-service access to environments

• Engage Operations early - One Team

Application Changes

InfrastructureChanges

Page 19: A DevOps adoption playbook- achieving business value at scale

Full Stack Deployment

Composite Applications

Components

Re-usable Workflows Environment Management

SIT

PROD

The “What”

The “How”

The “Where”

Deployment Automation

Page 20: A DevOps adoption playbook- achieving business value at scale

Rapidly deploy application environments in 3 simple steps

Provideportabilityacrossheterogeneousvirtualdatacenter,privateandpublicclouds

3. Portableacrossdifferentvirtualizedinfrastructure

Assemblemulti-tierapplicationenvironmentsanddefineauto-scalingpoliciestomeetoperationalneeds.

2. Assemblemulti-tierandscalableenvironmentblueprints

1. Createstacks

Load Balancer

Web Servers

App Servers

Database Servers

Firewall

DescribefullstackenvironmentsusinginfrastructurebuildingblockslikeImages,Middlewarescripts,andApplicationcode

VMware vCenter

Private PublicVirtual Datacenter

Application

Middleware ConfigMiddlewareOS ConfigHardwareEn

viro

nmen

t B

luep

rint Policies

Page 21: A DevOps adoption playbook- achieving business value at scale

Hybrid Cloud Deployments through a Single Point of Control

IBM Bluemix

On-prem Traditional IT

IBMCloudOrchestratorIBMPureApplicationSystem

Manage application deployment across dev, test, and production spanning multiple clouds

Key Points:• Enable full stack deployments (OS, patterns

and applications) across hybrid cloud applications

• Establish common toolchain framework with plug points to support continuous delivery

Docker

UrbanCodeDeploy

UrbanCode Release

IBMDev-TestEnvironmentasaService(IDTES)

Page 22: A DevOps adoption playbook- achieving business value at scale

Innovation

Page 23: A DevOps adoption playbook- achieving business value at scale

The Twelve-Factor App• A set of best practices for creating applications

– Implementing, deploying, monitoring, and managing• Typical modern applications

– Deployed in the cloud– Accessible as web applications that deliver software-as-a-service

• Can be applied to any application– Implemented in any programming language– Using any backing services (database, messaging, caching, etc.)

• Addresses common problems– The dynamics of the organic growth of an app over time– The dynamics of collaboration between developers– Avoiding the cost of software erosion– Systemic problems in modern application development

• Provides a shared vocabulary for addressing these problems

Sources: http://www.12factor.nethttp://www.clearlytech.com/2014/01/04/12-factor-apps-plain-english/

Page 24: A DevOps adoption playbook- achieving business value at scale

IBM Architecture Center

RUNTIMES &CONTAINERS

BLUEMIX

DELIVERY PIPELINESOURCE CONTROL

.js

LIVE SYNC

WEB IDE ACTIVE DEPLOY MONITORING & ANALYTICS

AUTO SCALING ALERT NOTIFICATION

SECURE GATEWAY API MANAGEMENT

TRACK & PLAN

MOBILE QUALITYASSURANCE

PRESENCEINSIGHT

1

2

3 4

5

6 7

8

811 910

12

CUSTOMERANALYTICS

DevOps

https://developer.ibm.com/architecture/

Page 25: A DevOps adoption playbook- achieving business value at scale

Scaling for Enterprise Value

Page 26: A DevOps adoption playbook- achieving business value at scale

Delivering a Business Capability – Hybrid Applications, Hybrid Platforms, Hybrid Teams

Application A

Application B

Application C

Application N

Business Capability

Page 27: A DevOps adoption playbook- achieving business value at scale

26

Adopting Multi-Speed IT - Touchpoints

Industrialized Core

Agile/Innovation Edge

Partner EcosystemAPI Economy • Monetization •

Service providers and consumers

APIs

APIs

APIs

Cloud Enabled/Legacy Systems

Cloud Native Systems

Evolving to an agile enterprise with Hybrid IT: https://ibm.biz/BdHhdg

APIsTest

Virtualization

Release Manage

mentPlanning

Page 28: A DevOps adoption playbook- achieving business value at scale

Orchestrating Complex Releases

• Keep track of the inventory across the entire life cycle of the release• Control the entire release lifecycle in an easy to use view

Page 29: A DevOps adoption playbook- achieving business value at scale

DevOps Multi-Speed IT ArchitectureIBM Architecture Center

BLUEMIX

DELIVERY PIPELINESOURCE CONTROL

.js

LIVE SYNC

WEB IDE ACTIVE DEPLOY

AUTO SCALING

SECURE GATEWAY

ON-PREMISES SYSTEMS

API MANAGEMENT

TRACK & PLAN

TRACK & PLAN DEVELOP BUILD DEPLOY

RELEASE TEST

RUNTIME ENVIRONMENTS

RUNTIMES &CONTAINERS

1

2

3

6 7

9

10

8

1

2

4

5

10

https://developer.ibm.com/architecture/

Page 30: A DevOps adoption playbook- achieving business value at scale

IBM UrbanCode Release

Legacy Stack On-Prem Cloud

Rational Test WorkbenchIBM UrbanCode Deploy

ProvisionApplication

Infrastructure

Private Cloud

Pattern Engine

ProvisionApplication +Infrastructure

Platform as a Service(Public)

BlueMix

Infrastructure

System z and/or Distributed Applications

ProvisionApplication +Infrastructure

BlueBoxIBM Container Service

AP

I Gatew

ay

CloudFoundry ‘Community’ Buildpacks

IBM DevOps Services

APIs

APIs

Off-Prem Cloud

Infrastructure

IBM Cloud Orchestrator

Pattern Engine

ProvisionApplication +Infrastructure

DevOps Multi-Speed IT – Implementation

Aspera

Page 31: A DevOps adoption playbook- achieving business value at scale

Creating a DevOps Culture And now for the hard part…

Page 32: A DevOps adoption playbook- achieving business value at scale

Building a DevOps Culture

• Setup a DevOps Center of Excellence• Everyone is responsible for Delivery,

including external Stakeholders• Common Measures of Success

It’s all about the people!

Page 33: A DevOps adoption playbook- achieving business value at scale

Start Here:Value Stream Mapping for Identifying and Addressing bottlenecks

Page 34: A DevOps adoption playbook- achieving business value at scale

Mapping your Delivery Pipeline

Idea/Feature/Bug Fix/Enhancement

Production

Development Build QA SIT UAT Prod

PMORequirements/

Analyst

Developer

CustomersLine of Business

BuildEngineer

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

Page 35: A DevOps adoption playbook- achieving business value at scale

Questions?

34

Page 36: A DevOps adoption playbook- achieving business value at scale

Notices and Disclaimers

35

Copyright © 2016 by International Business Machines Corporation (IBM). No part of this document may be reproduced or transmitted in any form without written permission from IBM.

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM.

Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for accuracy as of the date of initial publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to update this information. THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IN NO EVENT SHALL IBM BE LIABLE FOR ANY DAMAGE ARISING FROM THE USE OF THIS INFORMATION, INCLUDING BUT NOT LIMITED TO, LOSS OF DATA, BUSINESS INTERRUPTION, LOSS OF PROFIT OR LOSS OF OPPORTUNITY. IBM products and services are warranted according to the terms and conditions of the agreements under which they are provided.

Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice.

Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary.

References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business.

Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the views of IBM. All materials and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or their specific situation.

It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer’s business and any actions the customer may need to take to comply with such laws. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is in compliance with any law

Page 37: A DevOps adoption playbook- achieving business value at scale

Notices and Disclaimers Con’t.

36

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. IBM does not warrant the quality of any third-party products, or the ability of any such third-party products to interoperate with IBM’s products. IBM EXPRESSLY DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

The provision of the information contained h erein is not intended to, and does not, grant any right or license under any IBM patents, copyrights, trademarks or other intellectual property right.

IBM, the IBM logo, ibm.com, Aspera®, Bluemix, Blueworks Live, CICS, Clearcase, Cognos®, DOORS®, Emptoris®, Enterprise Document Management System™, FASP®, FileNet®, Global Business Services ®, Global Technology Services ®, IBM ExperienceOne™, IBM SmartCloud®, IBM Social Business®, Information on Demand, ILOG, Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®,PureData®, PureExperience®, PureFlex®, pureQuery®, pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, Smarter Commerce®, SoDA, SPSS, Sterling Commerce®, StoredIQ, Tealeaf®, Tivoli®, Trusteer®, Unica®, urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and System z® Z/OS, are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at: www.ibm.com/legal/copytrade.shtml.

Page 38: A DevOps adoption playbook- achieving business value at scale

Thank YouYour Feedback is Important!

Access the InterConnect 2016 Conference Attendee Portal to complete your session surveys from your

smartphone, laptop or conference kiosk.