Virtualization, Automation and DevOps – Why it’s Taking so long for Telcos?
summary
Sri Lanka Telecom (162 years old) is using SDN, NFV and cloud but still fails to automate because of a deep hardware mindset, fragmentation of open projects (confusing choices like ONAP vs OSM), and hard orchestration between PNFs and VNFs across bare‑metal, VMs and containers; mobile penetration is 150% and broadband 34%, so revenue growth stalls while traffic rises. Operators report 80% lack skills and 70% retention risk. Recommended actions are top‑down culture change, realistic ROI messaging (costs rise before they fall) and an aggressive skills‑bridging program.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:40About Sri Lanka
- 4:42About Sri Lanka Telecom
- 7:46The Business Problem
- 15:32The Hardware Mindset
- 26:50Open Source
- 27:59Network Functions
- 29:00Orchestration
- 31:13Standards
- 32:54Solutions
- 34:28Summary
- 35:11Questions
related talks
38mTowards the Cloud Native Telco: Learning from the Trenches
15mKeynote: Scaling DevOps – Moving from Mechanization to Automation
28mDevOps Road Blocks
36mNFVI Upgrades and NFV Migrations with Live Critical Telco
18mPast, Present, and Future of Network Operations
24mCI-CT-CD, Devops loop for future Telco Cloud
21mHardware Automation Deployment and Test with Big Scale in ChinaMobile NFV cloud
07mEnabling IT Operations - Transforming to DevOps