Install & Upgrade PDU OSS Technical Outlook Q2

You might also like

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 19

Install & Upgrade

PDU OSS Technical outlook


Q2 2014
Colum Carter, Portfolio CA
content
› business overview
› External and internal operations
› Portfolio outlooks

Ericsson Internal | 2014-05-28 | Page 2


Install & Upgrade overview

Environment
External operations internal
› Network Rollouts (NRO) › OSS-RC Upgrade Complexity Improvements
Serviceability Theme investigating IP completed & design work in
improvements to help NRO. progress, spread across 14B & 15A
– OSS-RC Upgrade Complexity
Improvements being promoted as › CI for OSS-RC End-to-End Upgrade rollout
one of the top improvements to cover areas other than Admin/Master
– Also looking at best practices for server, still in progress
upgrades
› NPT AT&T OSS-RC Upgrade Observation
activity

› ENIQ Upgrade Improvements delivered


– Reducing & automating manual steps
– One single orchestration point
– Reduction of downtime for a specific feature
– One GA Upgrade

› Status per RA:


– OSS-RC: fully engaged, design work
starting on improvements
– Assurance: upgrade improvements
delivered
– SON/LMS: nothing to report
– TOR: 14B under development

› Concern/Issues:
Ericsson Internal | 2014-05-28 | Page 5
– None
Outlook
executive summary

Ericsson Internal | 2014-05-28 | Page 6


Portfolio outlooks

Development strategy
Key challenges
OSS RC

Some examples
›› Development of values for some Key Metrics:
Strategy:
Downtime in
–– Reduction ~ Level
15 minutes for Admin
of Effort server. 2/3 hrs throughout an average MoP
for projects
– End-to-End Upgrade time
› OSS-RC End-to-End ~78Complexity
Upgrade hrs (PDU Testing figures).
Improvements
– Level- of Effort
Reduce & –Automate
1599 man hours
the for a840+
existing Sprint Upgrade
manual project
steps
– Configuration Freeze
- Orchestration time – from
of Upgrade from~one 6 up to ~ 24
central hrs (varies as some
point
customers haveminor
› Some other longerapplication
freeze times)
upgrade improvements (see slide 15 for more
details)

– Reduce Downtime & Configuration Freeze


› No investment
- Current architecture will only go so far…

– Instrumentation
› Upgrade timing & failures (via E2E Upgrade Complexity Improvements)

› Key Challenges:
– Upgrade Complexity Improvements is a huge challenge to undertake
› There are such varying servers with varying degrees of complexity and steps
› Cost of these improvements may mean it risks being rejected from project or
we will have capacity/resourcing issues
Late/Sudden
–Ericsson Network
Internal | 2014-05-28 | Page 8 Evolution features with impacts on upgrade & install
ENIQ Stats & Events

›› Development
Some examples
Strategy:
of values for some Key Metrics:

––No investment
ENIQ Stats: currently planned
– Decision for further~install
– Downtime 12 hrs& quoted
upgrade investments
(Sprint 13A to will be based on…
13B)**
–– Drive from time
Upgrade the Market
~ 8 hrs (PDU testing for LTE & EPC)
–– feedback
Level of on 14.x–Upgrade
Effort 201 manImprovements
hours for a Sprint Upgrade project (ENIQ Stats
co-deployed with OSS-RC so hours are also shared with OSS-RC project
costs)

› Key Challenges:
– ENIQ Events:
– None
– Downtime ~ 48 hrs (AT&T 12.1 to 13A) **
– Upgrade time ~ 10 hrs (PDU testing for LTE & EPC)
– Level of Effort – 250 man hours for a Sprint Upgrade project

– ** Note: there are extra activities included in these upgrades so down for service time was increased as a
result of this.

Ericsson Internal | 2014-05-28 | Page 9


SON (OM, Viz & Policy Manager)

› Development Strategy:

– No investment for install & upgrade for SON legacy products (PL Decision
to focus on ENM)

› Key Challenges:

– None.

Ericsson Internal | 2014-05-28 | Page 10


LMS

› Development Strategy:

– Focus on improving upgrade with glassfish is complete however still problems which
are being monitored.
– Focus on customer requirements & scalability for now
- No new LAT improvements

› Key Challenges:

– Only a handful of customers and plan to restrict 14B and 15A with full GA on 15B
– Use of Glassfish in LAT is causing problems with upgrade & install times

Ericsson Internal | 2014-05-28 | Page 11


ENM
› Development Strategy:
– Reduction in Level of Effort for projects
› Simple & Automated Install & Upgrade procedure
- 1 activity flow install & upgrade (Reduced Level of Effort – by at least 25%)
- e.g. integrated Healthchecks would be a step towards this
› Upgrade Independence
› Reduces the amount of OSS upgrades needed
– Deployment tooling needed
› To aid dimensioning, preparation, installation & upgrade of ENM deployments
› Reduce manual effort currently needed to handcraft deployments
– Reduce Downtime & Configuration Freeze
› Capability for Zero Downtime
› Capability for No Configuration Freeze (for successful upgrades)
› Instrumentation & Monitoring
› Instrumentation of Install & Upgrade times (and also failures)
› Monitoring of Install & Upgrades e.g. Alarms on failures via OSS Monitoring Tool
(OMT)
› Key Challenges:
– Ensuring Region/Customer confidence in architecture & new upgrade/install improvements in
ENM is a big challenge. For example, so that Customer Upgrade Project costs & lead-times
can be reduced by removing some of the “safety nets” that has grown into projects due to
nervousness & past experiences with PDU OSS products
– Rollback of rolling upgrade technically is a big challenge
TheInternal
–Ericsson move| 2014-05-28
of the data| Page layer
12 to ENM for Assurance is a big challenge particularly around
migration of data, upgrade and downtime
Portfolio outlooks

roadmaps
OSS-RC Roadmap
upgrade Investment started!
O14A/O14A.1 O14B/O14B.1 M13B (M-MGw
O15A only) O15B

• CR 182/109 18-FCP 130 • CR 154/109 18-FCP 130 5239 - • 105 65-0334/27573 - • Nothing planned yet
5239 - ARNE Export Improvement in EC's Installation Upgrade Enhancements
improvement using CSLib process on X86 • 105 65-0334/30072 –
(Feature Pack) • CR 255/109 18-FCP 130 5239 - Visibility of Customer
• CR 183/109 18-FCP 130 Optimise the installation time for Installed software version
5239 - ARNE Rule engine FM AAU's
redesign to improve &
reduce validation time in
import/GUI
• CR 901/109 18-FCP 121
9272 - ARNE to Switch OFF
rules validation at Client and
Server during EU Upgrade
• CR 905/109 18-FCP 121
9272 - Config freeze doc
improvements and add to
EU docs

O14A O14B O15A O15B

Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
2014 2015 2016
Released Ready for Contract Indicative Candidate Dates for products are GA dates
Ericsson Internal | 2014-05-28 | Page 14
ENIQ Stats ROADMAP
upgrade Investment completed!
ES14A.1 ES14B/14B.1
M13A M13B (M-MGw
ES15B only) ES16A

• Upgrade Automation and • Rolling Upgrade: • Market or feedback driven • Migration to ENM (16A)
Usability Improvements: The plan is to have rolling improvements only (see slide
Reduced downtime during upgrade of features to 9 for details)
upgrade, improved reduce the per-feature
procedure usability (execute downtime in an upgrade
majority of upgrade from
coordinator, reduced
number of manual steps and
Migration to
automation ), reduced ENM will take
duration a couple of
releases for
• One GA Upgrade
ENIQ. Exact
timeframe is
not confirmed
yet

E14A E14B E15A E15B E16A

Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
2014 2015 2016
Released Ready for Contract Indicative Candidate Dates for products are GA dates
Ericsson Internal | 2014-05-28 | Page 15
ENIQ Events Roadmap
upgrade Investment completed!
EE13B EE14A.1/EE14B.1
M13A M13B
EE15B/16A
(M-MGw only) EE16B

• Upgrade Automation and • One GA Upgrade • Market or feedback driven • Migration to ENM (16B)
Usability Improvements: improvements only (see
Reduced downtime during slide 9 for details)
upgrade, improved procedure
• Rolling Upgrade:
usability (execute majority of The plan is to have rolling
upgrade from coordinator, reduced upgrade of features to
number of manual steps and reduce the per-feature Migration to
automation), reduced duration, downtime in an upgrade.
Auto-provisioning of Mediation ENM will take
Zone
http://jira-oss.lmera.ericsson.se/br
a couple of
owse/EQEV-112 releases for
ENIQ. Exact
timeframe is
not confirmed
yet

E13B E14B E15B E16A E16B

Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
2014 2015 2016
Released Ready for Contract Indicative Candidate Dates for products are GA dates
Ericsson Internal | 2014-05-28 | Page 16
SON roadmap
Nothing planned!
14A M13A
14B M13B (M-MGw
15A only) 15B

• Limited Availability of • Nothing planned • Nothing planned • SON OM migration to


SON Viz (ENIQ Upgrade ENM (to be confirmed, 15B
Improvements (except or later)
rolling upgrades), see
ENIQ roadmaps for
details)

14A 14B 15A 15B

Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
2014 2015 2016
Released Ready for Contract Indicative Candidate Dates for products are GA dates
Ericsson Internal | 2014-05-28 | Page 17
LMS roadmap
Nothing planned!
14A M13A
14B M13B (M-MGw
15A only) 15B

• Nothing planned • Nothing planned • Nothing planned yet • Nothing planned yet

14A 14B 15A 15B

Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
2014 2015 2016
Released Ready for Contract Indicative Candidate Dates for products are GA dates
Ericsson Internal | 2014-05-28 | Page 18
ENM Roadmap
Next gen upgrade & install
14A 14B M13B (M-MGw
15B only) 16A

• Limited Availability • General Availability • Simple & Automated Install & • Instrumentation of Installs &
Solution: Solution providing the Upgrade Procedure Upgrades
following:
• Capability for Zero Down for • 105 65-0334/25643 - Upgrade • Monitoring of Installs &
Service time • Integrated Healthchecks Independence Upgrades
• Capability for No
Configuration Freeze (for • 105 65-0334/30326 - ENM • 105 65-0334/30142 - Visibility
successful upgrades) Upgrade characteristics of Customer Installed software
version

• 105 65-0334/30426 - ENM


Deployment Tools
• 105 65-0334/30427 - ENM
Dimensioning
• 105 65-0334/30428 - ENM
Deployment Preparation

14A 14B 15B 16A

Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4

2014 2015 2016


Released Ready for Contract Indicative Candidate Dates for products are GA dates
Ericsson Internal | 2014-05-28 | Page 19
Ericsson Internal | 2014-05-28 | Page 20

You might also like