ONF Connect 2018

SDN Enabled Broadband Access (SEBA) is an initiative started by AT&T and ONF. It is both a Reference Design jointly developed by a number of operators, and an exemplar implementation based on the reference design. This talk will mainly focus on the Exemplar implementation developed by ONF, AT&T's Atlanta Foundry and the SEBA and VOLTHA community.

We will start by briefly discussing SEBA's origins in R-CORD, then delve deep into the components that make up SEBA including VOLTHA, ONOS apps, NEM and the physical OLTs, ONUs and AGG switches, describing how they all fit together in a modular way. We will describe the engineering development process undertaken in the last 6 months to deliver SEBA, and discuss ways in which the community has been involved. Finally, we will touch upon the roadmap for SEBA and the engagement of operators for filed-trials and deployments.

DT's program Access 4.0 develops and engineers DT's next generation SDN-based access with initial focus on fixed line business FTTH/B/C. Key ingredients are bare metal hardware, open source software and merchant silicon. We will share an update on our progress on the path towards productization.

SEBA pods are located at the access edge of the network and they need to be centrally configured and monitored.  Using ONAP as a global orchestrator is a viable option and this talk addresses the use cases and the architecture of this integration.

Present our engagement on SEBA and VOLTHA (incl. activities, contributions, priorities on functional design, component development, management and automation) related to both reference design and exemplar platform implementation work, as well as planned / proposed next steps.

The scope of this talk is twofold, it will introduce the NGPaaS project by explaining its scope and architectural design and then it will introduce some of the work done for the NGPaaS project and which is related to the CORD and ONOS products of ONF. This includes:

1)The “Telco-PaaS” use case of NGPaaS, which is based on the CORD platform. This use case aims to provide VNFaaS capabilities, together with some value added services like VNF monitoring.

2) A network policy framework for ONOS which follows a disaggregated architecture and allows new policy types to be installed in an ad-hoc fashion.

3) A proposed design for  a VIM-adaption layer for CORD, which would allow support for multiple VIMs whilst also providing a single API for the users of CORD.

There are many changes between the 1.x releases of Voltha and the 2.0 release including the introduction of a very robust high availability model, the containerization of adapters, and a complete rewrite of the core. This talk will focus on outlining the new architecture that has been adopted for the 2.0 release. The talk will also highlight the areas where the new architecture brings about significant improvements and areas where improvements are still required to get to a deployable solution in 3.0.

VOLTHA provides a layer of abstraction over vendor-specific and white-box PON hardware devices. On its northbound interface, VOLTHA abstracts the PON network to appear as a programmable Ethernet switch to an SDN controller. On its southbound side, VOLTHA communicates with PON devices through vendor or device specific OLT and ONU adapters. VOLTHA has adapters contributed by OEM vendors and the community for both proprietary and white box devices. Contrary to what one might expect - the adapters are not just a translation layers; they are fairly complex, state-full modules that implement the core of PON device management. Adding support for a new hardware device entails a fairly good understanding VOLTHA internals which can be daunting especially for smaller white-box vendors with limited software development resources. One of the objectives of the current VOLTHA 2.0 release is to introduce a common OLT adapter that enables rapid onboarding of new white-box and proprietary OLT devices. This new adapter, called OpenOLT, exposes a well-defined protobuf-based, vendor-agnostic gRPC interface on the southbound side. OLT OEM/ODM device vendors are now able to re-use the OpenOLT adapter and focus on implementing the gRPC OpenOLT agent on their device. OpenOLT is actively being developed with code contributions from ONF, AT&T Foundry and members of the VOLTHA community and currently has support for OLT devices from EdgeCore, CIG and Iskratel. This paper presents the motivation, design, interfaces, current status and future development of OpenOLT.

How SEBA can be adapted to support different Access Technologies without changing any of the Core Code/Functionality, while maintaining a simple, Common Abstraction for different Access Equipment and Devices.
 

We propose a new optical access network architecture named “Mini-PON” that enables operators to deploy PON in various environments. Mini-PON uses pluggable module-type OLT and decomposed OLT software components in order to maximize flexibility and cost-efficiency. In the presentation, we explain the benefits of our proposed architecture, and how it actually works cooperating with OSS components in SEBA (e.g. ONOS and VOLTHA).

This talk provides an overview of SEBA-in-a-Box.  SEBA-in-a-Box is a fully virtualized SEBA pod targeted primarily at developers and testers.  It leverages Ponsim to emulate an OLT, ONU, and RG, and Mininet to emulate an aggregation switch, BNG, and DHCP server.  It can be installed on a physical machine or VM in about 15 minutes.  I will describe the SEBA-in-a-Box design, show how to install it, and do a brief demo / walkthrough of its capabilities.

QA testing is one of the processes to find errors and aimed at evaluating a reference design if it meets required results and performance criteria for lab and field trials. Since first release of CORD, Flex has collaborated with ONF QA group in integration, automation and test plan development & execution for CORD and its reference designs. In this talk, we will be going over results and learning from functional, stability, scale and soak testing of SEBA POD running in Flex CloudLabs.  The infrastructure setup at Flex consist of full POD CORD deployed via Jenkins with interconnected OLT, splitter, ONU and subscribers to emulate SEBA workflow