ONOS(Open Network Operating System) とは
NEC ⾦海 好彦 アジェンダ
▌ ONOSの概要
▌ ONOSのアーキテクチャと内部構造
▌ Intentとは
▌ ONOS向きシナリオ例
▌ ユースケース
▌ デモ
2 © NEC Corporation 2015 ONOSとは、⼀⾔で
ONOS, a SDN network operating system designed for high availability, performance, scale-out, and rich abstractions.
抽象化NEモデルを提供し、フローセット アップ性能に注⼒した、 分散SDNコントローラ基盤
3 © NEC Corporation 2015 ON.lab/ONOS ProjectへのNECの関与
1.0 Avocet release
Stanford Clean Slate
2007 2012 2014/9 2014/12
4 © NEC Corporation 2015 バージョン毎の⽬標
3ヶ⽉毎のバージョンアップ Emu Drake Enhancements for Lab trial & initial CORD deployment Platform Development deployment at SP Cardinal networks POC Blackbird demonstrati on at Collaborate with other Demonstrate ONS2015 open source projects, Performance, like ONF, OPNFV, etc. Avocet Scale & HA Real world Announce deployments in Open R&E networks Source Grow Community Development partners and community 5 © NEC Corporation 2015 ONOS Partner and Collaborator
Partners
Collaborators
6 © NEC Corporation 2015 ONOSが考えるSoftware-Define Networking とは
Control Apps Config Apps Mgmt Apps
Features SDN Network Operating System
Control Plane Disaggregation
Hardware
Agent OS
Loader
Merchant Silicon Legacy Closed Whitebox
7 © NEC Corporation 2015 ONOSが考える望ましいSDNの姿
telnet, ssh, … “REST”, telnet, ssh, …
Features Features SDN対応
Control Plane Control Plane
Hardware Hardware
8 © NEC Corporation 2015 ONOSアーキテクチャ概観
Apps ▌ SBプロトコル独⽴ なNBI Northbound Application Intent Framework, Global Network View, Flow Objectives (policy enforcement, conflict resolution) ▌ 論理的に集中した Distributed Core 分散基盤 (scalability, availability, performance, persistence)
▌ NEを抽象化し、 Southbound SBプロトコル独⽴ (discover, observe, program, configure)
なビューを提供 OpenFlow NetConf . . .
9 © NEC Corporation 2015 ONOSの構造(概要)
分散コントローラー
▌ 独立したインスタンス Apps ▌ インスタンスを追加削除 がシームレス
▌ スイッチ毎にマスターコ ントローラが異なる ONOS GlobalGlobal NetworkNetwork ViewView // StateState ▌ アプリケーションからは1 つのコントローラとして 見える ONOS Instance 1 ONOS Instance 2 ONOS Instance 3
10 © NEC Corporation 2015 Intent Example
Host to Host Intent
COMPILATION
Path Intent Path Intent
INSTALLATION
Flow Rules/Objectives Flow Rules/Objectives
Flow Rules/Objectives Flow Rules/Objectives
• Flow Rule/Flow Objectiveはフローテーブルの抽象化 (シングル/マルチテーブル抽象に対応) • Flow Objectiveは、OpenFlow1.3+に近いが、それに加え装置のパイプライン差異を抽象化
11 © NEC Corporation 2015 ONOSの特徴
性能とスケーラビリティに注⼒
C Apps
A. デバイスやリンク検知速度 Northbound - Application Intent Framework (policy enforcement, conflict resolution) • < 100ms B • ONOS part <10ms Flow rule subsystem B. Intent スループット • 150k ops/sec A Distributed Core C. Intent の伝搬遅延 (scalability, availability, performance, persistence) D • < 50ms D. Flow フループット Southbound • 500K to 3M ops/sec (discover, observe, program, configure) Adapter Adapter . . .
OpenFlow NetConf . . .
詳しくはWeb上の White Paper参照
12 © NEC Corporation 2015 ONOS向きシナリオ例 (1/2)
⾃動化された制御ループ
リアルタイムにTE等々 アプリ (e.g., CORD:fabric)
13 © NEC Corporation 2015 ONOS向きシナリオ例 (2/2)
⾼頻度制御、バースト制御
アプリ
NW全域に渡る グローバル最適化 API公開し、 多数のユーザ要求を 迅速にNEに反映する 必要がある
14 © NEC Corporation 2015 CORD (Central Office Re-architected as Datacenter)
SDNによる局舎の再設計 Central Office Re-architect as a DataCenter (CORD)
Goal: Achieves lower OPEX/CAPEX in central office by replacing legacy network appliances with commodity SDN devices and servers. • Combine ONOS with OpenVirteX (virtualized network), OpenStack, and XOS (orchestrator of different IaaS modules (incl. Amazon EC2, OpenStack, ONOS, …) • Develop virtual images of network functions (BNG, CPE, OLT, CDN server) and group them so that operator can use it as a “Service” Main participants: AT&T and Ericsson
Service defini ons Virtual func on instances Tenant defini ons Leveraging carrier- XOS (Service Orchestration) grade HA and performance to enable ONOS fast service setup OpenStack OpenVirteX (NW virtualization)
Fabric mgʼmt & traffic control Virtual infra mgʼmt ROADM (Core)
vCPE vCPE vCDN vCDN vBNG PON PON vCPE vOLT vCPE vBNG OLT OLT vOLT MACs MACs GPON
(Access) Commodity Servers, Switches, and Storage
16 © NEC Corporation 2015 CORD Key Building Blocks
CORD key components- • Commodity hardware • SDN Control Plane (ONOS) Applications • NFVI Orchestra on (XOS, Openstack) • Open Leaf Spine Fabric • Simple on-prem CPE + vCPE • Virtualized Access (PON OLT MAC + vOLT) SDN Control Plane NFVI orchestra on • Virtualized Func ons ONOS XOS • Virtualized BNG
Spine
Switches
Control
Fabric
Leaf
Switches I I O O
Metro Core I vOLT vBNG LDAP PON OLT Link O Access MACs DHCP ONT Link vCPE RADIUS Simple Switch
20K-100Ksubscribers/CO Commodity hardware Data Subscriber Home Central Office Re-architected as Datacenter 17 17 © NEC Corporation 2015 A closer look at XOS- Service Orchestration for CORD Service Composi on Mobile PGW XCODE NLA CDN Customers
Residential BNG CDN CG-NAT Firewall NFVI Orch-XOS Customers
Enterprise VPN WanEx DSA IDS Customers Service Abstrac on
Firewall Parental Subscriber-as-a- CDN-as-a- Control service service
BNG CGNAT Internet-as-a-service ……..
XOS
vBNG app vOLT app vCPE app XOS opera onalizes Openstack Openstack Keystone Nova Neutron ONOS
• XOS is a cloud opera ng system built using Openstack Firewall vCPE vBNG • XOS provides: service abstrac on and service composi on • Network operators can provision services and let XOS worry Caching/ CGNAT CDN DPI about interfacing with Openstack and doing VM mgmt
Commodity Hardware
18 © NEC Corporation 2015 SDN-IP
レガシーIP NWとOpenFlow NWの相互接続 および実網試験 SDN-IP (SDN and legacy IP peering)
Goal: Make SDN network interoperate with legacy IP networks • Enable SDN network to behave as an AS using ONOS • Deploying ONOS to real environment to test its scalability and reliability Main participants: Internet2, FIU/AmLight, and CSIRO Deployments in operation
Implement BGP speaker Provides apps to interoperate with redundancy of BGP routers and forward BGP speakers transit traffic and send/ receive IP traffic between SDN and internet domains Internet2 (US)
CSIRO FIU/AmLight (Australia) (South America)
20 © NEC Corporation 2015 ONOS Deployments in Progress
KREONET/KISTI (Korea) GigaPoP
Intercontinental deployment (Internet2 , GEANT, GARR, FIU/AMLight, NAP, RedClara, Santiago) 12 universities and research institutes ESnet (US) / AARNET (Australia) exchange routes. BGP peering (15k routes announced) L3 communication without core routers
ON.Lab local office network ONOS starting to have a global footprint in R&E networks Reactive forwarding
21 © NEC Corporation 2015 Packet-Optical
WDM装置とOpenFlow装置の統合制御 Packet/Optical Integration
Goal: Centralized multilayer control of packet-domain and optical-domain • Optimize network usage over packet and optical layers • Enable on-line path setup (Bandwidth on-demand, calendaring) Main participants: AT&T, Ciena, Fujitsu, and Huawei
Implement southbound TL1 BW Calendaring Control Apps Config Apps Mgmt Apps providers for multiple vendors, and enhance data ONOS model in ONOS
Multi-layer path provisioning
Packet Network Datacenter 2 Datacenter 1
Failure detection and rerouting in optical layer
Optical Network
23 © NEC Corporation 2015 Multi-Layer Network without Converged Control Plane
C E A IP IP Logical Tunnels Full Mesh MPLS IP B IP IP D Multiple protection modes Peak rate (up to 4 times BW) provisioning P3 P5 Primary IP IP P1 IP P4 IP IP P2 Routers Protected IP IP
Static planning R7 R2 R4
ROADM
R1 ROADM ROADM ROADMs Light Paths
ROADM ROADM R5 R6 Lightpaths R3 ROADM ROADM 24 © NEC Corporation 2015 Conceptual Solution: Multi-Layer SDN Control
BW 1. Centralized control of packet and optical Calendaring Control Apps Config Apps Mgmt Apps 2. Multi-layer optimization based on availability, economics and policies ONOS
Datacenter 2
Datacenter 1
Packet Network
Optical circuit re-routed
Optical Network
25 © NEC Corporation 2015 Carrierʼs Potential Cap-Grow-Drain Strategy
Segment Rou ng Op cal control Segment Rou ng Op cal control Segment Rou ng Op cal control (for MPLS network) (for MPLS network) (for MPLS network)
ONOS ONOS ONOS
Packet Packet Packet Network Network Network Whitebox switches Whitebox Whitebox Whitebox Whitebox switches switches Whitebox switches switches Drain Cap switches
Op cal Op cal New Network SDN Network Op cal Edge Network Grow
Route Big Flows to Cap-Grow-Drain op cal network = Bring SDN to backbone without fork lift upgrade Cap Packet-based backbone – Grow packet edge and op cal core with Drain the packet-based backbone as donʼt grow the legacy backbone SDN control plane and make the best most traffic transi ons to new packet of proprietary routers use of packet-op cal technologies edge and op cal core network
26 © NEC Corporation 2015 Next Step: Vertical Integration of ROADMs
ROADM controller Control Apps Config Apps Mgmt Apps Control and config of WSS and transponders
Signal Monitoring and Adjustment Metering and alarms SDN Network Opera ng System
demux mux fiber
pass through Agent controller add/drop OS HAL WSS Hardware transponder Whitebox Legacy
27 © NEC Corporation 2015 Transport SDN
トランスポートネットワーク制御の集中化 Transport-SDN
Goal: Offer flexible and easy-to-use multi-layer/multi-domain/multi-device view/ control of transport network which consists of legacy and pure-SDN domains. • By combining with network abstraction layer functions (NECʼs own ODENOS). Main participants: NTT communications and NEC
Global/Local view Customer-domain Protocol layer Inter-domain & control view & control view & control path restoration
ODENOS (Network virtualization) Mobile backhaul Packet-transport Optical driver ONOS driver driver driver
Leveraging high NMS Optical network performance and scalability domain NMS NMS Mobile backhaul Packet-transport domain domain ONOS OpenFlow domain ONOS ONOS ONOS OpenFlow OpenFlow OpenFlow domain domain domain
29 © NEC Corporation 2015 Transport-SDN 構成(ONS2016)
OpenFlowドメイン3 OpenFlow switch 仮想リンク(mininet内) 物理接続 Mininet3 オプティカルネットワークドメイン PTN 波⻑多重接続 VM OXC VM VM Mobile BackHaul VM VM VM VM
192.168.2.11-14
パケットトランスポート Mininet1 ネットワークドメイン
OpenFlowドメイン2
モバイルバック VM VM ホールドメイン VM VM VM VM VM VM Mininet2 VM VM VM VM VM OpenFlowドメイン1 192.168.1.11-14
192.168.0.11-14
30 © NEC Corporation 2015 デモ まとめ
▌ ONOSのアーキテクチャと内部構造
▌ Intent l Host to Host Intent, Path Intent, Flow Intent
▌ ONOS向きシナリオ例
▌ ユースケース
▌ デモ
32 © NEC Corporation 2015