IBM Innovate 2013 Session: DevOps 101

DevOps 101
Concepts and Overview
Sanjeev Sharma (@sd_architect)
Rational Specialty Architect and DevOps SME
sanjeev.sharma@us.ibm.com
DevOps Blog: http://bit.ly/sdarchitect
IBM Software Group
Session #: DR-1147
© 2013 IBM Corporation

2
Please note the following
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.

Agenda
• Why DevOps?
• What is DevOps?
• Understanding DevOps
• The flavors of DevOps
• Adopting DevOps
• IBM DevOps Reference Architecture
• IBM DevOps Solution

5
54%
of companies believe software delivery is critical
25%
leverage software delivery effectively today
But only…
69%
outperform
those who don’t
leverage
software delivery
effectively
Source: “The Software Edge: How effective software development drives competitive advantage,” IBM Institute of Business Value, March 2013
Software Delivery is critical to success

And a lack of continuous delivery
impacts the entire business
6
Costly, error prone
manual processes and
efforts to deliver software
across an enterprise
CHALLENGES
Upgrade risk due to
managing multiple application
configurations and versions
across servers
Slow deployment
to development and test
environments leave teams
waiting and unproductive
CHALLENGES
Operations/
Production
Development/
TestCustomers
Business
Owners
Software glitch costs
trading firm Knight
Capital $440 million
in 45 minutes
A bad software upgrade
at RBS Bank left
millions unable to access
money for four days
New Zealand’s biggest phone company,
Telecom paid out $2.7 million to some
47,000 customers who were
overcharged after a software glitch

Patterns of challenges
Differences in dev
and ops
environments
cause failures
Backlog of agile
releases that Ops
cannot handle
Manual (tribal)
processes for
release lack
repeatability/speed
Lack of feedback and
quality metric leads to
missed service level
targets
Daily
Build
Monthly
Delivery
Who did
this last
time?
Dave…
Dave’s not
here
man…
Dev
Prod

DevOps: The time is now
Four key drivers are making DevOps an imperative for all organizations.
DevOpsDevOps
Business
Agility
Business
Agility
Cloud
Computing
Cloud
Computing
Operational
Discipline
Operational
Discipline
Agile
Development
Agile
Development

Why DevOps?
Time to value
–Deploy faster. Deploy Often
–Reduce cost/time to deliver
Developer ‘Self-service’
–Allow Developers to Build and Test against ‘Production-like’ systems
Increase Quality
–Reduce cost/time to test
–Increase test coverage
Increase environment utilization
–Virtualize Dev and Test Environments

Why DevOps?
Deployment
–Minimize deployment related downtime
–Minimize roll-backs of deployed Apps
Defect Resolution
–Increase the ability to reproduce and fix defects
–Minimize ‘mean-time-to-resolution’ (MTTR)
–Reduce defect cycle time
Collaboration
–Reduce challenges related to Dev and Ops collaboration
–Dev vs. Ops

Stakeholders
Development
QA
Operations
–Dev and QA Environments
–Production Environment
Security, Data, Cloud, Enterprise Architecture…

DevOps is a Philosophy
Source: http://virtualplatosacademy.blogspot.com/p/great-philosophers.html

DevOps definitions
DevOps (a portmanteau of development and operations) is a
software development method that stresses communication,
collaboration and integration between software developers and
Information Technology(IT) professionals. DevOps is a response
to the interdependence of software development and IT
operations. It aims to help an organization rapidly produce
software products and services.
-- Wikipedia

DevOps definitions
…modern applications, running in the cloud, still need to be resilient
and fault tolerant, still need monitoring, still need to adapt to huge
swings in load, etc. But those features, formerly provided by the
IT/operations infrastructures, now need to be part of the application,
particularly in “platform as a service” environments. Operations doesn’t
go away, it becomes part of the development. And rather than envision
some sort of uber developer, who understands big data, web
performance optimization, application middleware, and fault tolerance
in a massively distributed environment, we need operations specialists
on the development teams. The infrastructure doesn’t go away – it
moves into the code; and the people responsible for the infrastructure,
the system administrators and corporate IT groups, evolve so that they
can write the code that maintains the infrastructure. Rather than being
isolated, they need to cooperate and collaborate with the developers
who create the applications. This is the movement informally known as
“DevOps.
-- Mike Loukides, VP, Content Strategy for O'Reilly Media, Inc.

dev·ops noun 'dev-äps
Enterprise capability for continuous software delivery that enables clients
to seize market opportunities and reduce time to customer feedback.
A blueprint for continuous delivery of software-
driven innovation
 Accelerated software delivery
 Reduced time to obtain and
respond to customer feedback
 Improved governance across the lifecycle
 Balanced quality, cost and speed
DevOps Lifecycle
Continuous Feedback and Improvements
Operations/Produ
ction
Development/Tes
t
Customers Business
Owners
16

DevOps Principles and Values (the IBM
view)
 Develop and test against a production-like
system
 Iterative and frequent deployments using
repeatable and reliable processes
 Continuously monitor and validate operational
quality characteristics
 Amplify feedback loops
People
Process
Tools
People
Process
Tools

Key Concepts
The key technical Capabilities of DevOps
1. Continuous Integration
2. Continuous Delivery
3. Continuous Test
4. Continuous Monitoring
5. Infrastructure as Code
6. Build and Delivery Pipeline
7. Organizational Change

1. Continuous Integration
http://bit.ly/PRQ4a7

2. Continuous Delivery
http://bit.ly/PRQ4a7

3. Continuous Test
http://bit.ly/PRQ9dQ

4. Continuous Monitoring
http://bit.ly/PRQ9dQ

5. Infrastructure as Code/Software
Defined Environment
package "apache2" do
package_name node['apache']['package']
end
service "apache2" do
case node['platform_family']
when "rhel", "fedora", "suse"
service_name "httpd"
# If restarted/reloaded too quickly httpd has a habit of failing.
# This may happen with multiple recipes notifying apache to restart - like
# during the initial bootstrap.
restart_command "/sbin/service httpd restart && sleep 1"
reload_command "/sbin/service httpd reload && sleep 1"
Rational Automation
Framework
(WAS, Commerce, MQ…)
Rational Automation
Framework
(WAS, Commerce, MQ…)

Delivery Pipeline
Deploy
Environment
Running System
Source Control
Management
Source Artifacts
.jsp
.java
.html
chef
recipes
.sh
Deployable Artifacts
Build,
Package,
& Unit Test
Application
Binaries &
Platform
Configuration
Library

7. Organizational Change
‘‘Shift Left’ – Operational ConcernsShift Left’ – Operational Concerns
Build ‘Application aware’ EnvironmentsBuild ‘Application aware’ Environments
Environment SprintsEnvironment Sprints
NOT create a ‘DevOps Team’NOT create a ‘DevOps Team’
‘‘Shift Left’ – Operational ConcernsShift Left’ – Operational Concerns
Build ‘Application aware’ EnvironmentsBuild ‘Application aware’ Environments
Environment SprintsEnvironment Sprints
NOT create a ‘DevOps Team’NOT create a ‘DevOps Team’

The Flavors of DevOps
1. Water-SCRUM-fall
2. NoOps
3. ShadowOps
4. BizOps
…
1. ChatOps
2. HugOps

Cloud Hosted Environments
The Variants of Continuous Delivery
1. Deploy to Dev, QA and Prod hosted on Private
or Public Cloud
Asset
Library
Asset
Library Asset
Library
Asset
Library

2. Deploy to Dev, QA and Prod hosted on Physical
Servers (no Cloud)
Asset
Library
Asset
Library Asset
Library
Asset
Library

3. Deploy to Dev and QA hosted on Private or
Public Cloud. Prod is on-prem physical servers
(very common)
Asset
Library
Asset
Library Asset
Library
Asset
Library

Provider III
Provider III
Provider II
Provider II
Provider I
Provider I
4. Full Software Supply Chain with in-house or
outsourced providers. Each may or may not be
Cloud Hosted
Asset
Library
Asset
Library Asset
Library
Asset
Library

DevOps Adoption
 Identify the Business Value
 Build a Business Case
 Create a DevOps Culture
 People – Processes – Tools
 Identify Capabilities to Adopt/Enhance

DevOps Adoption (1 of 2)
 Requirements Management
–Requirements Management and communication across Development and
Operations
 Versioning of all DevOps assets
–Versioning of Deployment Scripts and Source Code
 Access to Production-like Environments
–Documentation of Production-like environments as Patterns
–Developers have ability to launch and destroy production-like environments
from these patterns
 Deployment Automation
–Pattern based reusable deployment scripts
–Ability to deploy applications in One-step
–Daily deployment and verification of applications to a production-like
environment
Source: 12 Steps to Better DevOps – Michael Elder

DevOps Adoption (2 of 2)
 Change Management
–Linking bugs, issues and work items to application changes
–Linking production issues to associated deployment bugs
 Automated Testing
–Automated testing is used to validate application and platform function and
characteristics
 Monitoring
–Monitoring Deployed applications to validate performance and reliability
 Delivery Pipeline
–Having a dashboard to track application stages thru the delivery pipeline and
track deployment velocity

Continuous Delivery Adoption Maturity

Continuous Delivery flow
Artifact LibraryArtifact Library
Cloud Platform ProviderCloud Platform Provider
Automation Agent
(execute delivery process)
Automation Agent
(execute delivery process)
39
Deliver
changes
Post
changes
Post results
Publish
packages
Request
cloud
resources
Provision
resources
Retrieve
packages
Developer ToolsDeveloper Tools
Source Control and Change
Management server
Source Control and Change
Management server
Test AutomationTest Automation
Execute
tests
Build ServerBuild Server
Publish
packages
Virtual System
Trigger
delivery

IBM DevOps Reference Architecture
Monitor and OptimizeRelease and DeployDevelop and Test
Mobile Cloud Social
Intelligent
Devices
Developer Communities
SecurityBig
Data
Expert
Systems
EcoSystem
ImplementationServices
Industry
DevOps Foundation
(enabled by the Jazz Platform)
Deployment Platforms (PaaS, IaaS, Physical
Infrastructure)
TOSCA
Linked DataOSLC

Monitor and OptimizeRelease and DeployDevelop and Test
Mobile Cloud Social
Intelligent
Devices
Developer Communities
SecurityBig
Data
Expert
Systems
EcoSystem
ImplementationServices
Industry
DevOps Foundation
(enabled by the Jazz Platform)
Deployment Platforms (PaaS, IaaS, Physical
Infrastructure)
TOSCA
Linked DataOSLC
UrbanCode
Expand DevOps capabilities and accelerate plans

DevOps Tool Chain
Application Release Management
Cloud Provisioning
Application Deployment Automation

Application Release Management
Cloud Provisioning
Application Deployment Automation
DevOps Tool Chain - Implementations
Rational Collaborative Lifecycle
Management Solution
Rational Team Concert
Jazz Build Engine
Rational Build Forge
uBuild
Rational Automation Framework
Rational Test Workbench
Jenkins Chef
SmartCloud Continuous Delivery
SmartCloud Provisioning
SmartCloud Orchestrator
SmartCloud Control Desk

Continuous testing with virtualized services
Avoid testing bottlenecks due to dependencies on
external services
• Automate setup and management of test
virtualization server in the cloud
• Automates configuration of virtualized
services for an application under test
• Automate setup of production-like test
environments with low cost
Databases Mainframe
applications
Third-party
Services
Rational Test Virtualization Server
App deployApp deploy
Application
changes
being tested
virtualized services
IBM SmartCloud Orchestrator
IBM PureApplication System
SITSIT FVTFVT
IBM Rational Test
Workbench
IBM Rational Test
Workbench

IBM DevOps for Mobile Applications
FeedbackFeedback
Application Deploy for Mobile
• Automates deployments of multi-tier applications
and configuration across multiple environments
• Graphical DnD editor replaces scripts
• Models environments and keeps track of what is
deployed where
• ~100 Integrations with key MW targets
Application Testing for Mobile
• Author automated tests for iOS, Android, Hybrid,
and Worklight
• Drive automated mobile app tests as part of your
continuous integration process
For mobile teams who wish to
reduce cycle times by automating
the deployment and testing of their
multi-tier mobile apps
Bring your own SCM and CI servers,
Application Deploy will:
Instrument your app for test
Deploy your app to device targets
Execute automated tests
Give you the results
Rational Test Workbench for
mobile
Continuous Delivery for Mobile
1574A Mobile DevOps – Challenges and
Best Practices (with Leigh Williamson, IBM
Distinguished Engineer)
Dolphin – Asia 3 Wed, 5/Jun, 03:00 PM –
04:00 PM

COBOL, PL/I, C++, Java, EGL, Batch,
Assembler, Debug Tool
x86 PC running Linux
IMS
z/OS
WAS
DB2
MQ
CICS
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.
DevOps Lifecycle
Continuous Feedback and Improvements
Operations/ProductionDevelopment/TestCustomers Business Owners
IBM Continuous Integration
Solutions
for System Z
IBM Continuous Integration
Solutions
for System Z
IBM Rational Test
Workbench
IBM Rational Test
Workbench
Rational Development and Test Environment
for System z
48
IBM Application Deploy
1144A Continuous Integration for System z (with
Rosalind Radcliffe, IBM Distinguished Engineer)
Dolphin – Asia 2 – Tue, 4/Jun, 01:45 PM – 02:45 PM

Featured DevOps Events at Innovate 2013
Time Session Location Speakers
Mon, June 3
1:45-2:45 PM
DOPS-1033: DevOps Review and Roadmap Asia 2 Daniel Berg
Mon, June 3,
4:15-5:15 PM
DOPS-1600: Field Experiences with IBM
DevOps solutions
Asia 2
Paul Bahrs/Customer
Panel
Tue, June 4
12:15- 01:15PM
BOF-2604A: How do you accelerate delivery
with DevOps?
Southern II Birds of a Feather
Tue, June 4,
3:00-4:00PM
DOPS-2617: The DevOps Imperative: Why the
Enterprise Needs to Continuously Release and
Deploy Software
Australia 2
Maciej Zawadzki,
Albert Ho
Wed, June 5,
10:00-11:00AM
BDPLY-2637 : WebMD Adopts Automated
Deployment in support of Continuous
Integration to transform their SDLC
Asia 2
Teresa Dietrich, Derek
Chang, WebMD
Wed, June 5,
11:15AM–12:15PM
BDPLY-2618: Streamlining Delivery with
Automated Deployment
Australia 2 Eric Minick
Thu, June 6,
9:00-10:00AM
BDBLY- 1239: Automation is not enough Asia 1 Rick Moran, Fidelity
Download the new IBM DevOps Whitepaper from eLit
• Visit the UrbanCode Booth
• 19 DevOps-related Pedestals in the DevOps Zone
• Collect the DevOps Buttons!
• Visit the Consulting Café to know more about DevOps workshop
Solution Center

Where to get more information?
 IBM Enterprise DevOps blog
–http://ibm.co/JrPVGR
 6 Ways for Enterprises to Adopt DevOps blog
–http://ibm.co/xq71xY
 Understanding and Adopting DevOps (Series on my Blog)
–http://bit.ly/MyDevOps

52
Daily Apple TV giveaway
 Complete your session surveys online each day at a conference kiosk or on
your Innovate 2013 Portal!
 Each day that you complete all of that day’s session surveys, your name will
be entered to win the daily Apple TV!
 On Wednesday be sure to complete your full conference evaluation to receive
your free conference t-shirt!

53
Acknowledgements and disclaimers
© 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.

54
© 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.

IBM Innovate 2013 Session: DevOps 101

Recommended

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to IBM Innovate 2013 Session: DevOps 101 (20)

More from Sanjeev Sharma (19)

Recently uploaded (20)

IBM Innovate 2013 Session: DevOps 101

Editor's Notes