Mobile to mainframe - The Challenges and Best Practices of Enterprise DevOps

© 2013 IBM Corporation

Mobile to MainframeThe Challenges and Best Practices of Enterprise DevOps

Sanjeev SharmaIBM Worldwide Lead – DevOps Technical Sales

Executive IT Specialist, IBM Software Group

[email protected]

@sd_architect


mailto:[email protected]

https://twitter.com/sd_architect


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,WebSphere, Rational, and IBM Mobile Enterrise 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

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.

http://www.ibm.com/legal/copytrade.shtml


Agenda

• A Level set on DevOps• IBM’s view of DevOps• DevOps and the Enterprise• DevOps for Mobile Apps• DevOps for the Mainframe• Adopting DevOps in The Enterprise

o Peopleo Processo Technology


Agenda




Market trends and expected client business outcomesDependent on rapid Software Innovation and Delivery

5

Continuousclient experience

Partner valuechain

Cloud-basedServices

Systems of Engagement Systems of Record

SAP HR

DB ERP

Systems of Interaction

Leverage cloud to enable flexibility and offer new services

Integrate, evolve and maintain stability of services and comply with any regulations

Rapidly deliver differentiating digital content, applications and services to grow revenues & obtain new customers

Provide differentiating client experience to meet the needs of empowered users

Enable a software supply chainInternet of Things

Deliver software based innovation to enable machine to machine interactions


Organizations that effectively leverage software innovation outperform their competitors... yet few are able to deliver it effectively

6

86%

of companies believe software delivery is important or critical

25%

leverage software delivery effectively today

But only…

Source: “The Software Edge: How effective software development drives competitive advantage,” IBM Institute of Business Value, March 2013

69%

outperformthose who don’t

of those wholeverage software

delivery today


Achieving the business outcomes are exposing gaps in the software innovation and delivery processes

Systems of Interaction

Continuousclient experience

Partner valuechain

Cloud-basedServices

Systems of Engagement Systems of Record

CRM HR

DB ERP

of applicationsrolled back

>80%

of partnered projects fail to meet objectives

>50%

of resources devoted to maintaining existing systems and products

>70%

to deliver application changes to customers

4-6 Weeks

Line-of-businessTakes too long to introduce or make changes to digital apps and services

OperationsRapid app releases impacts system stability and compliance

Development/TestSpeed mismatch between faster moving front office and slower moving back office systems, delaying time to get feedback

SuppliersDelivery in the contextof rapid changes


And a lack of continuous delivery impacts the entire business

8

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

BusinessOwners

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


Agenda




William Deming – American statistician

Major influencer of Japanese manufacturing and business

Famous for Plan-Do-Check-Act cycle (Deming Cycle)

– I like “Adjust” versus “Act”

PDCA cycles found in DevOps

10

William Edwards Deming

Plan Do

CheckAdjust

Deming Cycle

Qualit

y

Plan Do

CheckAdjust

Plan Do

CheckAdjust


Accelerate Software Delivery

Balance speed, cost, quality and risk

Reduce time to customer feedback

DevOps

Enterprise capability for continuous software delivery that enables clients to seize market opportunities and reduce time to customer feedback

1111

Continuous Innovation, Feedback and Improvements

DevOps Lifecycle

Operations/Production

Development/TestCustomers

BusinessOwners


DevOps approach: Apply Lean principles to software innovation and delivery to create a continuous feedback loop with customers

Line-of-business

Customer

1

3

2

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

Adopt DevOps approach to continuously manage changes, obtain feedback and , deliver changes to users

Eliminate any activity that is not necessary for learning what customers want


Agenda



© 2013 IBM Corporation14

Adoption paths to a DevOps approach

DevOps Foundation

Open Lifecycle and Service Management Integration Platform

DevOps LifecycleOperations/ProductionDevelopment/TestCustomers Business Owners

Continuous Innovation, Feedback and Improvements

Ec

os

ys

tem

Be

st P

rac

tice

s

Monitor and Optimize

Plan and Measure Develop and Test Release and Deploy

OSLC


Heterogeneous Environments

Public CloudPrivate Cloud

Data Warehouse MainframeEnterprise Service Bus

Directory Identity

File systems

Collaboration

Mobile App

Routing Service

Third-partyServices

Portals

ContentProviders EJB

SharedServicesArchives

Business Partners

Messaging Services

DevOps in the Enterprise


Multi-technology, multi-vendor

Silo-ed development and deployment

Dev – Ops segregation

Distributed Teams

Supply Chain model

Partners and Suppliers

Water-SCRUM-fall model


Agenda




DevOps for Mobile - Challenges

Mobile Apps are the front-end to a complex(enterprise) back-end system

– Mobile Apps are rapidly becoming a critical user interface to enterprise systems

– But they are just one part of a multi-tier, multi-component application “eco-system”

– Developing and delivering mobile apps requires coordination across that whole eco-system



Data Warehouse MainframeEnterprise Service Bus

Directory Identity

File systems

Collaboration

Mobile App

Routing Service

Third-partyServices Portals



Business Partners

Messaging Services


DevOps for Mobile - Challenges

Fragmented Platforms

– Multiple mobile operating systems

– Multiple devices & form factors

– Multiple implementation technology choices

Frequently a mix of technology is involved for mobile app implementation

API and Provisioning Keys need to be governed

App stores add additional asynchronous deployment step


Mobile Application Architecture: LinkedIn

http://engineering.linkedin.com/testing/continuous-integration-mobile

http://engineering.linkedin.com/testing/continuous-integration-mobile


Multi-tier mobile apps present specific challenges to DevOps

Middle Tier ServerClient Tier Devices Back-end Data & Services

Mobile-specific challenges: Lots of device targets Provisioning rules

and artifacts Curated App Stores Dependent upon

backend service versions

The Mobile-specific challenge in DevOps is mainly:1. Dealing with the specific issues in the Mobile Client tier2. And subsequently coordinating separate pipelines for

each tier: Mobile Client Middleware Back-end data and services


DevOps for MobileAccelerate Delivery focusing on quality and user experience

One-star ratings kill companies. A fickle user base with many competing options makes reacting to feedback essential. Continuous Feedback and Optimization using Tealeaf helps monitor user sentiment and usage, letting teams react to poor feedback before it spirals

Build Deploy Functional Test

Acceptance Test App Store


Agenda




Mainframe Delivery Pains…

Multiple teams working across restricted dev and test capacity lead to conflict, delays, or bad test results in shared environments

Complex and manual management and configuration tasks result in errors and delays

Too much bad code going into test and production causes crit sits and emergency fixes

Bottlenecks due to inefficient communications between disparate platforms and teams (Dev/Test - System Programmers; mobile – distributed-mainframe)


Go on Offense

Play Defense

…solutions from IBM

Provide cheap, isolated, development and test environments for project teams

– Rational Development and Test Environment

– Rational Test Virtualization Server– SmartCloud Provisioning – Cloud Ready for Linux on System z

Automate consistent build, configure, and deploy processes across all stages

– Rational Team Concert– uDeploy– SmartCloud Orchestrator

Enforce base quality standards automatically prior to promotion

– Rational Test Workbench– Rational Quality Manager– SmartCloud Application Monitoring– Omegamon

Improve communication and collaboration with cross-platform release planning

– IBM Collaborative Lifecycle Management

– Smart Cloud Control Desk

© 2013 IBM Corporation25 25

Test LPAR

z/OS

…

Typical z/OS Testing ArchitectureOrganized by project team, vertically scaled, sharing resources, limited automation

ProjectTeam[April Maintain]

ProjectTeam[Prototype SOA]

ProjectTeam[June New Func]

ProjectTeam[Dec Sys Upgrade]

TestData

App

App

App

Problems Encountered

1. Shared resources combined with overlapping schedules can elicit conflicts, impede innovation and slow code delivery

2. Coordination of environmental changes and releases cause bottlenecks, delays and additional overhead

3. Shared test data is difficult to manage and can lead to over testing or incorrect test results


Agenda

• An Level set on DevOps• IBM’s view of DevOps• DevOps and the Enterprise• DevOps for Mobile Apps• DevOps for the Mainframe• Adopting DevOps in The Enterprise



Plan / Measure Development / Test Release / Deploy Monitor / Optimize

Scaled

Reliable

Repeatable

Practiced

DevOps maturity model

Define release with business objectives

Measure to customer value

Plan and source strategically

Dashboard portfolio measures

Plan and source strategically

Dashboard portfolio measures

Link objectives to releasesMeasure to project metrics

Link objectives to releasesMeasure to project metrics

Automate problem isolation and issue resolution

Optimize continuously

Improve continuously with development intelligence

Test Continuously

Manage environments through automation

Provide self-service build, provision and deploy

Monitor using business and end user context

Centralize event notification and incident resolution

Monitor using business and end user context

Centralize event notification and incident resolution

Deliver and build with testCentralize test management

Link lifecycle information

Deliver and build with testCentralize test management

Link lifecycle information

Plan departmental releases and automate status

Automated deployment with standard topologies

Plan departmental releases and automate status

Automated deployment with standard topologies

Optimize applications Use enterprise issue resolution procedures

Optimize applications Use enterprise issue resolution procedures

Deliver and integrate continuously

Manage data and virtualize services for test

Deliver and integrate continuously

Manage data and virtualize services for test

Standardize and automate cross-enterprise

Automate patterns-based provision and deploy

Standardize and automate cross-enterprise

Automate patterns-based provision and deploy

Document objectives locallyManage department

resources

Document objectives locallyManage department

resources

Monitor resources consistently

Collaborate Dev/Ops informally

Monitor resources consistently

Collaborate Dev/Ops informally

Manage Lifecycle artifactsSchedule SCM integrations

and automated builds Test following construction

Manage Lifecycle artifactsSchedule SCM integrations

and automated builds Test following construction

Plan and manage releases Standardize deployments

Plan and manage releases Standardize deployments

Industry norm


Lifecycle Integration for DevOps

ManagementAccountability

Integration

CultureCollaboration

Communication

AutomationIntegration

VisibilityOperational

Models, Assets, Data

and Stores

Development Models, Assets, Data and Stores

Dev Tools

OpsTools

Process

People

Technology


Agenda




• Common Business Objectives • Vision Statement

• Common measures of Success

Product Owner

Team Member

Team Lead

Team Member

Team Member

Senior Executives

UsersDomain Experts

Auditors

Gold Owner

Support Staff

External System Team

OperationsStaff

Adopting DevOps in the Enterprise: People/Culture


• The case for and against ‘DevOps Team’• The DevOps Liaison Team

• No overlay layer of bureaucracy



• Building a DevOps Culture• There is no Silver Bullet

• Right People are needed

Product Owner

Team Member

Team Lead

Team Member

Team Member

Senior Executives

UsersDomain Experts

Auditors

Gold Owner

Support Staff

External System Team

OperationsStaff



• Organizational Change

‘Shift Left’ – Operational ConcernsBuild ‘Application aware’ Environments

Environment Sprints



Agenda




• DevOps as a Business Process• A Process to get Capabilities from Ideation to Value

• Apply Lean Thinking to Processes

Adopting DevOps in the Enterprise: Process


Key Capabilities

1. Collaborative Development & Continuous

Integration

2. Continuous Business Planning

3. Continuous Release and Deploy

4. Continuous Testing

5. Continuous Feedback



1. Collaborative Development and Continuous Integration

http://bit.ly/PRQ4a7

Mobile App Developent Teams

Enterprise Services Developent Teams



2. Continuous Business Planning

3. Continuous Release and Deploy

4. Continuous Testing

5. Continuous Feedbackhttp://bit.ly/PRQ4a7



Agenda




• Infrastructure as Code/Software Defined Environments

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"

/* REXX *//* REXX BIND processor sample */ trace o Arg PACKAGE DBRM rcode = 0

/* Set BIND options */ SYSTEM = 'DSN9'

i = Pos('(', DBRM) len = Length(DBRM) LIBRARY = Substr(DBRM, 1, i - 1) MEMBER = Substr(DBRM, i + 1, len - i - 1)

OWNER = 'DEVDBA' ACTION = 'REPLACE' VALIDATE = 'RUN' ISOLATION = 'CS' EXPLAIN = 'NO' QUALIFIER = 'DEVDBA'

Call Bind_it

Exit rcode

Bind_it:

/* Create a bind control statement as a single long line. Then *//* queue that into a FIFO stack */ DB2_Line = "BIND PACKAGE("PACKAGE")" ||, " LIBRARY('"LIBRARY"')" ||, " MEMBER("MEMBER")" ||, " OWNER("OWNER")" ||, " ACTION("ACTION")" ||, " VALIDATE("VALIDATE")" ||, " ISOLATION("ISOLATION")" ||, " EXPLAIN("EXPLAIN")" ||, " QUALIFIER("QUALIFIER")"

/* Write the bind control statement to the data queue and execute */ /* DB2I to perform the bind. */

queue DB2_Line queue "End" Address TSO "DSN SYSTEM("SYSTEM")" rcode = RC

Return

Rational Automation Framework

(WAS, Commerce, MQ…)

Adopting DevOps in the Enterprise: Technology


Adopting DevOps in the Enterprise: Technology

41

• Common Collaboration Tools• Common Work Item Management Tool

• Dashboards to show status/progress


IBM acquires UrbanCodeExpand DevOps capabilities and accelerate plans

Release and Deploy


IBM announces the acquisition of UrbanCode Inc.

Enhancing Continuous Release and Deployment:

Drive down cost by automating manual tasks, eliminating wait-time and rework

Speed time to market by increasing the frequency of software delivery

Reduce risk through increased compliance of application deployments.

43

Deployment

Complements our DevOps solution:

Deliver a differentiated and engaging customer experience by reducing time to customer feedback

Quicker time-to-value of software-based innovation with improved predictability and success

Increased capacity to innovate by reducing waste and rework in order to shift resources to high-value activities

Complementing our DevOps solution, combining IBM and UrbanCode, will enable clients to more rapidly deliver mobile, cloud, big data analytics and traditional applications.


Line of Business

IBM UrbanCode Build

Example DevOps Tool ChainIncrementally adopt when/if needed

Rational Team Concert Rational Quality ManagerRational Test WorkbenchRational Test Virtualization Server

SmartCloud Application Performance Management

Rational Focal PointRational Requirements Composer

SmartCloud OrchestratorIBM Pure Application System

44

IBM UrbanCode Deploy

IBM UrbanCode Release


DevOps for MobileAccelerate Delivery focusing on quality and user experience

Build Deploy Functional Test

Acceptance Test App Store

RTW MobileIBM UrbanCode Deploy IBM UrbanCode Release


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 Rational Test Workbench

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

46

IBM Application Deploy


Continuous testing with virtualized servicesAvoid 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 Mainframeapplications

Third-partyServices

Rational Test Virtualization Server

App deploy

Application changes being tested

virtualized services

IBM SmartCloud Orchestrator

IBM PureApplication System

SIT FVT

IBM Rational Test Workbench


What is Service Simulation and Test Virtualization?

Test Virtualization enables to create “virtual services”:

–Virtual Services simulate the behavior of an entire application or system during testing

–Virtual Services can run on commodity hardware, private cloud, public cloud

–Each developer, tester can easily have their own test environment

–Developer and testers continue to use their testing tools (Manual, Web performance, UI test automation)

48

Ca

ptu

re & M

od

el

Ca

ptu

re & M

od

el

System dependencies are a key challenge in setting up test environments:Unavailable/inaccessible: Testing is constrained due to production schedules, security restrictions, contention between teams, or because they are still under development Costly 3rd party access fees: Developing or testing against Cloud-based or other shared services can result in costly usage feesImpractical hardware-based virtualization: Systems are either too difficult (mainframes) or remote (third-party services) to replicate via traditional hardware-based virtualization approaches



Data Warehouse MainframeEnterprise

Service Bus

Directory Identity

File systems

Collaboration

App Under TestRouting Service

Third-partyServices Portals



Business Partners

Messaging Services

Databases Mainframeapplications

App Under Test

Third-partyServices

Packaged apps, messaging services, etc.

Virtual Services


Cloud Deployment using UrbanCode Deploy

Compute | Storage

OS

Packaged Software

Application

Middleware

Compute | Storage

OS

Packaged Software

Middleware

Network

Cloud

Provisioning (SmartCloud Orchestrator, Pure Systems)

Cloud Management



Continuous Delivery with Cloud

IBM UrbanCode DeploySmartCloud Orchestrator

IBM Pure SystemBuild Artifact Library

ApplicationResource Template

Build Deploy Provision

Application binaries (versioned)

Environment configurations (versioned)

• Automate provisioning of environments as part of the end-to-end delivery process – Establish and automate deployment of Application Blueprint with resource templates imported from Cloud patterns.

• Deploy early and often to ensure high quality and faster releases using repeatable, reliable, and managed automation - Seamless process flow for incremental, full stack provisioning and application deployment automation

IBM UrbanCode Deploy v6.0



Blueprint

ApplicationResource Template

Continuous Delivery to Cloud

Capture cloud pattern to be used for

creating an Environment

Incremental deployment of

application builds to cloud

environments

Map the application to multiple

cloud patterns

The freedom to provision a version of a full stack or incrementally deploy an application version into an already provisioned environment

Environments | Processes | Configurations

Import pattern

DEV

QA PRODDEV

DEV

SmartCloud Orchestrator

IBM Pure Application System

Create env from pattern

Deploy app


LegacySystems

SW-Defined Environments

Mobile Transformation

Market Experimentation

Agile Transformation

Quality Improvement

AgileInitiative

Case Study: Fidelity International

Business Challenge• Unpredictable Release schedules• Need to adopt Agile development practices• Compliance and Audit requirements

Pain Points• Speed of delivery – release process took 2-3 days• Manual test and environment setup resulted in

down time• Manual processes introduced errors

Benefits• Cost Avoidance of over £1.5M ($2.3M) a year Assured regulatory compliance

• Test team “down-time” virtually eliminated • Release processes take 1-2 hours versus 2-3 days

• Developers gain autonomy and self-service for deploying applications

Release /Deploy

Develop /Test

Plan /Measure

Monitor /Optimize

Jazz, OSLC and Open Standards Platform

Collaboration Change & ConfigurationManagement

Dashboard / Analytics

Requirements

Code

Test

Deployment

ProvisioningCustomer Feedback

Monitoring

Continuous Delivery

Portfolio Management

http://www.urbancode.com/html/resources/articles/Fidelity_Success_Story.pdf

http://www.urbancode.com/html/resources/articles/Fidelity_Success_Story.pdf


www.ibm.com/software/rational

http://www.ibm.com/software/rational


© Copyright IBM Corporation 2012. 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.

www.ibm.com/software/rational

http://www.ibm.com/software/rational

55

Mobile to mainframe - The Challenges and Best Practices of Enterprise DevOps

Technology

wikirational20presentation20templates

mobileaccelerate

mainframeenterprise

bind control

directory

full stack

seize market

mobile approuting