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 4 2012 © NEC Corporation 2015 2014/9 2014/12 バージョン毎の⽬目標 3ヶ⽉月毎のバージョンアップ Emu Drake Lab trial & initial deployment at SP networks Cardinal Platform Development Blackbird Avocet Demonstrate Performance, Scale & HA Announce Open Source 5 © NEC Corporation 2015 POC demonstrati on at ONS2015 Grow partners and community Enhancements for CORD deployment Collaborate with other open source projects, like ONF, OPNFV, etc. Real world deployments in R&E networks Community Development ONOS Partner and Collaborator Partners Collaborators 6 © NEC Corporation 2015 ONOSが考えるSoftware-‐‑‒Define Networking とは Control Apps Features Control Plane Config Apps Mgmt Apps SDN Network Operating System Disaggregation Hardware Agent OS Loader Merchant Silicon Closed 7 © NEC Corporation 2015 Whitebox Legacy ONOSが考える望ましいSDNの姿 “REST”, telnet, ssh, … telnet, ssh, … Features 8 SDN対応 Features Control Plane Control Plane Hardware Hardware © NEC Corporation 2015 ONOSアーキテクチャ概観 ▌ SBプロトコル独⽴立立 なNBI Apps Northbound Application Intent Framework, Global Network View, Flow Objectives (policy enforcement, conflict resolution) ▌ 論論理理的に集中した 分散基盤 ▌ NEを抽象化し、 SBプロトコル独⽴立立 なビューを提供 9 © NEC Corporation 2015 Distributed Core (scalability, availability, performance, persistence) Southbound (discover, observe, program, configure) OpenFlow NetConf ... ONOSの構造(概要) 分散コントローラー ▌ 独立したインスタンス Apps ▌ インスタンスを追加削除 がシームレス ▌ スイッチ毎にマスターコ ントローラが異なる ▌ アプリケーションからは1 ONOS Global Network View / State つのコントローラとして 見える ONOS Instance 1 10 © NEC Corporation 2015 ONOS Instance 2 ONOS Instance 3 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 A. デバイスやリンク検知速度 • < 100ms • ONOS part <10ms B. Intent スループット • 150k ops/sec C. Intent の伝搬遅延 • < 50ms D. Flow フループット • 500K to 3M ops/sec 詳しくはWeb上の White Paper参照 12 © NEC Corporation 2015 Apps Northbound - Application Intent Framework (policy enforcement, conflict resolution) B A Flow rule subsystem Distributed Core (scalability, availability, performance, persistence) D Southbound (discover, observe, program, configure) Adapter Adapter ... OpenFlow NetConf ... ONOS向きシナリオ例例 (1/2) ⾃自動化された制御ループ アプリ 13 © NEC Corporation 2015 リアルタイムにTE等々 (e.g., CORD:fabric) ONOS向きシナリオ例例 (2/2) ⾼高頻度度制御、バースト制御 アプリ API公開し、 多数のユーザ要求を 迅速にNEに反映する 必要がある 14 © NEC Corporation 2015 NW全域に渡る グローバル最適化 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 Leveraging carrier-‐‑‒ grade HA and performance to enable fast service setup Service defini+ons Virtual func+on instances XOS (Service Orchestration) ONOS OpenStack OpenVirteX (NW virtualization) 16 PON OLT MACs Virtual infra mgʼ’mt vCPE vCPE vCDN vCPE vOLT vCPE vOLT vCDN vBNG vBNG Commodity Servers, Switches, and Storage © NEC Corporation 2015 ROADM (Core) GPON (Access) Fabric mgʼ’mt & traffic control PON OLT MACs Tenant defini+ons CORD Key Building Blocks 20K-100K subscribers/CO CORD key components-‐ • Commodity hardware • SDN Control Plane (ONOS) • NFVI Orchestra9on (XOS, Openstack) • Open Leaf Spine Fabric • Simple on-‐prem CPE + vCPE • Virtualized Access (PON OLT MAC + vOLT) • Virtualized Func9ons • Virtualized BNG Applications SDN Control Plane ONOS Spine Switches Control NFVI orchestra9on XOS Fabric Leaf Switches Simple Switch ONT Access Link I O I PON OLT O MACs LDAP vBNG vOLT vCPE DHCP Metro Core Link RADIUS Commodity hardware Data Subscriber Home Central Office Re-architected as Datacenter 17 I O © NEC Corporation 2015 17 A closer look at XOS-‐‑‒ Service Orchestration for CORD Customers BNG CDN CG-‐NAT Firewall Residential Customers Service Composi9on PGW XCODE NLA CDN Mobile NFVI Orch-‐XOS VPN WanEx DSA IDS Enterprise Customers Parental Control Subscriber-‐‑‒as-‐‑‒a-‐‑‒ service BNG CGNAT Internet-‐as-‐a-‐service …….. XOS Openstack Nova Keystone vBNG app ONOS Neutron • • • Firewall vCPE Caching/ CDN vBNG CGNAT Commodity Hardware 18 © NEC Corporation 2015 vOLT app DPI vCPE app Service Abstrac9on CDN-‐‑‒as-‐‑‒a-‐‑‒ service Firewall XOS opera9onalizes Openstack XOS is a cloud opera9ng system built using Openstack XOS provides: service abstrac9on and service composi9on Network operators can provision services and let XOS worry about interfacing with Openstack and doing VM mgmt 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 apps to interoperate with BGP routers and forward transit traffic and send/ receive IP traffic between SDN and internet domains Provides redundancy of BGP speakers Internet2 (US) CSIRO (Australia) 20 © NEC Corporation 2015 FIU/AmLight (South America) ONOS Deployments in Progress KREONET/KISTI (Korea) GigaPoP ESnet (US) / AARNET (Australia) BGP peering (15k routes announced) ON.Lab local office network Reactive forwarding 21 Intercontinental deployment (Internet2 , GEANT, GARR, FIU/AMLight, NAP, RedClara, Santiago) 12 universities and research institutes exchange routes. L3 communication without core routers ONOS starting to have a global footprint in R&E networks © 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 BW Calendaring Control Apps Config Apps Implement southbound TL1 providers for multiple vendors, and enhance data model in ONOS Mgmt Apps ONOS Multi-‐‑‒layer path provisioning Packet Network Datacenter 1 Failure detection and rerouting in optical layer Optical Network 23 © NEC Corporation 2015 Datacenter 2 Multi-‐‑‒Layer Network without Converged Control Plane E C Logical Tunnels Full Mesh MPLS A IP IP B IP IP Multiple protection modes (up to 4 times BW) IP IP Routers P1 IP Primary Protected R1 Peak rate provisioning P5 IP IP P4 P2 IP IP Static planning R7 R4 ROADM Light Paths ROADM ROADM ROADM ROADM Lightpaths 24 © NEC Corporation 2015 D P3 R2 ROADMs IP R3 ROADM R5 ROADM R6 Conceptual Solution: Multi-‐‑‒Layer SDN Control BW Calendaring Control Apps Config Apps Mgmt Apps 1. Centralized control of packet and optical 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 Rou9ng Op9cal control (for MPLS network) Segment Rou9ng (for MPLS network) ONOS Cap New SDN Edge Segment Rou9ng Whitebox switches ONOS ONOS Packet Network Whitebox switches Whitebox switches Whitebox switches Op9cal Network Op9cal Network Op9cal control (for MPLS network) Packet Network Packet Network Whitebox switches Op9cal control Drain Whitebox switches Op9cal Network Grow Route Big Flows to op9cal network Cap-‐‑‒Grow-‐‑‒Drain = Bring SDN to backbone without fork lift upgrade Cap Packet-‐‑‒based backbone – donʼ’t grow the legacy backbone of proprietary routers 26 © NEC Corporation 2015 Grow packet edge and op9cal core with SDN control plane and make the best use of packet-‐op9cal technologies Drain the packet-‐based backbone as most traffic transi9ons to new packet edge and op9cal core network 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 Opera9ng System mux demux fiber pass through add/drop WSS controller HAL Hardware transponder 27 Agent OS Whitebox © NEC Corporation 2015 Legacy 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 & control Protocol layer view & control Customer-‐‑‒domain view & control Inter-‐‑‒domain path restoration ODENOS (Network virtualization) Mobile backhaul driver Leveraging high performance and scalability Optical driver NMS NMS Packet-transport domain Mobile backhaul domain OpenFlow domain 29 © NEC Corporation 2015 ONOS driver Optical network domain NMS ONOS Packet-‐‑‒transport driver ONOS OpenFlow domain ONOS ONOS OpenFlow domain OpenFlow domain Transport-‐‑‒SDN 構成(ONS2016) OpenFlow switch PTN OpenFlowドメイン3 仮想リンク(mininet内) 物理理接続 オプティカルネットワークドメイン 波⻑⾧長多重接続 Mininet3 VM VM VM VM VM VM VM OXC Mobile BackHaul 192.168.2.11-‐‑‒14 パケットトランスポート ネットワークドメイン Mininet1 OpenFlowドメイン2 モバイルバック ホールドメイン VM VM VM VM VM OpenFlowドメイン1 192.168.0.11-‐‑‒14 30 © NEC Corporation 2015 VM VM VM VM VM VM VM VM Mininet2 192.168.1.11-‐‑‒14 デモ まとめ ▌ ONOSのアーキテクチャと内部構造 ▌ Intent l Host to Host Intent, Path Intent, Flow Intent ▌ ONOS向きシナリオ例例 ▌ ユースケース ▌ デモ 32 © NEC Corporation 2015
© Copyright 2024 ExpyDoc
