CORD Presentation at ONS by Larry Peterson

Transcript

1. Central  Office  Re-­‐architected   as  a  Datacenter  (CORD)     Open Networking Lab In collaboration with AT&T – See Demo at the ONS Showcase –
2. 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 Telco Central Office
3. CORD = SDN x NFV x Cloud SDN NFV Cloud Resource & Service Management Commodity Hardware + Software
4. Cloud NFV SDN CORD = SDN x NFV x Cloud Exploits both NFV and SDN Some VNFs run in VMs Some VNFs “run in” WhiteBox Switches Catalyzes function disaggregation Clean-slate approach to “function bundles” Exploits Cloud Best-Practices Services are the “unit of orchestration” Both “global” and “local” functionality
5. GPON (Access) ROADM (Core) Commodity Servers, Storage, Switches, and I/O CORD – Hardware Architecture PON OLT MACs Leaf-Spine Fabric PON OLT MACs 48-port, 1RU, I/O Board 1-­‐4                5-­‐8                  9-­‐12            13-­‐16          17-­‐20        21-­‐24      25-­‐28          29-­‐32          33-­‐36      37-­‐40            41-­‐44          45-­‐48 Optical  10  GbE  (Active)                              1-­‐12 Optical  10  GbE  (Standby)                        1-­‐12 Back  Panel Front  Panel
6. CORD – Software Architecture XOS OpenStack Nova Keystone Neutron ONOS OVX Control Applications Services . . . . . . . . . . . . Virtual Networks and other Flow Rules (programmed into switching fabric) Virtual Machines (instantiated on commodity servers) Manage Services Manage Fabric and Host Control Apps Manage Virtual Infrastructure
7. Residence/Enterprise Central Office CPE   ONU   OLT   ETH   AGG   BNG   Legacy Central Office Acronyms •  CPE – Customer Premises Equipment •  OLT – Optical Line Termination •  BNG – Broadband Network Gateway Backbone   Core   Data   Center  
8. Residence/Enterprise Central Office ONU   CORD ACCaaS vBNG vBNG vOLT … Backbone   Core   Access-as-a-Service (ACCaaS) – Implemented by an ONOS control application (vOLT), where each tenant corresponds to a Subscriber VLAN. Logically centralized Service Controller Scales over a set of Service Instances Multi-Tenant with Tenant Abstraction
9. Residence/Enterprise Central Office ONU   CORD SUBaaS vBNG vBNG vCPE ACCaaS vBNG vBNG vOLT … Backbone   Core   Subscriber-as-a-Service (SUBaaS) – Implemented by a Docker container (vCPE), where each tenant corresponds to a Subscriber Bundle.
10. Residence/Enterprise Central Office ONU   CORD SUBaaS vBNG vBNG vCPE ACCaaS vBNG vBNG vOLT INTaaS vBNG vBNG vBNG … Backbone   Core   Internet-as-a-Service (INTaaS) – Implemented by an ONOS control application (vBNG), where each tenant corresponds to a Routable Subnet.
11. Residence/Enterprise Central Office ONU   CORD CDN vBNG vBNG Cache SUBaaS vBNG vBNG vCPE ACCaaS vBNG vBNG vOLT INTaaS vBNG vBNG vBNG … Backbone   Core   Content Distribution Network (CDN) – Implemented by a global caching hierarchy (including local caches), where each tenant corresponds to a Content Provider.
12. Software Architecture XOS ONOS vOLT ACCaaS SUBaaS INTaaS CDN vBNG OpenStack vCPE Cache
13. Service Composition Details vCPE vCPE vCPE vCPE vCPE vCPE vBNG vBNG vBNG vBNG vBNG vOLT HPC_Client vBNG vBNG Cache vCPE_WAN To Internet vCPE_LAN To Subscriber Set of VM Instances Connected to a Private Virtual Network
14. Service Composition Demo vBNG vBNG vBNG vCPE vCPE vCPE vCPE vCPE vCPE vBNG vBNG vOLT vBNG vBNG Cache Set of VM Instances Connected to a Private Virtual Network ONU   With AT&T Foundry NetGear (OpenWRT) PMC Sierra PON OLT MAC Minimal (See Next Talk) Dockerfile (Xerocole) Akamai Licensed CDN
15. NFV Orchestrator (NFVO) VNF Manager (VNFM) (XOS) Element Manager (Service Controller) Virtual Infrastructure Manager (VIM) (OpenStack, ONOS) VNFI VNF (Service Instance) ETSI NFV Architecture
16. 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 Demonstrating Proof-of-Concept at ONS (Visit the Showcase) Complete CORD POD for Field Trials (December 2015) Summary
17. Join the journey @ onosproject.org