Requirements for Building a Virtualized Central Office Net-Centric 2016 Requirements for Building a Virtualized Central Office Colin Dixon TSC Chair @ OpenDaylight; Dist. Eng. @ Brocade colin@colindixon.com colindixon.com @colin_dixon www.isocore.com/2016 Some content from: Azhar Sayeed and Alan Sardella

What is a Central Office?

What does Central Office do? Everything needed to connect customers to the rest of the network, usually the Internet Customer Internet Central Office

What does Central Office do? Subscriber Management capabilities Subscriber Gateway Authentication and authorization Event and subscriber information logging Optical Line Termination (OLT) for PON/GPON (Passive Optical Network) Service functions Residential/biz services, self service portal, NAT, FW, routing, IPAM QoS management Quota management Video caching Local information servers Mail and file stores Mobile services vBBU – C-RAN Mobile vGateways & Switching Centers HetNet & Traffic Offload gateway

What is a Virtualized Central Office? AKA CORD (Central Office Re-architected as a Data Center) Virtualization and deployment of general purpose compute, storage and network capability at the local central office to deliver Residential services – R-CORD Business services – E-CORD Mobile services – M-CORD Analytics – A-CORD Start with a traditional data center design to deliver general purpose compute, storage and network

Why do we need a V-CO? Increased flexibility Reduce cost Deploy new network functions quickly To flexible subsets of users (or even their traffic) Reduce cost Decouple network functions from h/w (CAPEX) Increased automation (OPEX)

Traditional Data Center Arch. WAN North - South Start with a data center, because that’s what will have the compute and virtualization resources you need. VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM East West

V-CO Data Center Architecture While traditional data centers terminate traffic A V-CO data center is designed to transit traffic North- South VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM WAN East West WAN

V-CO Data Center Architecture Traffic (logically) enters/leaves via VMs Transited between VMs by the DC Network North- South VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM WAN East West WAN

V-CO Data Center Architecture Importantly, traffic might transit other VMs The VMs are Virtual Network Functions (VNFs) North- South VNF VNF VM VM VM VM VM VM VM VM VNF VM VM VM VM VM VM VM VNF VM VM VNF VM VM VM VM VM VM VM WAN East West WAN

V-CO Data Center Architecture Physical elements are divided into Network: provides fabric/underlay Servers: provides computer/storage for VNFs North- South Fabric/Underlay (Network) VM Servers/VNFs (Compute, Storage) VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM WAN East West WAN

V-CO Data Center Architecture Controllers and orchestrators use overlay networks to form service chains of VNFs North- South VNF VNF VM VM VM VM VM VM VM VM VNF VM VM VM VM VM VM VM VNF VM VM VNF VM VM VM VM VM VM VM WAN East West WAN

V-CO Data Center Architecture SDN Controller (Fabric, Overlay, Service Chains) VM/VNF Orchestrator (VM/VNF Lifecycle) North- South Fabric/Underlay (Network) VNF VNF VM Servers/VNFs (Compute, Storage) VM VM VM VM VM VM VM VNF VM VM VM VM VM VM VM VNF VM VM VNF VM VM VM VM VM VM VM WAN East West WAN

V-CO Architectural Requirements Fabric configuration and control Overlay configuration and control Service chaining configuration and control VM and container orchestration VNF lifecycle management VM lifecycle and event management

What is OpenDaylight Open Source SDN controller Many SB drivers: OVSDB, OpenFlow, NETCONF, SNMP, BGP, PCEP, LACP, PCMM/COPS, … Community: 800+ contributors, 100+ deployments Built-in solutions: Service Chaining, Network Virtualization, Policy-based networking, IoT, … Broad vendor and system integrator support Integration with other open source projects: OPNFV, ECOMP, FD.io, OVS, OpenStack, Tacker, …

V-CO Data Center Software Arch. OPNFV (Integration) V-CO Data Center Software Arch. OSS/BSS Policy (NIC, NEMO, GBP) VNFO (ECOMP, Open-O, OSM, …) Service Chaining Overlay Network Fabric VNF Spec (TOSCA) VNF Catlog VNFM (Tacker, Cloudify, …) SDN Controller (OpenDaylight, ONOS) VIM (OpenStack, Kubernetes, …) Fabric/Underlay (Network) VNF VNF VM Servers/VNFs (Compute, Storage) VM VM VM VM VM VM VM VNF VM VM VM VM VM VM VM VNF VM VM VNF VM VM VM VM VM VM VM

Typical Residential Services Model L2 NID/ONT GPON Ethernet Ethernet over G-PON or DSL OLT Aggregation PE - DC User Side Network Side Internet

Residential V-CO High-level view APP/Web/mail Servers VM VM vLoad Balancer VM vIPS/ Malware vFW Traffic-O Policy VM VM NAT ONT GPON vOLT Policing/Shaping VM VM NAT vServices Gateway Quota Management Parental Control Ethernet DC Fabric vFW Demarc Point Central Office µCPE Internet

Mobile V-CO High-level view HSS vMME PCRF Ethernet or Fiber Fronthaul Internet vBBU vGiLAN Services vSGW vPGW Passive Antenna - No eNB vCDN vePDG Virtualized CO Infrastructure Virtualized RAN virtualized BBU Virtualized EPC & Core virtualized MME, SGW, PGW, ePDG & PCRF Virtualized Services including vGiLAN vGiLAN - TCP Optimization, DNS Proxy, NAT, FW virtualized services - Cache, billing, SON etc Wifi

Building a V-CO from Open Source NFV allows us to create V-COs vCPE (Res/Biz V-CO) & vEPC (Mob. V-CO) top NFV use cases Open source components exist for most (if not all) parts of the V-CO architecture OpenDaylight is production-ready for V-COs [1,2] Large, active community Many existing projects for integration with other projects OPNFV, ECOMP, FD.io, OVS, Tacker, OpenStack, … Join us! [1] https://www.sdxcentral.com/articles/featured/opendaylight-powers-carrier-grade-openstack-performance/2016/10/ [2] https://www.opendaylight.org/cloud-and-nfv

Backup Slides

Size/scale depends on the V-CO Deployment Model Functionality Description Mini Pod Redundant environment: hardware and software 3 controllers, multiple compute nodes, data synchronization, and recovery capabilities in case of failure Micro Pod Some redundancy: power, ports, storage Single controller, storage Nano Pod No controllers: only Nova compute and storage nodes Centralized controller, keystone, LDAP, etc. Only compute nodes storage at the branch site