Develop better, Deliver Faster with

DevOps:
The CA LISA Product Suite
John Boebinger
Senior Principal
Consultant
 Today’s reality

2 Copyright © 2013 CA. All rights reserved.

 Does Any of This Sound Familiar?
Speed, Quality and Cost Problems Across Software Lifecycles

I spend 70% of Performance is What is IT doing?

my time waiting lousy in Saskatoon I need new apps
now!!

Our test systems

are not realistic
Mobile User
DEVELOPERS
I’m constantly
TESTERS fighting fires
I don’t have spare
capacity Dept User

INFRASTRUCTURE APPS
OWNERS SUPPORT
Fundamental Conflict Between Dev and Ops
Connecting Dev and Ops Objectives
 But What Does DevOps Actually Mean?

methods for improving

communication ,

integration , and
collaboration between
development and
operations
 CA’s perspective on reducing gaps in DevOps

RELEASE AUTOMATION

COLLABORATIVE OPERATIONS
PORTFOLIO PLANNING MONITORING
Deploy

Build SERVICE
VIRTUALIZATION Release

AGILE DEVELOP DATA MINING

& TEST ENVIRONMENT
MANAGEMENT
API DEVELOP

Continuous Feedback

AGILE DEVELOP
& TEST ENVIRONMENT
MANAGEMENT

PLAN BUILD TEST RUN

DevOps brings the application portfolio forward to meet market challenges

with collaboration and efficiency from design to deployment
Where CA fits

Portfolio System Integration Performance

Requirements Design Dev UAT Deploy Monitor
Management Test Test Test

Application Lifecycle

Planning & LISA Production

Service Virtualization
Governance & Support
Network Release Pathfinder LISA
(Clarity) Virtualization Automation Datafinder Test
(APM, eHealth)
Platforms for agile composite app dev

Requirements Management IDE

Static Code Analysis
Test Management Source Code Management
Code Security
Defect Management Build

Application Lifecycle
Management
 DevOps deeper dive

1 Service Virtualization – Remove constraints to testing

Release Automation – Bringing consistent and repeatable processes

2
to automating the release of applications

Network Virtualization – Testing applications in the same network

3
environment the users will see

Plan, build, test, run, enterprise-grade innovation … at

startup speed
Service Virtualization
The Good Old Days

3270

Mainframe
Modern Application Development Architecture

UI LAYER

GATEWAY

COMPOSITE
APPLICATIONS

ESB
INTEGRATION

MQ JDBC HTTP SOAP

>C
BACK-END
Mainframe Data Legacy External
Challenge: Constraints

“I can’t do anything until I have everything . . . and I never have everything!”

Firewall changes
needed (which Well, it’s designed,
takes 30 days) but not yet built

Data comes from a ESB A couple of pieces

different department INTEGRATION
may be there…

MQ JDBC HTTP SOAP

You can touch the M/F
>C
3rd Party, you get
for two hours Sunday
at 3:00 AM
charged, not always
Mainframe Data Legacy External available
It gets complicated…

Need an environment to
support the current version

>
C

Need an environment to
support the version shipping
this month
>
C

Need an environment to
support the version shipping
later this quarter

>
C
Band aid solution: Stubs

• Had to have something

• So we wrote stubs
• But stubs are wasted coding
• Difficult to write well
• Expensive to maintain
• Limited functionality
• Not particularly good
for performance testing
• Developers don’t write their
own compilers
Here a stub
• Why should they be writing
and maintaining stubs?

ESB
There a stub
INTEGRATION

MQ JDBC HTTP SOAP

>C Everywhere a stub
Mainframe Data Legacy External
stub
Solution: LISA Virtual Services
Virtual Test Environments (VSE) simulate the behavior, data, and
performance characteristics of unavailable or incomplete systems

Virtualize
No more
nearly any
stubs and
IT Asset
mocks

VSE
Eliminate
behaves
conflicts
like the real
over test
thing
data

ESB

No 3rd party
Available MQ JDBC HTTP SOAP transaction
24/7 >C or service
fees
Mainframe Data
Data Legacy External
What can I virtualize?
LISA Service Virtualization: How does it work?

CAPTURE PROCESS MODEL

 Structured Conversations  Heuristics  Sophisticated Behavior

 Observe  Analytics  Dynamic Properties (Dates,
 Understand  Algorithms values, etc.)

 Protocol-Level  State  Scenario Support

 Recorded traffic  Test Data Sanitation
 Design specs  Compiled Model vs. Stubs
 Sample RR pairs  Automatic Healing
 Transaction logs
 Manual Creation
 Byte-Code
Recording a LISA Virtual Service (Capture)

Existing Environment

Load Generators

Exercise the SUT

LISA VSE
Request

Request
Response

Response
Request ESB
Response

MQ JDBC HTTP SOAP

>C

Mainframe Data Legacy External

 Delivery Schedules
2
Actual Project
Planned ProjectSchedule
Schedule
Weeks

Development Loss of 2 to 4 weeks behind

schedule based on historical data
Unit Test Integrated System Test System Test
Integrated
Average of 54% of new functionality
3rd Party System Test testing done instead of 75% planned

Backend Data Code

System Integration
SystemTest
Integration Test
Refresh Refresh

Functional Test 1stst Pass: Functional Test 2nd Pass:

System Test
75%
54% 100%

Regression Test: Regression Test:

75% 100%

Load and Performance

Load and Performance Test
Environment Prep

User Acceptance Testing

Production
 Delivery Schedules
2
LISA Value Release
Weeks

Development 44%
Savings
Unit Test Integrated System Test

3rd Party System Test

388%
more defects found
Backend Data Code
System Integration Test
Refresh Refresh

Functional
Functional
Test Test
1st Pass:
1st Pass: Functional Test 2nd Pass:
System Test
System Test
75%75% 100%

60% Savings Regression

Regression
Test:Test: Regression Test:
75%75% 100%

Load and Performance

Load and Performance Test
Environment Prep
35% Time Savings
40% More Coverage User Acceptance Testing

Production
Compressed Testing
Schedule by 3 Weeks
Our Customers
Release Automation
 What does it take to make an application?

 You need the customer application itself

– Java, HTML files, database, etc. Application

 You need the base software

Application
– WebSphere, Web Server, Database Base Software

 You need an operating system

Operating
– (Windows, Linux, AIX, etc.) System

You need a server

Server
 (This stuff has to run somewhere)

24 Provided Under NDA. Copyright © 2013 CA. All rights reserved.

 How does CA Technologies make all this happen?

 CA LISA Release Automation can deliver the

components of the application
Application

 CA Server Automation installs the base

application software (WebSphere, etc.) Application
Base Software

 CA Server Automation provisions the

Operating
Operating System
System

 Server can be physical, virtual, or cloud

Server

25 Provided Under NDA. Copyright © 2013 CA. All rights reserved.

 How often are changes needed?

 Application components may get updated

weekly (or even more often)
Application

 Application Base Software updated about

every two to four years (Patches needed) Application This is where you
Base Software need Release
 Operating systems installed on new servers Automation
Operating
– Patches do need to be maintained System

 Servers typically replaced every three to

six years Server

26 Provided Under NDA. Copyright © 2013 CA. All rights reserved.

 What makes up a typical application?

HTML
Used to display information
Goes on a Web Server
Java or .NET
Used for the application rules
Goes on an Application Server
Database
Goes on the Database Server

27 Provided Under NDA. Copyright © 2013 CA. All rights reserved.

 How are these issues being handled today?

Could be done manually

with mass effort
Could be done with ugly,
barely maintainable scripts
The point is that a purpose
built, automated tool can
do this better, faster, and at
less cost

28 October 11, 2013 Copyright © 2013 CA. All rights reserved.

 application delivery maturity model

Optimization
Ongoing
Improvement Continuous

End to End
Key Achievements

Delivery
Automation
Standardization

Scripting
Process Manual

Heroes

Level 1 Level 2 Level 3 Level 4 Level 5

Delivery Levels

29 October 11, 2013 Copyright © 2013 CA. All rights reserved.

 level 3 – application release automation

Zero Touch Release Deployment

Deployment Manifest

30 October 11, 2013 Copyright © 2013 CA. All rights reserved.

 level 4 – continuous application delivery

Continuous
Integration
Artifact
Repository
Build Automation

Change Mgmt.

Continuous
Test Application Delivery Config Mgmt.

Automation
CA LISA®
Release Automation Infra Prov

DEV TEST UAT PROD

31 October 11, 2013 Copyright © 2013 CA. All rights reserved.

 Bringing It All Together
Source Control
Artifact Service Desk
repository

Dev Mgr

Application Delivery
Test Automation
CA LISA®
Release Automation

Test Prod

Service
Virtualization
 our customers’ experience

Company Application Release Before/After Business Value

Streamlined International
Multinational Online Grocery and Wine 2.5 Days  20 Minutes Updates of online grocery
Grocer Apps £250K / a month

Financial £ 8.6M annually implement

Institution Fix Income IB division 12 Days  1.5 Minutes
globally

Oil drilling platform 3 Days  4 Minutes

Oil and Gas £380K / a month
application

Financial Rating Business information 90minutes  3minutes $1.3M annually

Online Gambling On Line Gambling 2 Days  3 Minutes $2.3M annually implement

globally

Global Retailer Online store 2 Days 12 Minutes $1.2M annually

33 October 11, 2013 Copyright © 2013 CA. All rights reserved.

Service Virtualization
For Networks
 CA SVN completes the end to end

CA SVN creates the production network conditions between:

Users, Application Infrastructure, and Services;
all prior to production.

Load Generation

Emulated
Networks
Emulated
Networks

App Services
Firewall Composite
Application
Distributed
Application Under Test Services

Functional Testing

35 October 11, 2013 Copyright © 2013 CA. All rights reserved.

 LISA SVN: Component Level Specification

DISCOVER EMULATE OPTIMIZE

Capture of production Testing of applications Analysis & optimization

network conditions like with virtualized of performance before
bandwidth, latency, production network deployment, before poor
performance affects
jitter and packet loss conditions
users

CA LISA SVN
 application complexity increases failure

The average application connects to 38 discreet services

3rd Party
Private or Public
Cloud Services Cloud Services
Customers

Load Web App DB

Mainframe
Major ISP Balancers Servers Servers Servers

Employees

Storage
Mobile Carriers Content
Browsers Web
& ISPs Delivery
& Services Mobile
Networks Components
Devices

37
 Analyze and Optimize

3G Mobile Poor LISA VSE without

Network Emulation
Mobile User experiences more delays, why?
 CA LISA SV4N Overview

Network virtualization for software

testing
• Capture production network
conditions
• Test applications on a virtualized
network in the test environment
• Analyze and optimize application
performance
Average customer ROI < 3 months
Average customer eliminates 25% of
in-production performance incidents
per year

Ensure performance before deployment and before poor performance affects your
customers.
CA LISA and DevOps

 Service Virtualization removes constraints

and shifts the development cycle to the left
 Release Automation reduces errors and
increases the speed of deployment
 Network Virtualization creates a real world
network performance environment
 Applications delivered faster with higher
quality and at lower cost

Copyright © 2013 CA. All rights reserved.