Pulse 2013: DevOps Review and Roadmap

CDO-1884: DevOps
Review and Roadmap
Daniel Berg, Chief Architect for DevOps
Ruth Willenborg, DE, Cloud and DevOps
Andrew Hans, Senior Dev Manager DevOps

© 2012 IBM Corporation

Please note

IBM’s statements regarding its plans, directions, and intent are subject to change or
withdrawal without notice at IBM’s sole discretion.
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.

1

Businesses are challenged to meet time pressures with
quality software

….34% of all new IT Projects deploy late*

41% 51%
applications rolled
45%
experience delays
experience delays
in integration, configuration back due to quality due to troubleshooting
and issues escaping and fine-tuning issues
testing of applications* into production* in production*

Business Line of Development IT Operations
Owners Customers
Business & Test

GAP GAP

Up to 4-6 Weeks to deliver a simple code change**

*

Forrester/IBM
Study:
A
New
View
of
IBM’s
Opportunity
for
Integrated
Op>mized
Systems
Address
,
2011

**
Forrester
“Five
Ways
To
Streamline
Release
Management”,

2011
2

Patterns of challenges

Diﬀerences
in
dev
and
Backlog
of
agile
Manual
(tribal)
Lack
of
feedback
and

ops
environments
releases
that
Ops
processes
for
release
quality
metric
leads
to

cause
failures
cannot
handle
lack
repeatability/ missed
service
level

speed
targets

Dev Who did
this last
time?
Daily
Build Dave…

Prod Dave’s
not here
Monthly
Delivery man…

3

Software delivery is at the heart of today’s top technology trends

Big Data
New applications provide
insights by interpreting
massive quantities of data
Collaboration
Cloud
Development and Operations teams High application demand requires
work in continuous application fast, scalable environments
delivery cycles for development / testing

Mobile Apps
Intelligent/
Modern workforce expects Connected Systems
constantly updated
Software Delivery! The software component
software to connect to
in smart products drives value
enterprise systems
and competitive differentiation

4

Our view of DevOps

A core enterprise capability for…

§  Continuous delivery of software to
People
§  Seize market opportunities and
Process
§  Make rapid improvements based on customer
Tools
feedback while

§  Balancing speed, quality, and costs

5

Cultural challenges adopting DevOps

Operator Developer

Application deployment failed again Why does it take so long to get a test
because of new libraries. environment?

Our processes ensure environment I like using new open source libraries.
stability.
I’ve checked in my code now it just
Development is always making bad needs to be deployed (easy).
operational decisions.

CDO-‐1511:
How
IBM
Leverages
SmartCloud

CDO-‐1741:
ShadowOps
versus
DevOps

Con>nuous
Delivery
to
Streamline
DevOps

6

DevOps Principles and Values

§  Develop and test against a production-like
system

§  Iterative and frequent deployments using People
repeatable and reliable processes
Process
§  Continuously monitor and validate operational
Tools
quality characteristics

§  Amplify feedback loops

7

Standardize Plan & Track Manage Changes Automate Delivery Feedback

IBM Workload
Deployer

IBM
PureApplication
Ra#onal
Team
Concert
Provisioning
Systems

Agile
Deployment
of

Development
Virtual
Systems

8

Standardize
Communicate and share environment patterns

Issues
§  Dev environments different
from production environments
§  Difficult to provision test
environments
§  Environment provisioning
creates new “snowflakes”

Solution
§  Define standard Virtual System
Patterns for environments
§  Share patterns between Dev
and Ops to improve
communications Func>onal

User
Acceptance

§  Repeatable and reliable Veriﬁca>on

Test
Environment

process to provision base Test
Environment

environments (rubber stamps)

9

Plan and Track
Common tools to plan and track changes across Dev and Ops

Issues
§  Configuration tasks are not
planned or tracked
§  Different tools/processes for
tracking work

Solution
§  Use collaborative development
tools to track and plan
application and configuration
changes
§  Ensures work is properly
planned in the proper order
§  Ensures audit trail for planned
changes to environments

10

10

Manage Changes
Version and manage application and configuration changes
Issues
§  Configuration changes vary
between environments
§  Configuration changes are not
well managed
§  Release artifacts are randomly
created and applied

Solution
§  Version control configuration
changes as code in an SCM close
to the application changes
§  Version and track release artifacts
in an Artifact Library
§  Track release dependencies

11

Automate Delivery
Repeatable and reliable processes

Issues
§  Application deployment is
generally an unreliable, manual
process
§  Difficult to replicate
§  Slow to execute
§  Long delays between
deployments increases size of
change sets making problem
determination difficult

Solution
§  Tooling to define and configure
an automated delivery process
§  Reliable and repeatable
delivery process
§  Deploy early and often to “fail
fast” and resolve even faster
12

Feedback
Immediate feedback of changes

Issues
§  Weeks, months pass before
getting any feedback of a change
(if any)
§  Often cannot determine where/if
a build was deployed
§  Long delays in feedback makes
problem determination more
difficult

Solution
§  Report results of automated
delivery process directly in
context of development tools
§  Preserve traceability of delivery
output with build process
§  Report automated tests results in
a timely fashion
13

Enterprise capability for continuous delivery of software
innovation

DevOps Lifecycle
Customers Business Owners Development/Test Operations/Production

Continuous Feedback and Improvements

Business Planning

Collaborative Continuous Continuous
Development Testing Release

Continuous Monitoring

Continuous Delivery

Open Lifecycle Integration Platform

14

DevOps capabilities for continuous testing
Collaborative Development Continuous Testing Continuous Release

Build
Quality

Automa>on
Management

Applica>on

Environment

Release

Provisioning

Automa>on

Change
Source
Control
Test
Service

Management
Management
Automa>on
Virtualiza>on


Applica>on
Performance
Monitoring

Delivery
Pipeline
Continuous Delivery

Open Lifecycles Integration Platform

15

DevOps tool chain for continuous testing
Collaborative Development Continuous Testing Continuous Release

IBM
SmartCloud

Build

IBM
Ra>onal
Quality
a>onal

IBM
R
Jenkins
Provisioning

Automa>on

Build
Forge
Management

Quality
Manager

Chef

IBM

Applica>on
Workload

IBM
Ra>onal
Environment

Release
Deployer

Automa>on
Provisioning

Automa>on

Framework
IBM
Pure

Change
IBM
Source
Control

Ra>onal

IBM
Ra>onal

Systems

Test
Service

Management
Team
Concert

Management
Test
Workbench

Automa>on
Virtualiza>on


IBM
SmartCloud
Applica>on

Applica>on
Performance
Monitoring

Performance
Management

IBM
SmartCloud

Delivery
Pipeline

Con>nuous
Delivery
Continuous Delivery

Open Lifecycles Integration Platform

16

IBM SmartCloud Continuous Delivery flow

Test Automation
Cloud Platform Provider

Developer Tools Execute
Request
tests
cloud
resources
Provision
Deliver resources
changes
Automation Agent
Post results
(execute delivery process)

Source Control and Change
Management server Publish
packages
Retrieve
packages
Trigger
delivery
Artifact Library
Post
changes
Virtual System

Publish
Build Server packages

17

17

Discover where we are going next

18

End-to-end release planning
Real-time feedback for the delivery of business value
Business Planning Development Planning

Focal Point Team Concert

Business Dev Release
Need Project Plan Story

Build

Requirements Composer Quality Manager

Requirement Test Plan Test Case
New
integration

Application Release Management

SmartCloud Continuous Delivery SmartCloud Orchestrator

New Application
Environment
Virtual New
Release System
Feature!
19

Continuous testing with virtualized services Continuous Feedback and Improvements

Avoid testing bottlenecks due to dependencies on
Business Planning
Collaborative Continuous Continuous

external services
Development Testing Release
Continuous Delivery
NEW!
Continuous testing using
Green Hat virtualized
services in the Cloud

Rational Test Workbench Application changes
being tested

SmartCloud
Databases Mainframe Third-party
Continuous Delivery applications Services
virtualized services
Rational Test Virtualization Server

•  Automate setup and management of test
virtualization server in the cloud
•  Automates configuration of virtualized IBM SmartCloud Provisioning
services for an application under test
IBM Workload Deployer
•  Automate setup of production-like test
environments with low cost IBM PureApplication System
20

Multi-stage Continuous Delivery Pipelines
Pipeline
dashboards
provide

feedback
for
the
ﬂow
of

changes
through
the

SCM Changes
trigger
Artifact pipeline

(Source code & pipeline
Library
configurations) execu>on

Delivery Pipeline

QA Stage

Pre-
Build Promote to
Production
Production
Business Owners
Stage Stage Customers

Performance
Stage

Approval
gates
with

Each
stage
deﬁnes
tasks
to
automated/manual

provision
an
environment
Stages
can
be
run
in
parallel
approvals
provide

with
entrance
and
exit
compliance
checking

criteria

21

Rational Development and Test Environment for System z
Continuous build and test of distributed systems

DevOps Lifecycle


IBM
Con>nuous

Integra>on
Solu>ons

COBOL, PL/I, C++, Java, EGL, Batch,
for
System
Z
Assembler, Debug Tool

IMS DB2
CICS
IBM
Ra>onal
Test
WAS MQ
Workbench

z/OS
New

integraDon

x86 PC running Linux
IBM
SmartCloud

Con>nuous
Delivery

Note: This Program is licensed only for development and test of applications that run on IBM z/OS. The Program may not be used to run production workloads of any kind, nor more
robust development workloads including without limitation production module builds, pre-production testing, stress testing, or performance testing.

22

22

Continuous delivery for mobile
There are mobile-specific challenges in achieving continuous delivery
§  Device fragmentation §  Builds are pulled from app-stores vs push
§  Additional governance required §  Injection of app-store feedback into delivery
§  Curated app-stores impose review processes process
§  Device testing is difficult §  Native plus back-end services required for
mobile applications

DevOps Lifecycle

March

BETA

IBM
Ra>onal
Test

Workbench
for
Mobile

Business Planning
Device Anywhere Mobile simulator
Collaborative
IBM
Mobile
Development
Continuous Continuous
Development
Lifecycle
Solu>on
Testing Release
AppCenter


IBM
SmartCloud

Continuous Delivery
Con>nuous
Delivery

New

Open Lifecycle Integration Platform
integraDon

23

Open, dynamic orchestration of resources, workloads and services

New

•  Fully automates the deployment and
lifecycle management of cloud services
Orchestrator Open Beta across resources, workloads and services"
•  Built on a foundation of open standards –
TOSCA, OpenStack, OSLC"
•  Accelerated deployments with reusable
workload patterns and Chef recipes"
•  Uniﬁed management of heterogeneous
environments"
•  Supports deployment of hybrid & public
clouds"
Continuous delivery pipeline
•  Works with SmartCloud Continuous Delivery
to provide extended DevOps platform"

Reduce
>me-‐to-‐market
to
deliver
new
business
services

Improve
administrator
produc>vity
24

© 2013 IBM Corporation | IBM Confidential until 11am ET March 4th, 2013

Managing workloads across the lifecycle requires orchestration

!
Network Monitoring !
Domain!
IT
Monitoring IT Asset
Storage
Storage Management" Management!
Domain"
Domain"
Domain!
Data
ComputeAvailability Network
Change
Domain Domain" Domain"
Management!

Orchestration
Engine Web App DB Service
Desk!

Provision Pattern

Resource Orchestration! Service Orchestration
Onboard, provision, manage Workload Orchestration
Workload aware placement, Manage the lifecycle of
CPU, Storage and
Network optimization and operation business applications
25

Extended platforms

Ra#onal
Team
Concert

IBM
SmartCloud
Orchestrator

Agile

Development

More clouds More patterns
EC2 TOSCA
Virtual Applications

26

SmartCloud Orchestrator Promotion Control
Orchestrator

Drive Build Promotion OpsCode
Chef

Chef
Server

Retrieve list of builds

Hosted
Chef

Change environment mappings

Change

Integrated instance

Approval environments

Processing

DEV

QA

PROD

Continuous
Delivery Deliver and
inst

inst

inst

test new builds

Your Infrastructure
Pedestal
74:
Marrying
Apps
&
Infrastructure:
Deliver
Working
Code
More
Quickly
and
with
Greater

Consistency
than
Ever
Before
27

How we plan to get there …

Phase 1 Phase 2 Future

Con>nuous
tes>ng
with
End-‐to-‐end
release

Simpliﬁed
developer

Service
Virtualiza>on
planning

experience
for
building

engaging
systems

New
Placorms:
Mul>-‐stage
pipelines

Openstack
&
SmartCloud

Orchestrator
Con>nuous
delivery
for

Mobile
and
Mainframe

28

Summary

§  Challenges to deliver
software-driven innovation

§  Disruptive technologies
driving greater need to
innovate

§  DevOps is critical to your
success

§  IBM has first class DevOps
solutions and is continuing to
invest and improve upon
these solutions
29

We want to hear you!

Workshop: DevOps / Continuous Delivery
•  60-minute, small group discussion (fewer than 10)
•  Hosts:
•  Neeraj Chandra, VP - Strategy
•  Randy Newell, Director - Capabilities Marketing

Tuesday, March 5, 5:15 – 6:15 pm pt
Pulse Expo Hall - Marquee Ball Room, Room B5

Limited seats – please RSVP: RNewell@us.ibm.com or 203-521-9157

30

3
0

The IBM Technical Summit

Top Five Reasons to Attend
Learn how you can make the most of Agile, DevOps,
Cloud, Mobile, Big Data, Social Business and other key
trends to release products faster, improve processes,
increase quality, and meet business objectives.
Get detailed Rational technical training trough hundreds of
breakouts, hands-on technical workshops, open labs and a
wide variety of certification testing

Explore Innovation Labs, observe interoperability in
action and meet face to face with experts in a high-
energy Exhibit Hall. Innovate 2013: The IBM Technical Summit
is the event for software practitioners and
Network with over 4000 attendees from around the world product developers. Attendees will learn to
and collaborate with your peers from a wide variety of roles,
industries and locations.
improve the practices, predictability and
economics of software delivery through
Enjoy top-notch keynotes and entertainment, detailed education and insights into key
including strategic presentations, dynamic guest
technical trends!
speakers and customer success stories.

Register by March 15 and save $300!
ibm.com/innovate

Acknowledgements and Disclaimers:
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.

© 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.
§  Please update paragraph below for the particular product or family brand trademarks you mention such as WebSphere,
DB2, Maximo, Clearcase, Lotus, etc

IBM, the IBM logo, ibm.com, [IBM Brand, if trademarked], and [IBM Product, if trademarked] 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 3rd party trademark names/attributions here]
Other company, product, or service names may be trademarks or service marks of others.
32

Pulse 2013: DevOps Review and Roadmap

More Related Content

What's hot (20)

Similar to Pulse 2013: DevOps Review and Roadmap (20)

More from Daniel Berg (9)

Recently uploaded (20)

Pulse 2013: DevOps Review and Roadmap