Open Source Networking for Cloud Data Centers

Transcription

1 Open Source Networking for Cloud Data Centers Gaetano Borgione Distinguished PLUMgrid April

2 Agenda Open Source Clouds with OpenStack Building Blocks of Cloud Networking Tenant Networks Integration with Physical Assets Integration with Services April

3 Open Source Clouds with OpenStack April

4 OpenStack OpenStack is a cloud management system that controls large pools of compute, storage, and networking resources throughout a datacenter, all managed through a dashboard that gives administrators control while empowering their users to provision resources through a web interface April

5 OpenStack Core Services Compute ("Nova") provides virtual servers upon demand. Compute resources are accessible via APIs for developers building cloud applications and via web interfaces for administrators and users. Network ( Neutron") is a pluggable, scalable and API-driven system for managing networks and IP addresses. Like other aspects of the cloud operating system, it can be used by administrators and users to increase the value of existing datacenter assets. Block Storage ("Cinder") provides persistent block storage to guest VMs. This project was born from code originally in Nova (the nova-volume service described below). Dashboard ("Horizon") provides a modular web-based user interface for all the OpenStack services. April

6 Driving toward a Cloud junction! April

7 Tenant Networks April

8 Per-Tenant Routers with Private Networks - Tenant create Networks, linking them to a Router - Ad-hoc model for Tenant-defined multi-tier applications, with each tier as separate network behind a Router - Multiple Routers make possible overlapping IP space among Tenant subnets - Access to External Network via SNAT / Floating IP April

9 flat networking model VM interfaces are all bridged toward a network adapter Ok for full-trust or single-tenant deployments were segmentation is not needed No multi-tenancy, L2 isolation, overlapping IP address spaces support L3 first-hop routing is either provided by physical networking devices (flat model) or by OpenStack L3 Service (flat-dhcp model) April

10 vlan-based networking model A VLAN per tenant network is used to provide multi-tenancy, L2 isolation, overlapping IP Address spaces support Each VLAN can be either pre-configured on physical switches ***or*** Neutron plugins (provided by switch vendor) can communicate with physical switches to provision it L3 first-hop routing is either provided by physical networking devices or by OpenStack L3 Service April

11 overlay-based networking model multi-tenancy achieved by overlaying MAC-in-IP Tunnels onto the physical switch fabric (underlay, transport network) Encapsulation header (VXLAN, NVGRE, STT) convey tenant network ID to enable full isolation and overlapping IP Address spaces support Software layers to implement routing / switching operations within and across tenant networks April

12 overlay-based networking model (cont.) Neutron plugin talk to SDN Controller via vendor APIs SDN Controller manages vswitches in the Hypervisors PLUMgrid, VMware NSX, Contrail, Nuage, Midokura, 12

13 Integration with Physical Assets April

14 Virtual Topology and Physical Interconnect needs April

15 Virtual to Physical Networking April

16 Integration with Services April

17 Services Adoption in Cloud Data Center 17

18 Service Provisioning steps in OpenStack Provisioning of Virtual Service Form Factor: Virtual Machine or Docker Container Placement Algorithm: RR, Resource Utilization Criteria, Affinity Properties High Availability Service Configuration Service plug-in for solutions supported by vendors Ad-Hoc configuration via Management Interface Service Connectivity SDN solutions to onboard exposed Virtual Service Interface(s) onto Networks provisioned in OpenStack April

19 Wrapping up April

20 Multi-Tenancy + Physical Connectivity + Service Insertion = Cloud Networking April

21 Questions? Gaetano Borgione April