CORD: Central Office Re -architected as a Datacenter

CORD: Central Office Re-architected as a Datacenter

Guru ParulkarON.Lab and Stanford University

[email protected]

Inventing Future Access and Services

발표자

프레젠테이션 노트

Thanks! Good morning – it is so nice to back here. Appreciate the opportunity. I want to talk about CORD – Central Office Re-architected as a Datacenter It started as a use case of ONOS and has become an important project in its own right. Please note there is a very informative talk on ONOS by Madan Jampani who is one of the key architects of ONOS, later this afternoon. Please check it out. Coming back to CORD, let me begin with our mission …

mailto:[email protected]

CORD + ONOS Community

Community includes all stakeholders of the value chain: service providers and vendors: OEM, merchant silicon, white box, disaggregated functions, system integrators, …

For service providers and by service providers

ON.LAB SERVICE PROVIDER PARTNERS

COLLABORATORSVENDORPARTNERS

VOLUNTEERS

40+ Companies

발표자


Today our partnership and community looks like this. We have 5 leading service providers from almost all important geographies: US, China, Japan, and Korea. All these service providers have a shared vision, they are actively engaged, providing and building SDN and NFV use cases, and looking to do field trials and deployments based on ONOS. We have 8 vendors who represent almost all major vendors that provide products and solutions to service providers around the globe. I want to also mention we have more than 20 collaborating organizations that are actively contributing to our mission in some significant way. I hope you agree we have created a very strong partnership and community for CORD – this is just the beginning. With this partnership and community we are in a strong position to realize our vision and achieve our mission.

Special Thanks To …

Steven Rim

Central Office – The Most Important Infrastructure for Service Providers

Central Office

Residential

Enterprise

Mobile

• One central office may support– 10K+ residential subscribers – 10K+ mobile subscribers– 1K+ enterprise customers

• There are 1000s of CO operated by service providers

• It is a service provider’s “gateway” to its customers

• It represents a great vantage point for a service provider

– Enable new services to customers – Potentially a key differentiator over

OTT providers 1Central Office is broadly interpreted. It can be small or large and has different names in different contexts.

What is wrong with a Central Office?

Large number of COs

Evolved over 40-50 years

300+ Types of equipmentClosed Proprietary

Source of high capex and opex

Source of lack programmability

Inhibits innovation

Limits service providers’ ability to create new services

CORD Mission: Deliver to Service Providers

Economies of a datacenter Infrastructure built with a few commodity building blocks using

open source software and white boxes

Agility of a cloud provider Software platforms that enable rapid creation of new services

With an open CORD reference implementation

발표자


Our mission is to deliver to service providers 1. Economies of a data center 2. Agility of a cloud provider What do these requirements mean? This means service providers want to build their infrastructure like the datacenters – that is build it using a few commodity building blocks that use open source software and hardware. For example datacenters use commodity servers, white boxes for the leaf and spine switches, and many open source software platforms and tools. The net result is that the service providers can scale their infrastructure and significantly reduce capex and opex. Agility means they want to introduce new revenue generating services quickly – what cloud providers do so well.

CORD: Central Office Re-architected as Datacenter

Large number of COs


300+ Types of equipmentHuge source of CAPEX/OPEX

SDN Control Plane -ONOS

VNF/Services Control Plane – XOS

White Box White Box White Box

White Box

White Box White Box

White Box White Box White Box White Box


Leaf-Spine Fabric

White Box

White Box

SDN enabled Central Office Fabric

Commodity servers, switches, and network access

Access

(Core)

SDN NFV

Cloud

Domains of Use: Residential, Mobile, EnterpriseRO

ADM(Core)

Commodity Servers, Storage, Switches, and I/O

PONOLT MACs

Leaf-SpineFabric

BBUs(Multi-RATs)

ONOS + OpenStack + XOS

MobileEnable 5G w/

Disaggregated/Virtualized RAN &

EPC, Mobile Edge

Residential vOLT, vSG,

vRouter, vCDN

EnterpriseSDN-WAN with

programmability,packet-optical convergence

EnterpriseMetro Ethernet

Field Trial

POC at

ONS

POC at

ONS

CORD: An Open Reference ImplementationCORD POD

An open service delivery platform that provides cloud

economies and agility.

From FTTH-as-a-Serviceto Software-as-a-Service.

Hardware Blueprint

Bill of Materials– OCP Servers– OCP Switches– Access Devices

Assembly Instructions– …

Testing Infrastructure– …

Open Source Software

Core Components– OpenStack– ONOS– XOS– OCP

Domain Services– R-CORD: vOLT, vSG, vRouter, …– E-CORD: vCE, vOAM, vFirewall, -- M-CORD: vBBU, vSGW, vPGW,

Other Services– Monitoring

Many configurations of CORD possible for different contexts for different operators

Ciena and Radisys to provide “turn-key CORD PODs”

Service Provider Interest: Across the Globe

Service Provider Interest

AT&T ONOS + CORD + Optical

Bell Canada R-CORD, Packet-Optical

China Unicom E-CORD, M-CORD

China Mobile R-CORD

NTT Comm E-CORD, Packet-Optical

NTT East R-CORD

SK Telecom M-CORD, Packet-Optical

Windstream CORD

Verizon M-CORD (R-CORD?)

DT, Telecom Italia, Orange,

Telefonica, EE/BT, Vodafone

ONOS use cases and

[R,E,M]CORD

OTT Validation and Strong Interest

Leading OTT providers validate CORD architecture and approach and show strong interest

Opportunity for us to work with them and their ecosystem to accelerate CORD development and adoption

Partnership with Key Industry Organizations

BBFNext Gen Broadband

Use Cases

MEFNext Gen Enterprise

Use Cases

CORDOpen Reference Implementation

Use Cases/Requirements

Open Source ImplementationsInput to Specifications

IEEE5G Capabilities

IEEE

Join ONOS and CORD

If you want to create real value with SDN, NFV and Cloud and want to really impact service provider infrastructure and services, join ONOS and CORD.

http://onosproject.org/ and http://opencord.org/

http://onosproject.org/

http://opencord.org/

CORD Building Blocks

CORD: Central Office Re-architected as Datacenter

Large number of COs


300+ Types of equipmentHuge source of CAPEX/OPEX

SDN Control Plane -ONOS

VNF/Services Control Plane – XOS

White Box White Box White Box

White Box

White Box White Box



Leaf-Spine Fabric

White Box

White Box

SDN enabled Central Office Fabric

Commodity servers, switches, and network access

Access

(Core)

SDN NFV

Cloud

ONOSOpen Source SDN OS for Service Provider Networks

● Scalability, High Availability & Performance

● Northbound & Southbound Abstractions

● Modularity

Disruptive SDN Control Plane Requirements &ONOS Architecture

Northbound - Application Intent Framework(policy enforcement, conflict resolution, virtualization, slicing)

OpenFlow NetConf . . .

AppsApps: Config, Control, Management

Distributed Core(scalability, availability, performance, persistence)

Southbound(discover, observe, program, configure)

Scalability, Performance, HA

Distributed Core

Control, Config, & Management apps

Northbound Abstraction

Protocol Independence Southbound Abstraction

발표자


When you think about disruptive SDN where control plane is separated from the devices and especially for the service providers context we have some demanding requirements. These include o The control plane has to have scalability, performance, and HA – this requires well architected distributed system or core o Need the ability to create control plane applications and services – innovative ones too – this requires appropriate northbound abstractions o We also need the control plane to be independent of specific southbound protocols including OpenFlow – this requires appropriate southbond abstractions Here is a high level architecture of ONOS that we have built – Thomas will talk about ONOS in more detail. It has distributed core that is designed for scalability, availability, performance and persistence southbound that can support multiple plug-ins for different protocols norhtbound that is based on the intent framework that makes it easy to create apps on the top Thomas will provide more details.

ArchitectureScale, Performance, HA

North & South-Bound Abstractions

ONOS Milestones and Evolution

Incremental SDN

Disruptive SDN

Micro-Services

* In progress

OpenFlow & P4*On Many Hardware & Software

Switches

South-Bound ProtocolsNetConf/Yang, BGP-LS, PCE, TL-1

On Legacy Devices

ConfigurationNetConf/Yang, OVSDB

North-Bound InterfacesIntent Framework, REST

Model Based Services*Yang based service definition

ONOS Platform Ready for Production Deployment

Solid Architecture Foundation

Minimal Features and Functions

Skeleton PlatformDec, 2014

Strengthened Architecture/Core

Many Features and Functions

Production ReadinessApril 2016

Huawei: building commercial solutions with ONOSCiena: offer ONOS commerciallyOthers in the pipeline and will be announced in 2016

발표자


I am pleased to see at least a couple of companies already building or starting to build commercial products and solutions based on ONOS.

Platform and Solutions: The Virtuous Cycle

Platform Solutions

Enable

EnrichSDN OS: ONOS CORD

Packet-OpticalSDN-IP PeeringAnchor StackMulticast content dist…

FabricR-CORDE-CORDM-CORDGaining Traction and Momentum

SP partners drive the

use cases/soluti

ons

발표자


As we know any platform by itself is not useful and cannot succeed. A platform has to enable many interesting and useful solutions. ONOS is the SDN OS platform that enables many solutions and that is the value of ONOS or any platform for that matter. We are in the process of creating the following solutions with ONOS. And as we build these solutions and make them more and more real, we find new requirements and opportunities to make ONOS better. This has been a very powerful cycle – it has been true for other platforms in the past.

Laptop Simple CPE

GPON ONT

Third-party Provider portal

Service Provider Portal

Subscriber Portal

Residential CORD (R-CORD) Implementation

PONOLT MACs

Fabric

ONOS + OpenStack + XOS

Residential Services: vOLT, vSG, vRouter, vCDN

Commodity Servers, Storage, Switches, and I/O

AT&T U-verse:

발표자


Now let me describe the set-up for the CORD POC demo. On the right is a proof-of-concept central office re-architected as datacenter. The infrastructure is comprised of commodity servers. Three open source platforms control, configure and manage the infrastructure and services – ONOS – the SDN Control Plane, Openstack – which manages VM’s and XOS- a cloud operating system built on Openstack that provides the overarching service management platform. As you can see, the proprietary boxes are disaggregated and their functions are instantiated either as services on commodity hardware or as control applications on ONOS. What’s also interesting here is that the OLT box is disaggregated into a standalone OLT MAC and the remaining functions of the traditional OLT are virtualized. On the left, is the subscriber home. The complex CPE that typically resides in the subscriber home is replaced with a simple Netgear box with Open WRT software. All the complex functions of the CPE are virtualized and moved to the Telco Central Office <click for animation – sckipio part will appear> The demo set-up includes two access technologies – GPON with openflow enabled GPON OLT MAC and open-flow enabled G.fast bridge with GPON, in effect highlighting that CORD is applicable to a diversity of access technologies.

CORD Software: External View

CORD POD

Controller RESTful API

Operator Specification (TOSCA, Yang)

Old/New OSS/BSS Systems

CORD Internal View: Residential

Controller: XOSService GraphResource PolicyScaling PolicyCustomer Policy

vOLT

Controller

vSG

Controller

vRouterResidentialSubscribers

Controller

Controller

vCDN

ControllerOpenStackDocker ONOS

Controller Controller

Monitoring

Everything-as-a-Service (XaaS) / Micro-Services ArchitectureHide all the complexity of VM/container management below “service abstraction:”

scaling, fault tolerance, load balancing, …

Enterprise WAN: Current State of the Art

Central OfficeE-Line

L3VPNROADM ROADM

ROADM

ROADMService provisioning takes days, weeks or

even months

Firewall

IDS

Internet

Public Cloud

Policy Control

Very hard tomonitor and control

VPNExpensive and vertically integrated equipment

HQ

Regional HQ

BranchOffice

BranchOffice

Very hard to spawn VNFs, enterprises use OTT instead

발표자


What’s assumption on connectivity between pods: existing infrastructure etc. incremental intro of services

E-CORD: Win-Win for Enterprises & Providers

Observe, Control, Adapt

InnovativeServices

Security, policy control, …

Virtualized Net on Demand

Customer Control

SDN WAN, Simple on-prem

SDN Control Plane - ONOS

NFV Orchestration w/XOS

SDN Fabric

Commodity servers, switches, network access

+

Carrier-grade “Network as a Service” – fastest growing SDN market (SD-WAN)built on an open CORD platform for rapid innovation

POC at ONS

ControllerService GraphResource PolicyScaling PolicyCustomer Policy

Everything-as-a-Service (XaaS) / Micro-Services Architecture

vCECarrier Ethernet

Controller

Enterprise VNFOpenStackDocker

ControllerMonitoring

ControllerControllerONOS

vRouter

ControllervOAM

ControllerEnterpriseSubscriber

E-CORD Internal View

Controller

Mobile Operator ChallengesIn the last 5 years

$50 Billion Spectrum investment

(~50 Mhz)

100,000% Increase in Wireless Data

Traffic

$5 Billion LTE System investment

(RAN, EPC)

Alternative “shared” access

(WiFi, LAA, LTE-U)

Closed Proprietary

Boxes

New and very diverse devices

with IoT

Slowing revenue growth

Agile and cost-efficient deployment

M-CORD Objectives

Provide customized services and better QoE to customers

Enhance resource utilization, especially spectrum

• On-demand deployment• Virtualized /disaggregated RAN and EPC• Commodity H/W and open source

• Customized service composition• Reduced latency and increased throughput• Differentiated QoE based on service requirements

• Real-time resource management• Exploit multiple RATs • Monitoring & Analytics framework

M-CORD: Enable 5G with/on CORD

MME, SGW, PGW

Mobile Edge Services

Caching, SON, Billing

Disaggregated/Virtualized

RAN

Disaggregated/Virtualized

EPC

BBU, RRUfront haul fabric

SDN Control Plane - ONOS

NFV Orchestration w/XOS

SDN Fabric

Commodity servers, switches, network access

+

POC at ONS

Platform for next gen mobile services + Software RANSeveral incumbent vendors said it cannot be done or crazy…

Now they are partnering with us for the next phase of M-CORD

M-CORD – Internal View

Mobile Subscribers

Operator Specification (TOSCA) + GUI

Service GraphResource PolicyScaling PolicyCustomer Policy

Everything-as-a-Service (XaaS) / Micro-Services Architecture

RRH

vMME

vBBU vSGW vPGW

OpenStack Monitoring vCDNONOS

Controller

Controller Controller Controller

ControllerControllerControllerController

Controller

CORD Provides Cloud Economies and AgilityFully Exploits Micro-Services (Access-as-a-Service)Fully Exploits Disaggregation (vOLT vSG vRouter)Fully Exploits SDN (overlay, underlay, services)

CORD is Catalyzing an EcosystemActive Developer Community (Carriers and Vendors)Two Partners Providing Integration (Ciena, Radisys)Partnerships with Industry Organizations (BBF, MEF, IEEE)

Great opportunity to contribute and impact practice of networking

Summary

Academic Research: Open Source and Path to ImpactAcademic Research: Open Source and

Path to Impact

Idea to Impact Practice of Networking

Idea Prototype Standards: IETF/ITU/…

Product Product Adoption

5-10 YearsLot of risks

Lot of consensus building/politicsDependency on product vendors

AcademiaPublish

Be Happy

Academic Research: Open Source and Path to Impact

Emergence of Open Source SDN and NFV

New Model: Idea to Practice

IdeaPrototype

Contribute to Open Source Platform

6-18 monthsNo industry-wide consensus required

Many paths and opportunities to impact

Network Operators

Software Vendors

Solution Vendors

NetworkOperators

Similar to what happens in the web world …

Academic research community has to change its model: research/innovation

Thank You!

Documents

CORD: Central Office Re -architected as a Datacenter