ABNO: The IETF approach for carrier SDN

Transcription

1 ABNO: The ITF approach for carrier SDN FIA Athens 2014

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

3 Which architecture fits in a Network Service Provider? SDN CONTROLLR Big black box controlling the network Centralize functionalities to enable automation Define simple standard interfaces 3

4 Vendors position Many vendors are taking into account the SDN approach in their solutions. Most of them are focus on the controllers and the integration between technologies. There are some proposals to extend OpenFlow to optical domains. SDN Controllers OpenFlow xtensions for Optical networks IP+Optical Control Plane Integration 5

5 SDN orchestration approach Current SDN solutions are mainly focused on single domain and monovendor scenarios (e.g data center) SDN architectures for heterogeneous networks with different technologies (IP, MPLS, thernet, optical ) and equipment providers are still under definition. We propose a SDN orchestrator architecture based on the ABNO (Application Based Network Operation) architecture because: ABNO is not a monolithic controller. ABNO is based on existing standard blocks defined within the ITF (PC, ALTO, VNTM ) which could be implemented either in a centralized or distributed way according to network operator requirements. ABNO is specially adapted to multidomain and multivendor networks enabling interoperability between traditional control plane (e.g IP/MPLS, GMPLS) and OpenFlow domains (e.g Data Center). The SDN orchestrator defined in ABNO is not substituting the distributed control plane but interworking with it. 6

6 SDN orchestration approach SDN orchestrator: It takes decisions on 2 network configuration and resources allocation according to service and network optimization criteria Abstracted information about network status Control plane triggering Multilayer and multidomain control plane: It executes network configuration according to SDN orchestrator request 7

7 ABNO architecture NBI Interface to interface applications SBI with three main functionalities: Discover network resources xample: IGP, BGP-LS, etc. Provision the request j: OF, PCP, NetConf, etc. Monitor the network. Not included in the project ALTO Server Topology Module OSS/NMS / Applica on Service Orchestrator Policy Agent VNTM ABNO Controller PC Provisioning Manager I2RS Client OAM Handler Client Network Layer Server Network Layer 8

8 Conclusions and next Steps The new control architecture proposed in this project enables automated and simplified network service provisioning through different network segments (metro, core, data center ) and technologies (IP/MPLS, optical, OpenFlow ) Such automation and simplification could be achieved by applying two complementary measures: 1. Network configuration points minimization by transferring multidomain and multilayer provisioning functionalities from NMS to the control plane. 2. Unified network configuration and orchestration mechanisms enabling end to end network provisioning according to service and network optimization criteria. The network orchestrator proposed in this project is based on the ABNO architecture being defined in the ITF. Three different ABNO use cases are prototyped and demonstrated in the project (one with a field trial) and another use case with remote demos. 9

9 Acknowledgement This work was supported by the FP-7 IDALIST project under grant agreement number

10