1. connect communicate collaborate GN3plus What the network should do for clouds? Christos Argyropoulos National Technical University of Athens (NTUA) Institute of Communications & Computer Systems Network Management & Optimal Design Lab (NETMODE) (GN3plus - GRNET 3 rd Party) GN3plus Symposium, October, 2013, Vienna

2. connect communicate collaborate Someone asked for.. 1 Dynamic provisioning No-human interaction, fast provisioning/deployment Elasticity Resource upscaling/downscaling on demand Mobility/Migration Rearrangement of resources Isolation Sharing of resources in a multi-tenant environment among users (tenants) that are unaware of each other profiles (the ultimate: independence without interference)

3. connect communicate collaborate Clouds started to deliver.. What about networks ? 2 Need for.. Enhancements.. Intra – DC (Data Center) networking Higher Port density Lower latencies on switching Programmable Fabric/Flow forwarding Software switching inside hypervisors Inter – DC networking Layer 2 connectivity Multi-tenancy Resource/Service Mobility Use-cases: load-balancing, disaster recovery

4. connect communicate collaborate Intra – DC Cloud Requirements 3 Cloud ComputingNetworking VM provisioningL2 net interface attachment VM grouping per tenantL2 private networking among VMs/tenant Scale up to millions VMs Scale up to hundreds of thousands groups Scale up to hundreds of thousands L2 private nets VM mobility VM net profile portability Net reconstruction across the Net Fabric (beyond legacy scripts) Clouds generate Requests

5. connect communicate collaborate Intra – DC Network Design Challenges 4 Networking requestsNetworking 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 portability Net reconstruction across the fabric VM profile binding to Access Switches Programmable Network Fabric Requests raise Challenges Port density Low latency switching High availability etc.

6. connect communicate collaborate Intra – DC Network Design Innovation 5 Networking challengesInnovation Programmable Access Switches (at least inside hypervisor) Management Protocol (e.g. NETCONF) Data Modeling Language (e.g. YANG, NDL) Programmable Network FabricFlow-forwarding (e.g. OpenFlow) Multi-bit separators/masks Protocol Stacking *again* (e.g. VXLAN, NVGRE, FabricPath) VM profile binding to Access Switches Programmable Network Fabric Cloud & Network Management Plane *Orchestration* Challenges trigger Innovation

7. connect communicate collaborate Intra – DC Network Design Solutions 6 InnovationSolutions 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

8. connect communicate collaborate Inter – DC Cloud Requirements 7 Cloud ComputingNetworking VM grouping across DCs (single slice across sites) L2 net connectivity across DCs VM grouping per tenantKeep the L2 isolation across DCs VM migration (cold) VM net profile portability (e.g. firewalling, virtual interfaces, MAC mobility, tunnels) IP mobility Large data set move VM migration (hot) VM net profile portability IP mobility Large data set move Net reconstruction across the fabric Low latency for memory synch Clouds generate Requests

9. connect communicate collaborate Inter – DC Network Design Challenges 8 Networking requestsNetworking challenges L2 net connectivity across DCs Distributed Network Fabric (state synchronization) Keep the L2 isolation across DCsDistributed Net Control Plane VM net profile portability IP mobility Large data set move (VM storage) Distributed Cloud Control Plane Avoid 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 Plane Avoid traffic trombone Very High Bandwidth for heavy data flows Flow redirection Dark Fibers, Short Distances Requests raise Challenges

10. connect communicate collaborate Inter – DC Network Design Innovation 9 Networking challengesInnovation 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 flows Flow redirection Dark Fibers, Short Distances Proprietary Cloud Solutions LISP Multi-Gig Optical Capacities Distributed Hierarchies - Flow controllers Print money! Requests trigger Innovation

11. connect communicate collaborate Inter – DC Network Design Innovation 10 InnovationSolutions Seamless overlay, Multi-homing (e.g. VPLS, OTV) Proprietary Net Solutions Proprietary Cloud Solutions IP mobility (e.g. LISP) Multi-Gig Optical Capacities Proprietary Cloud Solutions IP mobility (e.g. LISP) Multi-Gig Optical Capacities Distributed Hierarchies - Flow controllers Print money! Innovation generates Solutions SDN OpenDaylight Open vSwitch …

12. connect communicate collaborate Open Networking Foundation (ONF) SDN View 11 Source: ONF Separate Control-Data plane Network Programmability DC-manager (and authorized users) L2 topologies

13. connect communicate collaborate OpenFlow Protocol/API Flow Forwarding 12 Source: ONF L2 - L4 flow rules

14. connect communicate collaborate OpenFlow Switch Management & Control Source: ONF 13 Management interface Control interfaces

15. connect communicate collaborate Open vSwitch Architecture 14 Source: Linux Foundation

16. connect communicate collaborate Questions? Thank You ! 15