OpenStack - based NFV Cloud at Swisscom Challenges and Experiences - PowerPoint PPT Presentation

OpenStack - based NFV Cloud at Swisscom Challenges and Experiences

Agenda – Swisscom IPTV – A story of Innovation and Success – E2E Signal Chain Ranga Rajagopalan – E2E Service Orchestration Vision AVI Networks Inc. CTO – Lessons Learned rangar@avinetworks.com – Swisscom-HPE virtual headend project – Legacy vs virtual headend Mihajlo Zivkovic – Maturity levels of applications Swisscom (Schweiz) AG Product Owner – Enterprise Cloud vs. Media processing platform mihajlo.zivkovic@swisscom.com – Virtual Network performance and Container Networking – Multicast on OpenStack Marco Loetscher Hewlett Packard Enterprise – AVI Networks: Elastic Application Services Solution Architect marco.loetscher@hpe.com – A distributed architecture – Application Services – Elastic scale – Demo

Swisscom TV & Entertainment 3

Swisscom is a Marketleader since December 2015 1.5 Mio. Customers 2 Mio. STB’s in the field 3.4 Mio. Households 8 Mio. Population 2Mio. on Swisscom DSL 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 4

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

The Journey of Swisscom TV It’s a Story of Innovation and Success 2006 2009 2010 2011 2013 2015 2017 1. November 25. February 23. March 30. June 28. Decembar April November Launch Bluewin TV Start HD-Sender Swisscom TV Air Marketleader Digital TV 1 Million Customers HBB TV Mediaroom Launch TV1.0 Phase-out Entertainment 0S3 2014 Decembar 2016 2012 Launch Teleclub Play (Subscription VOD) April 16. January Voice Search with Launch Replay TV Swiss Dialects UHD 2014 2015 April Decembar Launch TV 2.0 Marketleader Switzerland 6

Next Generation Entertainment & TV Services Swisscom TV E2E Signal Chain 7

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

MediaCloud: The Big Picture Goal to have all Entertainment Service on the MediaCloud MediaCloud Channel/Service Definition Bussiness process workflow Service Orchestration Monitoring and Service Monitoring vHE Radio AVI AppBE nPVR LiveTV LivingDocs xyz VNF Mgr VNF Mgr VNF Mgr VNF Mgr VNF Mgr VNF Mgr VNF Mgr VNF Mgr Virtual Virtual Virtual Virtual CPU Memory Storage Network Virtualization Layer / RedHat OpenStack / KVM CPU Memory Storage Network Hardware Hardware Hardware Hardware 9

Media Cloud - Virtual HeadEnd Lessons learned Organizational challenges: – Vendor management (working mode with Vendors). – Mindset of the project staff. – Transforming engineers into the new "cloud" world. – Operation of two environments (legacy and cloud). – Knowledge and the experience (combined application with infrastructure and network) – Organization and processes . Technological challenges: – Working on the bleeding edge of the technology. – Technology unknowns. – Infrastructure : very large high performance media cloud solution. – Zero packet loss in cloud environment with the multicast. 10

Media Function Virtualization 11

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

Virtualized headend with HPE VHM Virtualized Headend Ch. 1 Transcoder A 1 click channel deployment Ch. 2 Multiplexer Transcoder A X One interface Ch. 3 Transcoder A to manage it all Backup Transcoder A Multiplexer X HPE Virtual Headend Ch. 4 Transcoder B Manager Multiplexer Video Ch. 5 Y Transcoder B Signal Switch STB Backup Transcoder B Multiplexer Y Ch. N Multiplexer Z Transcoder C CDN Channels Transcoder D Multiplexer W on the fly 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 13

Virtual Headend ETSI Reference Architecture NS and VNF Catalogs OSS/BSS Service Orchestration NFV Service, VNF and Infrastructure Orchestrator Description EMS 1 EMS 2 EMS 3 Transcoder Muxer Probe VNF Manager(s) VNFM VNF 1 VNF 2 VNF 3 Virtual Virtual Virtual Virtualization Layer (HyperV, KVM, ESX) Computing Storage Network NFVI Infrastructure Virtualized Virtualization Layer Orchestration Infrastructure Manager(s) Computing Storage Network Standard Infrastructure Hardware Hardware Hardware Hardware Resources NFV MANO 14

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

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

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 17

Containers in VMs vs. Baremetal • The transcoding applications from Ateme and Harmonic are provided in Docker containers • We decided to put the containers into a virtual machine • Why? • Docker Networking App 1 App 1 App 1 • Hardware independence • VM as “bridge” between application and physical App 1 App 1 App 1 environment • Management and Monitoring Hypervisor Docker Engine • Virtualization Overhead: 5-10 % Operating System Operating System • Additional Component (Guest OS) to be managed • Physical Server Physical Server Cost of Hypervisor 18

Docker Networking – net=bridge: • Container is connected with the Network Bridge • Same IP addresses per Host, 1 NIC only • Standard Mode – net=none: • No network connection of the container (i.e. for number crunchers, batch jobs, etc.) – net=container:<CONTAINER | ID>: • Container is using the NW connection of a “neighbor” • Allow reachability of multiple segregated processes that under the same IP – net=host: • Container has direct access to physical NICs of the hos 19

Multicast in OpenStack • No multicast available out-of-the-box • Virtual layer-2 switches support IGMP snooping: – Open vSwitch 2.5 supports IGMP snooping – Open vSwitch 2.7 contains bugfixes to enable multicast with multiple provider VLANs – http://openvswitch.org/features/ – https://github.com/openvswitch/ovs/blob/master/FAQ.md – Linux Bridge 2.4 supports IGMP snopping – http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge#Snooping 20

Multicast in OpenStack – recommendations • Neutron provider network: • Don’t use Neutron -L3-Agent • Neutron does not route any multicast traffic • Use Neutron provider network • Use routable public VLAN configured on top-of-rack switches • Use router outside OpenStack • Use gateway outside OpenStack • Attach Nova instances directly to provider network • Configure multicast routing / PIM on the physical router 21

AVI Networks 22

Monolithic Appliances to Modern Distributed Architecture Management Plane: UI/CLI Monolithic Appliance Software Data Plane: LB Service Engines Controller APPLICATIONS DATA CONTROL Separate Control & Data Plane 23 Manage as one, not many devices