Upload
harley-totty
View
214
Download
0
Tags:
Embed Size (px)
Citation preview
connect • communicate • collaborate
GN3plus
What the network should do for clouds?
Christos Argyropoulos
National Technical University of Athens (NTUA)Institute of Communications & Computer SystemsNetwork Management & Optimal Design Lab (NETMODE)(GN3plus - GRNET 3rd Party)
GN3plus Symposium, October, 2013, Vienna
connect • communicate • collaborate
Someone asked for..
2
• Dynamic provisioning No-human interaction, fast provisioning/deployment
• Elasticity
Resource upscaling/downscaling on demand
• Mobility/MigrationRearrangement of resources
• IsolationSharing of resources in a multi-tenant environment among users (tenants) that are unaware of each other profiles(the ultimate: independence without interference)
connect • communicate • collaborate
Clouds started to deliver..What about networks ?
3
Need for..Enhancements..
• Intra – DC (Data Center) networkingHigher Port densityLower latencies on switching
Programmable Fabric/Flow forwardingSoftware switching inside hypervisors
• Inter – DC networking Layer 2 connectivity Multi-tenancy Resource/Service Mobility Use-cases: load-balancing, disaster recovery
connect • communicate • collaborate
Intra – DCCloud Requirements
4
Cloud Computing Networking
VM provisioning L2 net interface attachment
VM grouping per tenant L2 private networking among VMs/tenant
Scale up to millions VMsScale up to hundreds of thousands
groups
Scale up to hundreds of thousands L2 private nets
VM mobilityVM net profile portability
Net reconstruction across the Net Fabric(beyond legacy scripts)
Clouds generate Requests
connect • communicate • collaborate
Intra – DCNetwork Design Challenges
5
Networking requests Networking challenges
L2 net interface attachment Programmable Access Switches(at least inside hypervisor)
L2 private networking among VMs/tenant Programmable Network Fabric (DC network devices)
Scale up to hundreds of thousands L2 private nets Multi-bit separators/masks
VM net profile portabilityNet reconstruction across the fabric
VM profile binding to Access SwitchesProgrammable Network Fabric
Requests raise Challenges
Port densityLow latency switching High availability etc.
connect • communicate • collaborate
Intra – DCNetwork Design Innovation
6
Networking challenges Innovation
Programmable Access Switches(at least inside hypervisor)
Management Protocol (e.g. NETCONF)Data Modeling Language (e.g. YANG, NDL)
Programmable Network Fabric Flow-forwarding (e.g. OpenFlow)
Multi-bit separators/masks Protocol Stacking *again*(e.g. VXLAN, NVGRE, FabricPath)
VM profile binding to Access SwitchesProgrammable Network Fabric
Cloud & Network Management Plane*Orchestration*
Challenges trigger Innovation
connect • communicate • collaborate
Intra – DCNetwork Design Solutions
7
Innovation Solutions
Management Protocol (e.g. NETCONF)Data Modeling Language (e.g. YANG)
Software Switches(e.g. Open vSwitch/Nexus/JunosV)
Flow-forwarding (e.g. OpenFlow)Flow controllers
(e.g. Open-source Floodlight Controller, NEC ProgrammableFlow)
Protocol Stacking *again*(e.g. VXLAN, NVGRE)
Support for new protocols(e.g. Open vSwitch, Nexus)
Cloud & Network Management Plane*Orchestaration* Unified Control Plane
Innovation generates Solutions
SDN
connect • communicate • collaborate
Inter – DCCloud Requirements
8
Cloud Computing Networking
VM grouping across DCs (single slice across sites) L2 net connectivity across DCs
VM grouping per tenant Keep the L2 isolation across DCs
VM migration (cold)
VM net profile portability (e.g. firewalling, virtual interfaces, MAC mobility, tunnels)
IP mobilityLarge data set move
VM migration (hot)
VM net profile portabilityIP mobility
Large data set moveNet reconstruction across the fabric
Low latency for memory synch
Clouds generate Requests
connect • communicate • collaborate
Inter – DC Network Design Challenges
9
Networking requests Networking challenges
L2 net connectivity across DCs Distributed Network Fabric (state synchronization)
Keep the L2 isolation across DCs Distributed Net Control Plane
VM net profile portabilityIP mobility
Large data set move (VM storage)
Distributed Cloud Control PlaneAvoid traffic trombone
High Bandwidth for heavy data flows
VM net profile portability (hot)IP mobility (hot)
Large data set move (hot)Net reconstruction across the fabric (hot)
Low latency for memory synch (hot)
Distributed Cloud Control PlaneAvoid traffic trombone
Very High Bandwidth for heavy data flowsFlow redirection
Dark Fibers, Short Distances
Requests raise Challenges
connect • communicate • collaborate
Inter – DC Network Design Innovation
10
Networking challenges Innovation
Distributed Network Fabric Seamless overlay, MAC Multi-homing(e.g. VPLS, OTV)
Distributed Net Control Plane Proprietary Net Solutions (e.g. Google Onix)
Distributed Cloud Control Plane (cold)Avoid traffic trombone High Bandwidth for
heavy data flows
Proprietary Cloud Solutions (e.g. EC2)LISP (IP mobility)
Multi-Gig Optical Capacities
Distributed Cloud Control Plane (hot)Avoid traffic trombone
Very High Bandwidth for heavy data flowsFlow redirection
Dark Fibers, Short Distances
Proprietary Cloud Solutions LISP
Multi-Gig Optical CapacitiesDistributed Hierarchies - Flow controllers
Print money!
Requests trigger Innovation
connect • communicate • collaborate
Inter – DC Network Design Innovation
11
Innovation Solutions
Seamless overlay, Multi-homing(e.g. VPLS, OTV)
Proprietary Net Solutions
Proprietary Cloud SolutionsIP mobility (e.g. LISP)
Multi-Gig Optical Capacities
Proprietary Cloud SolutionsIP mobility (e.g. LISP)
Multi-Gig Optical CapacitiesDistributed Hierarchies - Flow controllers
Print money!
Innovation generates Solutions
SDN
OpenDaylightOpen vSwitch
…
connect • communicate • collaborate
Open Networking Foundation (ONF)SDN View
12Source: ONF
Separate Control-Data plane
Network ProgrammabilityDC-manager (and authorized users)
L2 topologies
connect • communicate • collaborate
OpenFlow Protocol/APIFlow Forwarding
13Source: ONF
L2 - L4 flow rules
connect • communicate • collaborate
OpenFlow SwitchManagement & Control
Source: ONF
14
Management interface
Control interfaces
connect • communicate • collaborate
Open vSwitchArchitecture
15
Source: Linux Foundation
connect • communicate • collaborate
Questions?
Thank You !
16