CEWC 2012 Cloud SDN Ethernet and Colt

A network of depth and breadth• High capacity long distance network - 35,000km• Connecting 22 countries, 39 metro networks and >100 cities• 19 (+1) data centres and 18,000 connected buildings• MEF & ONF member2

Colt Data Networks Strategy Current Target Network Architecture Optical Layer Network Architecture Ethernet Layer IP Layer Integrated Eth/IP Layer Integrated Optical IP/Optical Core Core IP/MPLS Ethernet Core Core Intelligent IP Service Edge/ Ethernet Edge Aggreg Edge/Aggreg IPCPE Ethernet CPE Modular Ethernet End-user / DC compute End-user / DC compute 3

Use cases for Ethernet, Cloud and SDN 1 - Flex Managed IT services’ Internet 1 Internet Consumer 2 - Flex “private-wire” connectivity to Data Centre 2 Colt Colt Core Data Centre Network Customer 3 3 – Flex inter-Data Centre bandwidth Other Colt DCs4

Software Defined Networking architecture 2 Application Intelligence Controller 3 1 Compute Instance Data Compute Centre Instance Network Customer (OpenFlow-aware) Network Compute Fabric Instance Compute SDN Use Cases Instance Datacentre Fabric Cloud-centric Network Modular MSP Network Layer Integration Metering and Billing UCC (incl. Service Broker)5

The path towards network and IT programmability Existing / Service Catalog driven order and On-going provisioning of IT and network On-demand application IT and Full integration of network services, Customer Portal driven allocation network and IT service with single for MAC, Service Assurance of IT and network Future services today ent to end control plane Automation, Service Visualization resources and ReportingManual Semi-Automated Automated On-demand Programmability Elasticity for in-life Automation for initial service delivery Automation + Elasticity changes • System driven workflow (with a number of manual • Application driven • Software-driven, end-to- steps) (“dumb” mode) end control plane • Capacity Management • An application aware • Metering and Billing network coupled with network aware applications 6

Ethernet : Universal Access• Transport mechanism of choice in the access / WAN• LAN technology in the DC  Connect the two• How ? • Don’t treat DC as customer premises anymore • End-to-end connectivity, SLA, QoS, etc: technical and commercial service wrap • Openflow/own HW: remember not everybody is GOOG• Don’t forget: It’s also time to stop sell some services, migrate customers and remove technology7

Does the protocol matter ?• The service sure does matter... But to which extend ?• Carrier Ethernet, IPVPN, IP Access ?• Into the DC• Pick on the customer’s behalf (solutions) or let him decide (wholesale/retail)... But let him change it in-life and give him visibility  APIs & open protocols & co• What’s next ?8

Software-Defined Networking• aka Network Programmability• Sounds like a one-way function when networkapplication is as important• It’s not a protocol, it’s about thinking differently about architectures• Builds nicely on our Modular MSP model: future OSS• Isn’t everything already SDN ? So what’s the new model ? Customer-DN, Demand-DN, Application-DN ?9

So what’s the future like ?• Ethernet is the de-facto access technology for WAN and LAN• Monolithic MSP/CE solutions are going to be history soon• Modular, multi-vendor (i.e. IP like) will be the new norm• Openness, APIs, programmability will prevail over hardware capabilities• Not just bandwidth and features will change in-life, also the service type• Managed IT solutions will include and abstract the network10

But also many open questions• What’s the future for hardware: Generic ? Home-made and maintained ?• Cloud had its hype, SDN full in it: what’s left once the dust settles ?• New operating models for well established carriers and people• Management of hybrid networks (e.g. capacity)• And probably many more...11

CEWC 2012 Cloud SDN Ethernet and Colt

by Colt Technology Services on Oct 01, 2012

Accessibility

Upload Details

Usage Rights

Statistics

CEWC 2012 Cloud SDN Ethernet and Colt — Presentation Transcript