Juan Fernandez-Palacios Telefónica I+D. Carrier SDN Control plane and SDN convergence in E2E networks

Transcription

1 Juan Fernandez-Palacios Carrier Control plane and convergence in 2 networks

2 Software Defined Networking Network equipment as Black boxes Open interfaces (OpenFlow) for instructing the boxes what to do OPRATING SYSTM FORWARDING HARDWAR OPRATING SYSTM FORWARDING HARDWAR OPRATING SYSTM FORWARDING HARDWAR OPRATING SYSTM FORWARDING HARDWAR Boxes with autonomous behaviour Decisions are taken out of the box OPRATING SYSTM FORWARDING HARDWAR OPRATING SYSTM OPRATING SYSTM FORWARDING HARDWAR FORWARDING HARDWAR OPRATING SYSTM FORWARDING HARDWAR Adapting OSS to manage black boxes Simpler OSS to manage the controller 2

3 Why? Low cost hardware Increased service control scalability Data plane programmability Simpler and flexible OSS 3

4 How to implement? Low cost hardware -> low capacity nodes Increased service control scalability -> service edge nodes Data plane programmability -> single vendor domains Simpler and flexible OSS -> heterogenous and multitechnology scenarios IDALIST scope Small/Mid size Data Centers; accessbackhaul, Large Data Center Single vendor core domains nd to nd OpenFlow, NFV OpenFlow, Optical Switching PC, OpenFlow extensions orchestrator, Network Operating System 4

5 Basic Approach for OpenFlow Domains Application Layer ALTO TD orchestrator OAM Handler CONTROLLR VNTM PC Controller Provisioning Manager OPNFLOW Infrastructure Layer (e.g DataCenter) OpenFlow is based on the concept of actions that are applied to each packet of a given flow (thernet-level addresses, VLAN tags, IP addresses, MPLS labels or transport-level ports). The actions taken by the controller comprise: inserting and removing tags (layer 2), performing routing (layer 3) and also providing differentiated treatment to packets (QoS) 5

6 Main actions to be taken by the controller in 2 networks 1) Discovery of network resources 2) Routing, path computation 3) Automated network orchestration in response to changing network conditions and service requirements 4) Network resources abstraction to application layer 5) QoS control and performance monitoring 6) Multilayer interworking 7) Multidomain/multivendor network resources provisioning through different control domains (e.g OpenFlow DataCenter, OpenFlow MAN, GMPLS optical transport ) 2 networks might be pure OpenFlow based one day, but the migration process will take some time 82nd ITF, Taipei 6

7 IDALIST approach: Modular and standard controller Applications (Internet, CDN, cloud ) Most of these building blocks are on standardization process 4-ALTO 3- orchestrator 5-OAM Handler Controller 1- TD 6-VNTM 2-PC 7-Provisioning Manager OPNFLOW OPNFLOW NTCONF PCP OPNFLOW CLI OpenFLow Data Center OpenFlow MAN Domain IP/MPLS core GMPLS Optical Domains OpenFlow Optical Domain MPLS MAN 7

8 Multiple workflows inside the Orchestrator Cloud Services Live OTT Internet CSO CDN and network optimization Link Provisionin g Network s Multilayer Orchestrator Orchestration mechanisms NTWORK OPRATING SYSTM Provisioning Manager NetConf OpenFlow PCP UNI Physical Network Open Network Operating Systems will enable open orchestration software development 8

9 List of potential topics for future collaboration U-Mexico Cloud Services CSO Live OTT CDN and network optimization Internet Link Provisionin g Network s Multilayer Orchestrator Service and network orchestration mechanisms Orchestration mechanisms NTWORK OPRATING SYSTM Provisioning Manager NetConf OpenFlow PCP UNI Physical Network Open platform for orchestration software development 9

10 10