Considering moving your data and applications to the cloud? Tune in to learn why Swisscom can deploy services within minutes instead of weeks, using OpenStack and Avi Networks. Learn how Swisscom overcame challenges such as ensuring HA with no single point of failure, achieving zero packet loss in the NFV cloud with multicast traffic and low jitter, and more. View this webinar on-demand to: - Hear about Swisscom’s IT journey with OpenStack and the Avi Vantage Platform - Understand key features that Avi Vantage delivered for Swisscom, such as load balancing, elastic scale, an iWAF and security, analytics with a distributed architecture - See a live demo of the Avi Vantage Platform in action Watch the full webinar: https://info.avinetworks.com/webinars-swisscom-and-avi-networks

1. OpenStack-Based NFV Cloud
at Swisscom
Challenges and Best Practices

2. Ranga Rajagopalan
CTO/Co-founder, Avi Networks
Praveen Yalagandula
Sr. Director of Engineering, Avi Networks

3. Agenda
1. Swisscom NFV Cloud journey
2. Avi Networks LBaaS
3. Avi and OpenStack Integration
4. Demo

4. Swisscom NFV Cloud Journey
Presented at OpenStack Spring Summit 2018 with Swisscom and HPE

5. Swisscom TV & Entertainment

6. Swisscom TV Some Facts and Figures
..more then 2 Mio STB’s
> 650 Channels (SD, HD, UHD)
..more then 1.5 Mio Customer
25 Pbyte Storage / Year
> 2.8 Tbit/s Unicast Streaming
peak from Datacenter
>90 Pbyte of Storage
> 750K unique user per month
on Web & Mobile
Customer Satisfaction > 8

7. Next Generation Entertainment & TV Services
1st step virtualization
2nd step virtualization
3rd step virtualization
TV Platform Virtualization

8. MediaCloud
MediaCloud: The Big Picture
Virtualization Layer / RedHat OpenStack / KVM
CPU
Hardware
Virtual
Network
Memory
Hardware
Storage
Hardware
Network
Hardware
Virtual
CPU
Virtual
Memory
Virtual
Storage
vHE
Service Orchestration
Radio AVI AppBE nPVR LiveTV LivingDocs xyz
VNF Mgr VNF MgrVNF MgrVNF MgrVNF Mgr VNF Mgr VNF Mgr VNF Mgr
Channel/Service Definition
Business process workflow
MonitoringandServiceMonitoringGoal to have all Entertainment Service on the MediaCloud

9. Media Function Virtualization

10. Current headend operations challenges
Video
Signal
Dedicated
Management
Transcoders A
Manager
Transcoders B
Manager
Transcoders C
Manager
Multiplexer
X
Multiplexers Y
Manager
Multiplexers Z
Manager
Transcoder A
Transcoder A
Transcoder A
Transcoder B
Transcoder B
Transcoder C
Ch. 1
Ch. 2
Ch. 3
Ch. 4
Ch. 5
Ch. N
Multiplexer
Y
Multiplexer Z
Multiplexer
X
Transcoder A
Transcoder A
Transcoder A
Transcoder B
Transcoder B
Transcoder C
Ch. 1’
Ch. 2’
Ch. 3’
Ch. 4’
Ch. 5’
Ch.
N’
Multiplexer
Y
Multiplexer Z
Multiplexers X
Manager
Backup
headend
Active
headend
● Too many managers to manage
● Disaster Recovery expensive
● Costly Equipment Upgrades/Exchanges
● Operational complexity
● Missing Flexibility to add new channels
Current situation
Switch STB
CDN

11. Virtualized headend with HPE VHM
1 click channel deployment
One interface
to manage it all
HPE Virtual
Headend
Manager
Multiplexer
X
Transcoder A
Transcoder A
Transcoder A
Transcoder A
Ch. 1
Ch. 2
Ch. 3
Multiplexer X
Virtualized
Headend
Transcoder B
Transcoder B
Ch. 4
Ch. 5
Multiplexer
Y
Transcoder B Multiplexer Y
Transcoder C
Ch. N
Multiplexer Z
Backup
Backup
Transcoder D Multiplexer WChannels
on the fly
Switch STB
CDN
Fast time to launch new service One click channel deployment Non-proprietary infrastructure
Quick and automated lifecycles Simplicity: One interface for all CAPEX and OPEX reduction
Video
Signal

12. Maturity Levels of virtualized applications
Monolithic functions are
decomposed into micro-services
Functions separated from underlying
hardware
Functions deployed on hypervisor-driven,
virtualized infrastructure resources
Operated as part of the cloud, lifecycle
fully orchestratable
Decoupled
Virtualized
Cloudified
Decomposed
Market View R&D View
Bare Metal x86
Microservices
Automate / Orchestrate
Virtualize

13. Enterprise cloud vs. virtual Headend workloads
1. CPU, RAM or Storage bound performance
2. Aggregated view of resources
(CPU, Memory, resources overcommitted)
3. Endpoints
(Applications need the OS)
4. Many and small virtual machines
1. CPU & I/O bound performance
(DPDK, SR-IOV, etc.)
2. Enhanced platform awareness
(Internal Architecture relevant for guests)
3. Middlepoints
(Data-plane network bypass the OS)
4. Fewer and larger VMs
IT Cloud Virtual Headend

14. Key network performance and quality features
PCI-passtrhough
✓https://docs.openstack.org/admin-guide/compute-pci-passthrough.html
SR-IOV (Single Root I/O Virtualization)
✓http://en.wikipedia.org/wiki/X86_virtualization#PCI-SIG_Single_Root_I.2FO_Virtualization_.28SR-IOV.29
✓https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking
NUMA (Non Uniform Memory Access)
✓http://en.wikipedia.org/wiki/Non-uniform_memory_access
DPDK (Data Plane Development Kit)
✓http://en.wikipedia.org/wiki/Data_Plane_Development_Kit

15. Avi Networks LBaaS
Elastic Scale on OpenStack-Based NFV Cloud

16. BARE METAL VIRTUALIZED CONTAINERSON PREMISES PUBLIC CLOUDVIRTUALIZED CONTAINERS
Modern, Scalable, Multi-Cloud Architecture
CONTROLLER
(SaaS / Customer-Managed)
SERVICE ENGINE
SEPARATE CONTROL
& DATA PLANE
ELASTICITY
INTELLIGENCE AUTOMATIONMULTI-CLOUD
Copyright © 2018 Avi Networks

17. Avi and OpenStack Integration
H Heat
LBaaS

18. Provider Mode
SEs are shared across all the tenants
Tenant Mode
Dedicated SEs per Tenant
Provider Tenant
Tenant 2
Tenant 1
Tenant 3
Admin Tenant
Tenant 2
Tenant 1
Tenant 3
Avi Vantage in OpenStack – Tenancy options

19. Legacy Active-Standby
HA
App-1 App-2
Client Requests to
App-1
High Availability with Avi Vantage

20. Legacy Active-Standby
HA
App-1 App-2
Client Requests to
App-1
Active Active
HA
App-1 App-2
Client Requests to
App-1
High Availability with Avi Vantage

21. Legacy Active-Standby
HA
App-1 App-2
Client Requests to
App-1
Active Active
HA
App-1 App-2
Client Requests to
App-1
Cluster N+M HA
App-1 App-2 App-3 App-4 App-5
Client Requests to
App-1
High Availability with Avi Vantage

22. Active Active
HA
App-1 App-2
Client Requests to
App-1 Policy and Machine Learning based AutoScale
If CPU > 80% or Available Capacity < 10% increase
scale
Elastic increase Capacity - Auto-Scale

23. Active Active
HA
App-1 App-2
Client Requests to
App-1
OpenStack: Getting around throughput limitations
OpenStack Neutron Restriction:
A single IP can only be served by a one vNIC
• No concept of ECMP
• Bottleneck: PPS Limits on single vNIC

24. Active Active
HA
App-1 App-2
Client Requests to
App-1
OpenStack: Getting around throughput limitations
Upstream
Router
OpenStack Neutron Restriction:
A single IP can only be served by a one vNIC
• No concept of ECMP
• Bottleneck: PPS Limits on single vNIC
Workarounds
• Some plugins have API to place same IP on multiple
vNICs (e.g., Contrail)
• BGP peering with upstream router

25. Preview 1 of OpenStack Summit

26. Preview 2 of OpenStack Summit

27. Demo
A single application services fabric across multiple clouds

28. Thank you
@AviNetworks
Schedule a Demo!
1. OpenStack Summit, Berlin
1. Talk 1: Analytics-Driven Canary and Blue/Green
Continuous Delivery of Cloud Applications
1. Talk 2: Advanced Network Services: Load Balancing
as a Service (LBaaS)