ONF SDN Architecture and Standards for Transport Networks

Transcription

1 ONF SDN Architecture and Standards for Transport Networks Control Architecture and Network Modeling I M2H.1 Lyndon Ong Tutorial Talk 21 March 2016, pm pm lyong@ciena.com

2 Agenda 2

3 Open Networking Foundation 3

4 ONF >2017 Interim Board of Directors Google Facebook Microsoft Yahoo Goldman Sachs Deutsche Telekom Verizon NTT Academia SKTelecom AT&T NEC Dan Pitt Executive Director & Staff Guru Parulkar Operator Area Carrier Grade SDN Spec Area Open Transport Services Area Architecture Market Area Open Source SDN ON.LAB Open Datapath Information Modeling Testing and Interop NBI OF-Config CSO Mobile Security PIF 4

5 What s This About? 5

6 ONF Open Transport WG 6

7 Goal: Optical Networks Transformation from closed networks OSS to open networks OSS / Apps Vendor-specific management systems Proprietary OS Vendor X HW Proprietary OS Vendor Y HW Proprietary OS Vendor Z HW open SW open HW SDN Control Infrastructure Virtualized Multi-vendor Multi-domain Network Open APIs Proprietary, vendor-specific silos Complex to operate across vendors and technologies Interoperable networks Open APIs to OSS/Apps End to end orchestration 7

8 SDN Model for Network Control Program Global Network View Network Operating System Network Operating System Forwarding Control Programmable Forwarding Entity Programmable Forwarding Entity DataPlane Programmable Forwarding Entity 8

9 SDN Architecture M2H.1.pdf OFC 2017 OSA

10 OpenFlow: Prototype SDN SouthBound Interface Global control over forwarding behavior Match and drop flows for ACL or set QoS per flow Notify of unknown flows Network Operation Programs OF Central access to network performance monitoring Match and forward flows for Traffic Engineering Match Action Stats OF Client OLS OF Client OLS OF Client OLS OF Client OLS OF Client OLS 10

11 OpenFlow Optical Extensions Port attribute extensions for L0 and L1 Example: Port attributes for ODU Port #1 Port #2 Port #3 ODU-XC Port #4 Port #5 Port #6 Port (Base Layer) Signal Type = OTU4 Port Capabilities Supported Signal Types = ODU0-4 Supported Adaptations (Layer stack) above the base port layer = GFP-F, GFP-T Port Constraints Signal Compatibility Optical Interface Class (Application code/id) Port Transmitted/Received Identifier to support automated discovery/verification ONF TS-022 Optical Transport Protocol Extensions see under Technical Library 11

12 OpenFlow Optical Extensions Match/Action extensions for L0 and L1 connections Example: Match/Action for ODU-XC Port #1 Port #2 Port #3 ODU-XC Port #4 Port #5 Port #6 Match In_port = #1 ODU_Sigtype=ODU1 ODU_SigID={TPN=1, tslen=2,tsmap=[1,0]} In_port = #1 ODU_Sigtype= ODU1 ODU_SigID={TPN=2, tslen=2, tsmap=[0,1]} Action Out_port = #4 Set Field ODU_SigID={TPN=3, tslen=2,tsmap=[0,1]} Out_port = #5 Set Field ODU_SigID={TPN=4, tslen=2,tsmap=[1,0]} 12

13 Status 13

14 Multi-domain Transport SDN Architecture Program Global Network View Network Network Operating Operating System Forwarding Control Programmable Forwarding Entity Programmable Forwarding Entity DataPlane Programmable Forwarding Entity Transport API Child SDN Parent SDN Child SDN Child SDN

15 Previous Research Work A B C A B C NSI Topology 15

16 T-API: -agnostic API framework for Transport Applications ONF TR-527 Transport API Functional Requirements see under Technical Library 16

17 Transport API Project - Overview functional aspects YANG & JSON Topology Service SDN control of Transport networks Connectivity Service Path Computation Service Notification Service Virtual Network Service 17

18 TAPI Process Software Defined Standards in action Use cases describes concepts and API usage Functional Requirements Information Model Collect and Analyze the Purpose-specific Use cases Add, Modify, Clarify Functional Requirements Data Schema Software Prototyping Update Transport API Information Model (UML in Papyrus) Update Transport API Data-Schema (JSON/YANG) ONFOpenTransport Prototype the APIs 18

19 CIM to TAPI mapping M2H.1.pdf OFC 2017 OSA 2017 Network Control Forwarding Node Topology Opaque domain Transparent domain Link Link Logical Termination Point Forwarding Construct NodeEdgePoint ServiceEdgePoint ConnectionEdgePoint Service Connection Requested capability Implemented construct ONF TR-512 Core Information Model v1.2 see under Technical Library 19

20 TAPI Multi-domain Hierarchical Reference Model 1.G 10.G 2.R 9.R TAPI Context-G TAPI Context-R 3.G 11.G 4.R 12.R Multi- Node Edge Point Abstraction & Orchestration 1 Service EndPoint 1.D1 2.D1 TAPI Context-1 5.D1 6.D1 5.D2 6.D2 TAPI Context D2 8.D2 7.D3 8.D3 TAPI Context-3 3.D1 4.D1 9.D3 10.D3 Abstraction & Orchestration Abstraction & Orchestration Abstraction & Orchestration 11.D3 12.D3 G-1 R D D1-4 D1-2 D D D2-2 D D D3-4 D3-2 D G-2 R-2 UNI UNI 3 4 NNI NNI 9 10 UNI UNI G-3 R-3 R-4 G-4 20

21 Range from Abstract to Detailed Views of Topology n A Node aspect of the FD Topology aspect of the FD Observer 01 (Node Edge Point) Link 01.1 (Service End Point) FD (Node/Topology) 01 A.1.1 A.1 A NCD X -> Network Control A B Service Provider retrieves full topology of A A A.4 05 A A.2.1 A.2 A A A.5 04 FD-A appears a Topology of Nodes A.1 - A.5 & & Links between them 03 C n 02.1 Abstract view only aware of Service Endpoints 21

22 Key features of TAPI SDK Technology-agnostic API Framework Modular & Extensible Industry-wide Interoperability Objective SDK components generated using tools for agile prototyping 22

23 Related Industry Activities 23

24 OIF 2016 SDN TAPI Interop Demo M2H.1.pdf OFC 2017 OSA Q71: Demo private read-out events and white paper OFC 2017: Demo public read-out event see OIF Booth on the Exhibition Floor! 24

25 OIF/ONF Multi- Multi-Lab Testing Setup Network Orchestrator Network Orchestrator Network Orchestrator TAPI TAPI TAPI TAPI TAPI TAPI SBI 1 2 Verizon Lab 3 SBI 1 2 Telefonica Lab 3 SBI 1 2 SKTelecom Lab 3 Network Orchestrator Network Orchestrator TAPI TAPI TAPI TAPI Intra-lab testing SBI China Telecom Lab SBI China Unicom Lab Execute Test Plan between Orchestrator/ pairs, validate dataplane actions Inter-lab testing Testing extended using inter-lab control network 25

26 Test Topology Provisioning app Network Orchestrator TAPI TAPI TAPI Network Orchestrator TAPI TAPI Traffgen Traffgen Multi-, Multi-Vendor Vendor s Hierarchical Network Orchestration 26

27 Multi-domain Provisioning with Constraints Provisioning app Network Orchestrator Network Orchestrator Traffgen Traffgen 27

28 Packet/Optical Integration Use Case Network Orchestrator 41 TAPI Service End Point 41 TAPI Node Edge Point (external) Station1 Media Client Station2 Media Server J1 J20 J2 J3 J7 J8 J19 A13 A11 A14 A16 J4 J5 J6 J18 A14 A12 A15 A17 A18 B4 B5 B1 B2 B3 B6 B7 B8 28

29 TAPI Operations Topology API 29

30 TAPI Operations Connectivity API 30

31 TAPI Notification, PCE, Virtual Network 31

32 Some Demo Takeaways 32

33 33 TAPI and ETSI-NFV The target scope in OIF Network controller for the WAN Architectural model: Multi-layered Multi-vendor domains Network Model Hierarchical: E2E/ Network NBI/ SBI: TAPI Network elements in the WAN Optical network Nodes Packet network Nodes ETSI GS NFV-MAN 001 V

34 34 Mapping ETSI-NFV onto OIF/ONF TAPI Testing Network Network Orchestrator Multi- WAN ETSI-NFV 34

35 MEF CANTATA (CUS:BUS) Business Applicatio ns SONATA (BUS:BUS) Business Applicatio ns Customer Application Coordinator LEGATO (BUS:SOF) LEGATO (BUS:SOF) ALLEGRO (CUS:SOF) Service Orchestration Functionality INTERLUDE (SOF:SOF) Service Orchestration Functionality PRESTO (SOF:ICM) PRESTO (SOF:ICM) ONF TAPI Infrastructure Control and Management ADAGIO (ICM:ECM) Infrastructure Control and Management ADAGIO (ICM:ECM) Element Control and Management Element Control and Management Network Infrastructure 35

36 TAPI within LSO Architecture TAPI 36

37 IETF 37

38 TE Topology Model Node and Network TTP TE NODE TE LINK TE NODE TE LINK TE NODE TE LINK TE NODE TE LINK OVERLAY TE LINK TE NODE TE NODE UNDERLAY TE LINK TE LINK TE LINK TE NODE ABSTRACT TE NODE TE NODE 38

39 ACTN (Abstraction and Control of Transport Networks) Model Customer Network CNC CNC CNC VN Traffic Matrix is a set of E2E connectivity (in a simplest form) CMI Multi- Service Coordinator MDSC MPI TAPI? Physical Network PNC PNC PNC PNC PNC SBI 39

40 Summary 40

41 Future Work 41