Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Continuous Deployment | Stefan Nilsson | LTG-23

771 views

Published on

Presentation held by Stefan Nilsson, Ericsson, at Lean Tribe Gathering in Gothenburg Nov 7 2014.

Published in: Leadership & Management
  • Be the first to comment

Continuous Deployment | Stefan Nilsson | LTG-23

  1. 1. Continuous Deployment Stefan Nilsson 2014-11-07
  2. 2. Wcdma Radio Access network Continuous Deployment presentation | Ericsson Internal | © Ericsson AB 2014 | 2014-05-23 | Page 2
  3. 3. Continuous Deployment – high level Definition Continuous deployment: A process whereby all code that is written for an application is immediately deployed into production! Continuous Deployment presentation | Ericsson Internal | © Ericsson AB 2014 | 2014-05-23 | Page 3
  4. 4. Continuous Deployment – ericsson’s view › 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 presentation | Ericsson Internal | © Ericsson AB 2014 | 2014-05-23 | Page 4
  5. 5. What’s in it for: 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 Customer Correction 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 Continuous Deployment presentation | Ericsson Internal | © Ericsson AB 2014 | 2014-05-23 | Page 5
  6. 6. WMR challenges Q4 2013 – Q3 2014 Continuous Deployment presentation | Ericsson Internal | © Ericsson AB 2014 | 2014-05-23 | Page 6
  7. 7. Continuous Deployment presentation | Ericsson Internal | © Ericsson AB 2014 | 2014-05-23 | Page 7
  8. 8. Continuous Integration Continuous Integration Product Development by XFTs S D T S D T S D T S D T S D T Continuous Deployment presentation | Ericsson Internal | © Ericsson AB 2014 | 2014-05-23 | Page 8 Release System Design SW Design Test Quality Early Phase Release Validation Quality Continuous Legacy Test Hourly cycle Daily cycle Weekly cycle Sprint cycle Release Before CI With CI Constantly high quality – close to RFS level Slow feedback Fast feedback & constantly high quality
  9. 9. Sprint N Sprint N+1 Main Track Select build during week 1,3,2 CI: Weekly Test CI: Weekly Test CI: Weeklly Testt CI: Weekly Test CI: Weekly Test CI: Weekly Test RNC & RBS Q-statements1 CI: ODT CM:Release SW CI: analysis of ODT Acceptance test lab Storage 2 Continuous Deployment presentation | Ericsson Internal | © Ericsson AB 2014 | 2014-05-23 | Page 9 Field Intro. to Live network RNS 1 or 2 Generic FOA plan First sprints’ Delivery Decision. 3 Create Ticket for SGW Deliver 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 Customer Q-statement 4 ODT: Out Delivery Test SGW: Software Gateway
  10. 10. Challenges introducing Continuous Deployment Quality aspects Ability to deliver Software Ready For Service in (RFS) quality every third week Handle risky product changes Fulfil regulatory requirements Technical areas Backwards compatible interfaces and system behavior Incomplete features shall not cause problems in the live network Commercial aspects Don’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 place Don’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 Continuous Deployment presentation | Ericsson Internal | © Ericsson AB 2014 | 2014-05-23 | Page 10

×