SDN in CloudStack. Tuesday, October 15, 13

Transcription

1 SDN in CloudStack

2 About me» Hugo Trippaers Freenode: Spark404»

3 CloudStack networking - the five minute version» CloudStack networking Basic, isolation using security groups (L3) Advanced, isolation using network isolation (L2)» SDN was introduced to create isolated networks in Advanced zones» By now it can do much more... (Routing, Firewall, NAT) 3

4 Isolation with VLAN CloudStack takes care off the configuration of hypervisor switches. Who takes care of the networking gear? 4

5 Isolation with VLAN CloudStack takes care off the configuration of hypervisor switches. Who takes care of the networking gear? He does... 5

6 Isolation with Software Defined Networking CloudStack takes care off the configuration of hypervisor switches and L2 networking. Who takes care of the networking gear? 6

7 Isolation with Software Defined Networking CloudStack takes care off the configuration of hypervisor switches and L2 networking. Who takes care of the networking gear? 7

8 Software defined networking - core concepts» Decouples the control plane (what data is going where) from the data plane (how to get data there)» Makes network management easier by abstracting low-level functionality into virtual services. Independent of hardware and/or vendor» Provides a Northbound API Allows administrators to use automated tooling to provision services» Scale? 8

9 Software Defined Networking - advanced» Where can we go if we have a software based network infrastructure. Distributed routing? Integrated security framework? Application controlled networking?» Endless possibilities, it s all software anyway 9

10 SDN in CloudStack» Where is it? 10

11 SDN in CloudStack» Where is it? Implemented in the core of CloudStack. Movable parts configured per plugin. Controlled by existing offering model. 11

12 SDN implementations Isolation DHCP Firewall NAT Security Groups VPC GRE isolation Pre ACS

13 SDN implementations - GRE isolation» Uses the existing implementation of OpenVSwitch in XenServer and XCP Uses the OpenVSwitch GRE tunnels to link OpenVSwitch bridges between hypervisors Entirely controlled by CloudStack GSOC project to add KVM and OpenDaylight» Pros Doesn t require external components» Cons Bandwidth is limited due to lack of offloading Large deployments require a lot of tunnels Limited set of hypervisors supported (XenServer, KVM) 13

14 SDN implementations Isolation DHCP Firewall NAT Security Groups VPC GRE isolation Pre ACS Nicira NVP >=

15 SDN implementations - Nicira NVP» A commercial SDN solution developed by Nicira. Uses both OpenVSwitch and OpenFlow to build overlay tunnels on an existing network.» Pros STT tunnel protocol is optimized for high-bandwidth Includes a gateway to link existing L3 or L2 networks to the virtual switch» Cons Requires custom OpenVSwitch on hypervisors. 15

16 SDN Implementations Isolation DHCP Firewall NAT Security Groups VPC GRE isolation Pre ACS Nicira NVP >= >= 4.1 >= >= 4.1 Big Switch VNS >=

17 SDN implementations - Nicira NVP (>= ACS 4.1)» Nicira NVP plugin is updated to support L3 functionality. With this functionality the existing VRouter can be replaced with a SDN based construct.» Several changes have been made to the VPC setup to support SDN based networks in VPCs. 17

18 SDN implementations - BigSwitch VNS» The Big Switch Networks plugin is a CloudStack SDN plugin using the BigSwitch VNS platform. While BigSwitch VNS is a commercial solution, it is completely based on open standards like OpenFlow» Pros Uses open standards» Cons Requires hypervisors and switches to support OpenFlow 18

19 SDN Implementations Isolation DHCP Firewall NAT Security Groups VPC GRE isolation Pre ACS Nicira NVP >= >= 4.1 >= >= 4.1 Big Switch VNS >= Midokura Midonet >= 4.2 >=4.2 >= 4.2 >= >=4.2 Stratosphere SSP >=

20 SDN implementations - Midokura Midonet» Midokura Midonet is implemented as a CloudStack plugin. It offers a complete set of advanced features like DHCP, L3 Routing and various NAT options.» Pros Complete solution for building standard networks including L3 functions.» Cons Can only be used with the KVM hypervisor. 20

21 SDN implementations - Stratosphere» Stratosphre SSP is an SDN controller that controls or brokers physical and or virtual network devices. Stratosphere SSP will build a vxlan backed overlay network. The plugin makes L2 connectivity service provided by SSP.» Not much information available yet. 21

22 SDN Implementations Isolation DHCP Firewall NAT Security Groups VPC GRE isolation Pre ACS Nicira NVP >= >= 4.1 >= >= 4.1 Big Switch VNS >= Midokura Midonet >= 4.2 >=4.2 >= 4.2 >= >=4.2 Stratosphere SSP >= VXLAN master

23 SDN implementations - VXLAN» Announced at CCC 2013 by Toshiaki Hatano.» Not much information available yet, be sure to watch the recording of the talk. 23

24 SDN Implementations Isolation DHCP Firewall NAT Security Groups VPC GRE isolation Pre ACS Nicira NVP >= >= 4.1 >= >= 4.1 Big Switch VNS >= Midokura Midonet >= 4.2 >=4.2 >= 4.2 >= >=4.2 Stratosphere SSP >= VXLAN master

25 SDN implementations - next steps?» Support for VPC Including private gateways» Common configuration and setup» Security» Configurable on-ramp/off-ramp» IPv6 25

26 SDN in CloudStack - how does it work» Preparing a SDN solution for use requires some configuration work up front 26

27 Preparation - Configure physical network» The physical network defines the type of L2 isolation used. 27

28 Preparation - Setup Providers» The provider is the place to configure the SDN controller» Not used by the GRE tunnels, that is configured using configuration parameters. 28

29 Preparation - Setup network offerings» Connectivity is key» Services define where and how SDN is used in the offering 29

30 SDN in CloudStack - how does it work» Preparing a SDN solution for use requires some configuration work up front» Using the SDN solution is as straight forward as any networking in CloudStack 30

31 Usage - Creating a new network» The role of Network Gurus each guru supports a specific type of network select based on a number of criteria, of which isolation type is only one» Selected guru is stored in the database for this particular network. 31

32 Usage - Creating a new network» The role of Network Elements triggered when ever a new NIC is attached to a network configure devices like firewall, routers, etc..» Elements are selected based on the network offering used to create the network. 32

33 Usage - My first VM» Multiple actions happen at the same time network elements hypervisor resources» The NIC is the linking pin between a VM and the SDN implementation» The hypervisor sets flags to allow the VIF to be found» The network element tells the SDN solution what to look for» Not a generic way of doing things, depends on the SDN in use. 33

34 Usage - Ready 34

35 Thats all there is to it» IRC Freenode: Spark404 35