SDN Landscape and Challenges

Transcription

1 SDN Landscape and Challenges Attila Takacs Manager, Packet Technologies Ericsson Research, Hungary EWSDN European Workshop on Software Defined Networks October 25-26, 2012

2 Ericsson Research, GLOBAl VIEW: Packet Technologies Research Area Montreal Sweden - Kista - Luleå - Linköping - Mölndal - Lindholmen - Lund Helsinki Budapest Beijing Tokyo Aachen Madrid Silicon Valley Pisa Public Ericsson AB Page 2 2

3 Challenge Navigate well The Hype Public Ericsson AB Page 3

4 And this is not even the top of the CURVE Public Ericsson AB Page 4

5 Challenge Address all aspects ONF Architecture & Framework DefinitioN(S) No agreed definition ONF is most authentic +1 SDN is a concept which allows networking behaviour to be defined via software tools that enable easy modification as opposed to behaviour that is fixed by the design of networking equipment. Some recurring components Decoupling control and data plane aka split architecture Centralized controller Programmability and APIs Open interfaces External applications Virtualization Public Ericsson AB Page 5

6 Challenge Functions of the SDN controller vs. NMS Mapping SDN Programming Customization Box SDK Scripting Controller SW Split Architecture Speed Software Defined Networking Blurred boundary NMS/OSS 3 rd party Apps SON APIs Automation Public Ericsson AB Page 6 On-device distributed Network-wide centralized

7 technology evolution Model Subscriber aware forwarding/processing Switching/routing Gap IP Edge Aggregation & Metro Transport Data Center Networking Time Public Ericsson AB Page 7 Illustration

8 Challenge Will SDN indeed transform the carrier segment? technology evolution Model Complex Complex edge edge processing processing and and various various appliances appliances Simple Simple transport transport switches switches and and P routers routers Subscriber aware forwarding/processing Switching/routing IP Edge Aggregation & Metro Transport Data Center Networking SDN Time Public Ericsson AB Page 8 Illustration

9 Challenge Will we have one controller platform for all these? Application Areas MOBILE Virtualization of aggregation network Network support for cloud cloud / data center RESIDENTIAL Home Gateway control ENTERPRISE Multi-layer packet & optical transport Policy-based flow steering at edge Public Ericsson AB Page 9

10 Challenge Will new open-source initiatives get industry traction? Controller Universe Open source controllers NOX/POX Trema Beacon Floodlight Maestro Ryu FlowER Mirage Jaxon Single purpose controllers SNAC RouteFlow FlowVisor OpenRoads FlowScale Hedera NDDI/OESS Commercial controllers ONIX Helios ProgrammableFlow CPlane OpenTransit others Public Ericsson AB Page 10 Not a complete list!

11 Challenge Right level of split which functions should remain distributed? Split Architecture Smart CP CP CP FW Thin CP O&M FW FW Connectivity check 50ms protection Control network maintenance sort of Hybrid Public Ericsson AB Page 11

12 Challenge Tools, languages, components, chipsets Programmability OSS/BSS How to utilize SDN for new services Where/what is the NorthBound API? Smart CP Network abstraction model? Generic Controller or use-case specific? Reusability of components? Thin CP O&M FW DP programmability? How much flexibility is needed? OF Future? Can we go with generic chipsets? Public Ericsson AB Page 12

13 Summary It is not just virtualization Split between CP and DP: OAM and thin control layer How we program the network and what flexibility is needed Both controller and forwarding sides Need a migration strategy From legacy to SDN and to interwork with legacy Align controller initiatives to leverage scale Need experience from live network trials SDN fits best to DevOps model Public Ericsson AB Page 13

14 Public Ericsson AB Page 14