Stefan Nilsson2014-11-07

Continuous Deployment

Continuous Deployment presentation | Ericsson Internal | © Ericsson AB 2014 | 2014-05-23 | Page 2

Wcdma Radio Access network

Continuous Deployment presentation | Ericsson Internal | © Ericsson AB 2014 | 2014-05-23 | Page 3

Continuous deployment: A process whereby all code that is written for an application is immediately deployed into production!

Continuous Deployment – high level Definition

Continuous Deployment presentation | Ericsson Internal | © Ericsson AB 2014 | 2014-05-23 | Page 4

› It is– Continuous Deployment of SW containing maintenance corrections,

and sometimes also new features for testing purpose (only)– Making new features available to a few customers to be used in a

small part of their live networks for testing purposes

› It is NOT– Continuous Deployment of new features for sale and commercial

use, Ericsson sells features packages* two times per year.

* denoted as Base Package and Value Pack

Continuous Deployment – ericsson’s view

Continuous Deployment presentation | Ericsson Internal | © Ericsson AB 2014 | 2014-05-23 | Page 5

Ericsson Early detection of problems leads to faster corrections and reduced

correction cost: Constant feedback from a live network enables higher constant

quality (and higher GA quality) than can be achieved with PDU internal Continuous Integration testing only

CustomerCorrection of network specific problems earlier – before GA

(instead of after)Access to the latest SW (and features) every third week for testing

in a small part of the live network

What’s in it for:

Continuous Deployment presentation | Ericsson Internal | © Ericsson AB 2014 | 2014-05-23 | Page 6

WMR challengesQ4 2013 – Q3 2014

Continuous Deployment presentation | Ericsson Internal | © Ericsson AB 2014 | 2014-05-23 | Page 7

Continuous Deployment presentation | Ericsson Internal | © Ericsson AB 2014 | 2014-05-23 | Page 8

Continuous IntegrationRelease

SystemDesign

SWDesign Test

Quality

Early

Phase

Release

Validation

Quality

Continuous Legacy Test

Hourly cycle Weekly cycleDaily cycle Sprint cycle

Product Development by XFTs

S D T S D T S D T S D TS D T

Continuous Integration

Release

Before CI

With CI

Constantly high quality – close to RFS level

Slow feedback

Fast feedback & constantly high quality

Continuous Deployment presentation | Ericsson Internal | © Ericsson AB 2014 | 2014-05-23 | Page 9

Main Track

CI: Weekly Test

CI: ODT

CM:Release SW

RNC & RBS Q-statements1

CI: analysis of ODT

Sprint N Sprint N+1

Acceptance test lab

Field Intro. to Live network RNS 1 or 2

Generic FOA planFirst sprints’

Delivery Decision. 3

Create Ticket for SGWDeliver SW/report o CU(change in KPIs, known limitations etc.)

1. Q-statement and ODT Candidate selection;

2. Store SW in SGW and Gask

3. Delivery Decision meeting:

4. KPI evaluation and Q-statement from the customer’s RNS

Select build during week 1,3,2

Storage 2

Customer Q-statement 4

ODT: Out Delivery Test

SGW: Software Gateway

CI: Weekly Test CI: Weekly TestCI: Weekly Test CI: Weekly Test CI: Weekly TestCI: Weekly Test

Continuous Deployment presentation | Ericsson Internal | © Ericsson AB 2014 | 2014-05-23 | Page 10

Quality aspectsAbility to deliver Software Ready For Service in (RFS) quality every third weekHandle risky product changesFulfil regulatory requirements

Technical areasBackwards compatible interfaces and system behavior Incomplete features shall not cause problems in the live network

Commercial aspectsDon’t include a new sensitive technology in the main track, with Trade Compliance restrictions Third party products (or a new version of an already used one) shall not be built in the main track

before contracts and payment routines are in placeDon’t include a new free open source product (or a new version of an already used one) in the

main track before the license conditions have been reviewed and accepted by legal experts

Challenges introducing Continuous Deployment