SEBA VOLTHA Residential CORD Saurav Das Director of
SEBA, VOLTHA & Residential CORD Saurav Das Director of Engineering, ONF November 10, 2020 An Operator Led Consortium
CORD: Central Office Re-Architected as a Datacenter Residential v. OLT, v. SG, v. Router, v. CDN Mobile v. BBU. v. MME, v. SGW, v. PGW, v. CDN Enterprise v. Carrier. Ethernet, v. OAM, v. Wan. Ex, v. IDS Access Service Orchestration & Control White-box Switches with Merchant Silicon Cloud BBUs SDN NFV PON OLTs COTS (Off-the-Shelf) x 86 Compute ROADM (Core) Economies of a datacenter, Agility of a cloud provider 2
Outline ● CORD platform changes ● R-CORD & VOLTHA changes ● So what is SEBA? ● SEBA development & roadmap #Open. CORD 3
CORD platform changes 4
CORD platform & build-process (before mid-2018) profile 1 Install OS, Virt 2 Head node 3 Switch/Access s/w 4 Connectivity 5 Configuration 6 User workflow ONOS VOLTHA XOS Open. Stack Ov. S Head Node v. SG OS Ov. S Bare metal OS Bare metal Management network Access Node OS Leaf OS Upstream Dataplane network Spine #Open. CORD OS OS Spine OS 5
Issues with the previous CORD platform & build ● No v v distiniction between development vs deployment Most of the software built from source at “deploy time” Big scripts, scripts calling scripts, long process Monolithic: If something breaks, wipe and start from scratch Brittle: Small variations of hardware/connectivity could break build ● Not flexible or modular v Required specific versions of server OS v Tightly coupled components – cannot exclude or replace components v Required internet access for install ● Hard to use v Choose a profile at start; to change profiles reinstall v No means for adding services at runtime #Open. CORD 6
New CORD 6. 0 platform (July-2018) CORD control software set of Docker containers deployed on Kubernetes using standard tools like Helm charts ONOS VOLTHA Open. Stack XOS profile Kubernetes OS OS OS Bare metal Management network Access Node OS Leaf OS Upstream Dataplane network Spine #Open. CORD OS OS Spine OS 7
R-CORD & VOLTHA changes 8
Traditional Residential Access Central Office Residence RG ONU OLT ETH AGG BNG RG – Residential Gateway OLT – Optical Line Termination BNG – Broadband Network Gateway Backbone Network
Residential CORD – Disaggregated Services v. SGs per sub provide • VLAN termination, • Qo. S • DHCP, NAT Virtual OLT manages and abstracts PON Central Office Residence v. SG AAA VOLTHA RG ONU OLT MAC ETH AGG Leaf-Spine Fabric BNG Backbone Network Fabric provides • Eth aggregation • Routing + the ability to introduce other edge-compute services per subscriber
R-CORD & VOLTHA Demo BBWF 2017 ONOS CORD Head Node … XOS VOLTHA MAAS CORD Compute Node Ov. SG Whitebox To. R Fabric Switch nternet Edge. Core 7712 (Tomahawk 32 x 100 G) Central Office Residential Subscribers Edge. Core Whitebox OLT (ASFv. OLT 16) BCM ONU R G Nokia SD-OLT (Light. Span CF-24 W) Nokia ONU R G
OLT Disaggregation VOLTHA AAA VLANs, IGMP, 802. 1 x, Mcast … Mcast ONOS Backplane Open. Flow PON MAC blades Compute blades Net. Conf Open. Flow Agent Net. Conf OLT API OMCI Stack v. OLT Agent GPON OLT MAC (Celestica) 13 …
VOLTHA Overview
preprovision_olt -t asfvolt 16_olt -H <olt_mgmt_ip>: 59991 enable 0001 f 6 f 4595 fdc 93 channel_group create -n "Manhattan" -d "Channel Group for Manhattan" -a up -p 100 -s 000000 -r raman_none channel_partition create -n "WTC" -d "Channel Partition for World Trade Center in Manhattan" -a up -r 20 -o 0 -f false -m false -u serial_number -c "Manhattan" channel_pair create -n "PON port" -d "Channel Pair for Freedom Tower in WTC" -a up -r down_10_up_10 -t channelpair -g "Manhattan" -p "WTC" -i 0 -o class_a traffic_descriptor_profile create -n "TDP 1" -f 100000 -a 500000 -m 1000000 -p 1 -w 1 -e additional_bw_eligibility_indicator_none ONOS Logical device channel_termination create -i 0001 bb 590711 de 28 -n "PON port" -d "Channel Termination for Freedom Tower" -a up -r "PON port" -c "AT&T WTC OLT" # Wait for 5 sec for PON interface up vont_ani create -n "ATT Golden User" -d "ATT Golden User in Freedom Tower" -a up -p "WTC" -s "BRCM 12345678" -r "PON port" -o 1 # Wait for 5 Sec for ONT to come up ont_ani create -n "ATT Golden User" -d "ATT Golden User in Freedom Tower" -a up -u true -m false tcont create -n "TCont 1" -r "ATT Golden User" -t "TDP 1” #Wait for 5 sec for scheduler configuration to finish. v_enet create -n "Enet UNI 1" -d "Ethernet port - 1" -a up -r "ATT Golden User" gem_port create -n "Gemport 1" -r "Enet UNI 1" -c 2 -a true -t "TCont 1" VOLTHA ONU NNI OLT UNI
May 2017 Sept 2017 March 2018 VOLTHA core Maple Adaptor VOLTHA core Edge. Core Adaptor VOLTHA core Open. OLT Adaptor Closed/Proprieta ry Twisted RPC VM-in-themiddle Edge. Core OLT GRPC (BRCM-BAL based protobufs) Edge. Core OLT GRPC (generic protobufs) Whitebox OLT (including Edge. Core)
March 2018 VOLTHA core Why Open. OLT Adaptor? Generic OLT adaptor - ease of onboarding for new white-box vendors Open. OLT Adaptor Py GRPC client VOLTHA CORE Open. OLT Open. OMCI ONU GRPC (generic protobufs) Alpha ONU Iskratel ONU Arcadyan ONU C++ GRPC srv Chip Driver SDK(s) Whitebox OLT (including Edge. Core) CIG OLT Edge. Core OLT Tellabs OLT Iskratel OLT CIG ONU Tellabs ONU
Subscriber Traffic through v. SG (virt. Service Gateway) ONOS CORD Head Node … VOLTHA XOS Radius CDN CORD Compute Node Video Source Ov. SG Whitebox To. R Fabric Switch nternet Edge. Core 7712 (Tomahawk 32 x 100 G) Central Office Residential Subscribers Edge. Core Whitebox OLT (ASFv. OLT 16) BCM ONU R G Nokia SD-OLT (Light. Span CF-24 W) Nokia ONU R G
So what is SEBA? 19
SEBA Exemplar OSAM-Central Built on the new CORD platform EMS/NMS-adaptor OSAM-Local SEBA POD All control software deployed as containers on compute nodes using Kubernetes Legacy OSS ONAP Providing FCAPS & Inventory Network Edge Mediator (NEM) dhcp v. OLT mcast SR FPM T 3 ONOS Cluster REST Kafka OF OF Redfish VOLTHA Redfish TP TP TP ONU UNI Subscriber traffic ‘fast-path’ to Internet AGG Switch OLT NNI AGG Switch Compute
NEM Monitoring Infrastructure GRAFANA KIBANA PROMETHEUS ELK STACK XOS NEM KAFKA Operator OSS ONOS Alarms, events & stats Logs VOLTHA RG UNI TP TP TP BNG ONU AGG OLT NNI Compute
NEM Workflows SEBA POD All control software deployed as containers on compute nodes using Kubernetes Providing FCAPS & Inventory Network Edge Mediator (NEM) dhcp v. OLT mcast SR FPM T 3 ONOS Cluster OF OF Redfish VOLTHA Redfish TP TP TP ONU UNI Subscriber traffic ‘fast-path’ to Internet AGG Switch OLT NNI AGG Switch Compute BNG is a workload option • External physical BNG • v. BNG in compute • BNG in Agg switches • BNG in OLT boxes
Demo setup BBWF 2018 ONF Booth (Hall 22 a, Booth B 116) NEM User Interface NEM Monitoring Dashboard
Demo setup BBWF 2018 SEBA Peripheral/PNF/Pod Elasticsearch Grafana/Kibana Kafka XOS GUI Logstash Prometheus Exporter XOS Core Synchronizers Software Stack Network Edge Mediator (NEM) Chameleon v. OLT dhcp aaa sadis Tosca Database Radius Server Configuration SR kafka-i ONOS VOLTHA BBSim Hardware RG Alpha RG Iskratel RG Arcadyan RG Adtran RG CIG RG Iskratel ONU DHCP Serve Edge. Core OLT BNG (subscriber RG addressing) Adtran OLT CIG OLT Edge. Core AGG Switch Iskratel OLT (X) Iskratel OLT (G) Compute Nodes Public Internet
Demo setup BBWF 2018 ONF Booth (Hall 22 a, Booth B 116) ONUs: Arcadyan, Alpha, Adtran, CIG, Iskratel OLTs: Adtran, CIG, Edge. Core & Iskratel AGG switch: Edge. Core Servers: VOLTHA, ONOS, XOS, K 8 s, ELK, Docker, Prometheus, Grafana, Kibana
SEBA Development & Roadmap 26
Distributed Dev. Ops - SEBA OM en Op So ftw OLT are (BA CI Simulator L) SEBA System End-to-End OLT, Switch Hardware Redfish APIs 2. THA VOLTHA 2. 0 0 AT&T OLT & ONU Tec Pro hnolo file gy s Test automation Certification
SEBA Distributed Dev. Ops – ONF Responsibilities Joint Development with AT&T Foundry • Daily scrum • Bugs - issue analysis; root-cause; • Design discussions for new features • Documentation • Recommend bestpractices/training Support VOLTHA/SEBA Community • Weekly SEBA public meetings • JIRA issues – kanban methodology • Mailing lists, Slack community support • VOLTHA meetings, TST, architectural guidance Deliver SEBA/VOLTHA Stability & New Scale Features • ONF team resposible for all ONOS and NEM feature development • FCAPS features – kpis, alarms & logs in SEBA monitoring infrastructure • AT&T workflow development • Integrate with new ONU and OLT vendors • AGG switch features • Focus on stability of VOLTHA – robustness and repeatability • Investigate scalability and performance of full SEBA system Tooling • BBSim – Guide NTT in the development of PON simulator • SEBA-in-a-BOX: Complete end to end emulation of SEBA system with ponsim & mininet QA • Developing automated feature tests • Extending framework for hardware based end -to-end tests • Work with community to develop test automation and certification procedures
SEBA Deployment Goal @ AT&T Up to 64 ONUs per PON port SEBA POD Internal GE Management Switch ONU+RG DHCP Server (subscriber RG addressing) Up to 16 PON ports / OLT device ONU+RG Edge. Core OLT DHCP Server (POD Edge. Core OLT ONU+RG Edge. Core OLT Up to 16 OLT devices Edge. Core OLT AT&T External BNG AGG Switch (Tomahawk 32 x 100 G) Compute Node 29 VOLTHA, ONOS, NEM, Kubernetes, Docker registry, Gateway VM Abstract OLT addressing) Radius Server External OSS Public Internet
Roadmap • BNG Disaggregation • Redundancy • Using P 4 in Aggregation switch • Integrating VOLTHA 2. 0 & Technology profiles • Implementing more operator workflows • ISSU • Performance & scale improvements for Trials • Integrating M-CORD profile to use SEBA as mobile backhaul
Summary • CORD Platform changes in last 6 months • • • Move to Docker containers, Kubernetes & Helm charts Greatly easier to build/install Significant improvement in modularity & flexibility • VOLTHA & R-CORD changes in last 6 months • • • VOLTHA bottom-up discovery operation more ‘SDN’ Open. OLT and Open. OMCI-ONU adaptors lowering the bar for vendors Use of fast-path through hardware for subscribers (no v. SG) • SEBA: SDN Enabled Broadband Access • • Built on the new CORD platform, and includes all of the above Significant focus on FCAPS infrastructure Multiple operator workflows Headed to trials at AT&T
Backup
Voltha Core 2. 0 – 4 µservices REST OFAgent CLI Netconf View Only µservice Handles: • Read • List Device Handler µservice Handles device-specific operations: • Create/Update/delete only • Packet-out operations (OF) • Packet-in operations (OF) • Device lifecycle management (discovery -> deletion) Technology Profiles µservice Manages technology specific details (e. g x. PON): • Provisioning profiles • Specialized flow decomposition Cluster Management µservice Handles cluster specific operations: • event filter • backup & restore • etc. Kafka North. Bound Affinity Routing Proxy Etcd South. Bound Affinity Routing Proxies Adapter X Copyright © Ciena Corporation 2016. All rights reserved. Confidential & Proprietary. Adapter Y Adapter Sim Adapter Test 33
Abstraction: PON as a Quasi-Ethernet Switch UNI Ports Match Action In-port pbits Push vlans Apply meter Assign queue Outport Match Action In-port Push vlans Apply meter GOTO table Outport Meter Queues Scheduler Table Pbit mapping Queuing policy (GEM) TCONTs (BW) GEMs per TCONT Scheduler policy Technology Profiles NNI Ports
- Slides: 34