Central Office Re-­‐architected as a Datacenter (CORD) Open Networking Lab In collaboration with AT&T Telco Central Office Large number of complex facilities AT&T alone operates 4-5k Central Offices Each serves 10-100k residential, enterprise & mobile customers Evolved piecemeal over the past 40-50 years Source of huge CAPEX/OPEX costs Difficult to introduce new services Especially when compared to OTT cloud providers! Want the economies of commodity infrastructure Want the agility of scalable services CORD = SDN x NFV x Cloud Resource & Service Management SDN NFV Cloud Value Proposition Leverage SDN, NFV and Cloud technologies and best practices Reduce CAPEX with virtualized commodity hardware Reduce OPEX with automated service orchestration Accelerate time-to-market with cloud provider agility Add value to existing cloud services with edge footprint SDN x NFV x Cloud Source of technology to reduce CAPEX/OPEX e.g., virtual machines, virtual networks, elastic scaling Source of services to offer subscribers Control Plane Services e.g., VPN, Q-in-Q Termination, MPLS Tunneling,… Data Plane Services e.g., Parental Control, WAN Acceleration, NAT,… Global Cloud Services e.g., CDN, NoSQL DB, Analytics, Internet-of-Things,… CORD – Hardware Architecture Resource and Service Management PON OLT MACs PON OLT MACs Commodity Servers, Switches, and Storage ROADM (Core) GPON (Access) Leaf-Spine Fabric CORD – Software Architecture ... Services ... Manage Services XOS Manage Fabric and Host Control Apps OpenStack Nova Virtual Machines (instantiated on commodity servers) Keystone Neutron Control . . . Applications . . . ONOS Manage Virtual Infrastructure OVX Virtual Networks and other Flow Rules (programmed into switching fabric) Transforming Today’s C.O. into CORD Virtualize existing hardware devices, producing their software counterpart running on commodity hardware. Provide a framework that these software elements (plus any other cloud services the operator wants to run) can be plugged into, producing a coherent end-to-end system. Transforming Today’s C.O. into CORD Virtualize existing hardware devices, producing their software counterpart running on commodity hardware. Provide a framework that these software elements (plus any other cloud services the operator wants to run) can be plugged into, producing a coherent end-to-end system. Devices We Want to Virtualize Residence/Enterprise CPE ONU Central Office OLT ETH AGG BNG Backbone Core Acronyms • CPE – Customer Premises Equipment • OLT – Optical Line Termination • BNG – Broadband Network Gateway Data Center Devices We Want to Virtualize Residence/Enterprise CPE ONU NAT DHCP VoIP Firewall Parental Control … Central Office OLT ETH AGG BNG Backbone Core Data Center Devices We Want to Virtualize Residence/Enterprise CPE ONU Central Office OLT ETH AGG Authorization Physical Connect Point … BNG Backbone Core Data Center Devices We Want to Virtualize Residence/Enterprise CPE ONU Central Office OLT ETH AGG BNG Backbone Core QoS VPN GRE Tunneling MPLS Tunneling Q-in-Q Termination … Data Center Virtualization Process – Generic TLA à vTLA = Merchant Silicon + SDN Control Function (Control App running on ONOS) + NFV Data Function (Deployed as a Scalable Service) TLA = Three Letter Acronym Virtualization Process – Specific CPE à vCPE = White-box Switch in the home + N/A + Container-per-Subscriber OLT à vOLT = GPON Interface Card in the Central Office + App running on ONOS + N/A BNG à vBNG = White-box Switching Fabric in the Central Office + App running on ONOS + N/A Legacy Central Office Residence/Enterprise CPE ONU Central Office OLT ETH AGG BNG Backbone Core Acronyms • CPE – Customer Premises Equipment • OLT – Optical Line Termination • BNG – Broadband Network Gateway Data Center vOLT + vCPE + vBNG Central Office Residence/Enterprise Backbone Core ONU vOLT vCPE vCPE vCPE vBNG Caution: Once you transform legacy hardware appliances into their software counterparts, existing bundles will be refactored! Data Center vOLT + vCPE + vBNG Central Office Residence/Enterprise Backbone Core ONU vOLT vCPE vBNG Data Center Transforming Today’s C.O. into CORD Virtualize existing hardware devices, producing their software counterpart running on commodity hardware. Provide a framework that these software elements (plus any other cloud services the operator wants to run) can be plugged into, producing a coherent end-to-end system. Everything-as-a-Service (XaaS) (Multi-Tenant) Service Controller (Open Interface) Service Instances (Virtualized Commodity HW) Logically centralized interface to network-wide functionality Many points of implementation distributed across the network. Everything-as-a-Service Access-as-a-Service (ACCaaS) Implemented by vOLT control app running on ONOS Tenant Abstraction = Subscriber VLAN Subscriber-as-a-Service (SUBaaS) SDN NFV Implemented by vCPE running in a Linux Container Tenant Abstraction = Subscriber Bundle Internet-as-a-Service (INTaaS) SDN Implemented by vBNG control app running on ONOS Tenant Abstraction = Routable Subnet (minimal placeholder) Content Distribution Network (CDN) Implemented by a distributed set of caches Tenant Abstraction = Content Provider Cloud Software Architecture ACCaaS SUBaaS INTaaS CDN XOS OpenStack Nova Keystone Neutron vOLT vBNG ONOS OVX XOS Manages Tenancy Graph ACCaaS SUBaaS CDN INTaaS XOS (XaaS) OpenStack (IaaS) Legacy Central Office Residence/Enterprise CPE ONU Central Office OLT ETH AGG BNG Backbone Core Acronyms • CPE – Customer Premises Equipment • OLT – Optical Line Termination • BNG – Broadband Network Gateway Data Center vOLT + vCPE + vBNG Central Office Residence/Enterprise Backbone Core ONU vOLT vCPE vCPE vCPE vBNG Data Center CORD NetGear (OpenWRT) PMC Sierra PON OLT MAC PICA8 Switch Central Office Residence/Enterprise Backbone Core ONU ACCaaS With AT&T Foundry SUBaaS Docker Containers CDN Data Center INTaaS Akamai LCDN Proof-of-Concept for Open Networking Summit (June 2015) Summary Transform legacy C.O. into CORD Replace closed/proprietary hardware with “Commodity + Software” Orchestrate software as “Scalable Services” Leverage Open Source Software OpenStack – Provision virtual infrastructure ONOS (ON.Lab) – Host control apps and manage switching fabric XOS (ON.Lab) – Manage services with XaaS as unifying principle Path to Deployment Demonstrate Proof-of-Concept at ONS (June 2015) Complete CORD POD for AT&T Lab Trials (December 2015) Join the journey @ onosproject.org ETSI NFV Architecture NFV Orchestrator (NFVO) (HP NFV Director, Telefonica OpenMano) Element Manager (Service Controller) VNF (Service Instance) VNFI VNF Manager (VNFM) (XOS) Virtual Infrastructure Manager (VIM) (OpenStack, vSphere) Toolkit for building NFVMs Unbundle the NFVO