cewc 2012 cloud sdn ethernet and colt
DESCRIPTION
Presentation from Nicolas Fischbach on where Cloud and SDN will take Carrier Ethernet.TRANSCRIPT
© 2012 Colt Telecom Group Limited. All rights reserved.
Where will Cloud and SDNtake Carrier EthernetNicolas FischbachDirector, Network & Platform Strategy and Architecture
2
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 member
3
Colt Data Networks Strategy
IntegratedIP/Optical
Core
ModularEthernet
OpticalCore
IP/MPLSCore
IPEdge/
AggregEthernet
Edge/AggregIP
CPE EthernetCPE
Optical Layer
Ethernet Layer
IP LayerIntegrated Eth/IP Layer
EthernetCore
End-user / DC computeEnd-user / DC compute
CurrentNetwork Architecture
Target Network Architecture
IntelligentService
Edge
4
Use cases for Ethernet, Cloud and SDN
Colt CoreNetwork
Customer
Consumer
ColtData Centre
Internet
Other Colt DCs
1
2
3
1 - Flex Managed IT services’ Internet
2 - Flex “private-wire” connectivity to Data Centre
3 – Flex inter-Data Centre bandwidth
5
Software Defined Networking architecture
Customer Network(OpenFlow-aware)
DataCentre
NetworkFabric
Controller
ApplicationIntelligence
ComputeInstance
ComputeInstance
ComputeInstance
ComputeInstance
1
2
3
Metering and Billing
SDN Use Cases
Datacentre Fabric
Cloud-centric Network
Modular MSP
Network Layer Integration
UCC (incl. Service Broker)
6
The path towards network and IT programmability
Manual Semi-Automated Automated On-demand Programmability
Service Catalog driven order and provisioning of IT and network
services, Customer Portal for MAC, Service Assurance
Automation, Service Visualizationand Reporting
On-demand applicationdriven allocation of IT and network
resources
Full integration of networkand IT service with singleent to end control plane
• System driven workflow (with a number of manual steps)
• Capacity Management• Metering and Billing
• Application driven (“dumb” mode)
• Software-driven, end-to-end control plane
• An application aware network coupled with network aware applications
Automation for initial service deliveryElasticity for in-life
changesAutomation + Elasticity
IT andnetwork
services today
Existing /On-going
Future
7
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 technology
8
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 ?
9
Software-Defined Networking
• aka Network Programmability
• Sounds like a one-way function when networkapplication 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 ?
10
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 network
11
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...
