Removing Crucial Dependencies to Enable KPN as a Virtual Telecom Provider

Removing Crucial Dependencies to Enable KPN as a Virtual Telecom Provider

Robin Bleeker

DevOps: API Management and Application Development

KPN

Process Chains Manager Innovation Tooling

DO3X120S

@RobinBleeker

#CAWorld

2 © 2015 CA. ALL RIGHTS RESERVED.@ROBINBLEEKER #CAWORLD

© 2015 CA. All rights reserved. All trademarks referenced herein belong to their respective companies.

The content provided in this CA World 2015 presentation is intended for informational purposes only and does not form any type

of warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA.

For Informational Purposes Only

Terms of this Presentation


Abstract

In this presentation KPN, a Dutch telecom provider, will show why they started with CA Service Virtualization solutions and what they achieved with it.

Briefly KPN will explain what CA Service Virtualization is and what it is not.

Robin Bleeker

KPN

Process Chain Manager


Agenda

WHAT IS KPN

STUBS AND DRIVERS

FUTURE

WHY CA DEVTEST ?

EXAMPLES

CURRENT INSTALL AND RESULTS

1

2

3

4

5

6


What is KPN?

KPN is the leading telecommunications and ICT service provider in The Netherlands, offering wireline and wireless telephony, internet and TV to consumers, and end-to-end telecommunications and ICT services to business customers

27,000 employees, 18,000 in the Netherlands


What is CA Service Virtualization: Stubs & Drivers

DriverApplication or

sub chain

Stub / Virtual Service



CA Service Virtualization

Manual Test on the GUI or

with SoapUI or

automated with HP or CA App Test


Why did we start with CA Service Virtualization in 2010?

To reduce the number and costs of test environments

– Why:

Test environments are badly available

Test environments are expensive– Test environments require (expensive) licenses– Test environments need (expensive) hardware– Test environments must be maintained

Every project wants it’s own test chain, with it’s own environment for every app, because other projects are changing applications that “we” need to be prod-like.


What did it Bring Us?

No reduction of the test environments!

Still it was successful!

Why:

– We did save on creation of new test environments

– Higher availability of the used test-chain(s)!

– This caused: Less overtime to make the deadline More time to test Higher test coverage Better quality Less production incidents !!!!


Example

Doc Management

Ord

er in

take

orc

he

stra

tion

Commercial order Orchestration

CRM

ServiceActivation

BRM

ECM

Application IntegrationTrouble Ticketing

Workforce Mgt

Logistics (EBS)

BI

Assets

Product

Presentment

Kiwi (Zip code Check)

Account

EAI

Call

center

ECM

Collections

My KPN

Engineer


Results for This Fiber Environment Only

Results of CA Service Virtualization at Fiber:– Project duration shortened by 5%

– Functional availability increased from 40% to 95%

– Less production incidents caused by interface defects

– Interface message checks reduced by 25% because of easy HTML interface

– Uniform maintenance of virtual applications (stubs)

– Easier problem solving, all stubs created in the same way

– Switching between test environments changed from hours to minutes

– Increased test coverage (pa negative test possibilities)


Development and Maintenance of Virtual Services

Development and maintenance is centralized:– To encourage re-use

– No roles to separate virtual services

– Always someone available to maintain the virtual service

– Always someone available who knows how the virtual service works

– End users don’t need SV knowledge


Centralized Maintenance Downside

Always an extra party needed to make changes

No option to quickly make a small change

Because end users don’t use it themselves, they don’t see options to

improve or to use it more

Usage is not spreading like we hoped because of third party interference

We don’t get all benefit from SV. We can do better

Usage mainly in UAT E2E tests, we want also usage in SIT or ST


Agile project

Current Situation

Dev

Team

Team

A

Team

B

Team

B

Team

A

Team

C

SV maintenance and

development teamTest

Team

Waterfall project Agile Project 2

SV Production

(=linux bare

metal)

SV

Acceptance

(=windows

vm)


New Licensing Model

Unlimited number of Service Virtualization instances

No max transactions per day

Concurrent Power users available so end users can easlily switch services on or off

Runtime users


SV Production (=linux bare metal)

Agile project

New Situation

Dev

Team

Team

A

Team

B

Team

B

Team

A

Team

C

SV maintenance and development team

Test

Team

Waterfall project Agile project 2

SV

Acceptance

(=windows

vm)

SV 1SV 2

SV 3

SV 4

SV 5

SV 6SV 7SV 8

SV 9


Benefits New Situation

Every project/msp it’s own env

Simple usage by project itself (like small changes etc.)

Still central maintenance to monitor and reuse of virtual applications

Better understanding of SV by end users and by that more usage also

during development

More usage during system test/ system integration test, which should

result in shorter turnaround time


Agile Test Environment (Standard Situation)

Team

B

Team

A

Team

C

Agile Project

Team

D

Team

F

Team

E

Team

G

App 1 App 2 App 3

App4

Project scope


Agile Test Environment (Desired Situation)

Team

B

Team

A

Team

C

Agile Project

Team

D

Team

F

Team

E

Team

G


Project scope

Agile Test Environment (Best Situation)

Team

B

Team

A

Team

C

Agile Project

SV 1 SV 2

SV 3

Team

D

Team

F

Team

E

Team

G

App 1 App 2 App 3

Data Range AData Range B

Data Range CData Range D

Data Range EData Range F

Data Range G


Best Solution

Separate the teams by test data ranges per team

Separate test data, so the teams can use the same test chain

Use pass-through for some ranges and virtualized for others

Limited environments needed

Limited costs


Q & A


Recommended Sessions

SESSION # TITLE DATE/TIME

DO4T03S Analyst View: Leading Your DevOps Enterprise Journey 11/19/2015 at 10:00 am

DO3T20S

Autotrader Applies a "Patton and Gandhi" Approach to

Optimize Its DevOps Adoption Curve and

Communications to Drive Consensus

11/19/2015 at 1:00 pm

DO3X114S

Freeing the World from Slow: How Service Virtualization

and the Concept of S.P.E.E.D. Will Steer You Away from

Committing Continuous Delivery Suicide

11/19/2015 at 3:45 pm


Must See Demos

Application Test DemoCreate Better Application Tests

Theater 4

DevOps SimDevOps Simulation Experience

Theater 3

Continuous App InsightAutomate Tests for Better Apps

Theater 4

Service VirtualizationDeliver Better Apps Faster with SV

Theater 3


Follow On Conversations At…

Smart Bar

Theaters 3 & 4

Tech Talks

Theaters 3 & 4


For More Information

To learn more, please visit:

http://cainc.to/Nv2VOe

CA World ’15

http://cainc.to/Nv2VOe

http://bit.ly/1wbjjqX

Technology

Removing Crucial Dependencies to Enable KPN as a Virtual Telecom Provider