Networks for Enterprise Applications are Complex…. Image from windowssecurity.com
Why Quantum? Reason #1 On-demand Enterprise-Class Networking• Quantum has Tenants API to: Internet – create multiple private L2 L3 networks L2 – control IP addressing (can use L3 same IP space as existing datacenter deployment) L2 – Connect to an upstream router L3 for external access. L2 – Insert advanced network L3 services: routers, firewalls, VPN, IDS, etc. L2 – Monitor network status
Cloud Stresses the Network….• High-density multi-tenancy – But VLANs limit scale• On-demand provisioning – But traditional network solutions have interfaces designed for manual configuration.• Need to place / move workloads were capacity exists – But network state (e.g., IP address) is tied to a particular location
Why Quantum? #2: Leveraging Advanced Technologies• New networking technologies are emerging to try and tackle these challenges. – Network virtualization – Overlay tunneling: VXLAN, NVGRE, STT – Software-defined Networking (SDN) / OpenFlow – L2 Fabric solutions: FabricPath, Qfabric, etc. – [ insert other solution here ]• Quantum provides a “plugin” mechanism to enable different technologies (more later).
Quantum Architecture Generic OpenStack APIs Operator Selected Backends Compute API KVM Network API OVS Plugin Tenant Tools (GUI, CLI, Storage API Ceph API code)An eco-system of A generic tenant API A “plugin” architecturetools that leverage to create and with different back-endthe Quantum API. configure “virtual “engines” networks”
Basic API Abstractions VM1 VM2 virtual serverNova 10.0.0.2 10.0.0.3 virtual interface (VIF) virtual portQuantum Net1 L2 virtual network 10.0.0.0/24 virtual subnet “virtual networks” and “virtual subnets” are fundamentally multi-tenant, just like virtual servers (e.g., overlapping IPs can be used on different networks).
Quantum Model: Dynamic Network Creation + Association TenantA-VM2 TenantA-VM3 TenantA-VM1 10.0.0.3 126.96.36.199 10.0.0.2 188.8.131.52 Tenant-A Net1 Tenant-A Net2 10.0.0.0/24 184.108.40.206/24External Net220.127.116.11/18 • Tenant can use API to create many networks. • When booting a VM, define which network(s) it should connect to. • Can even plug-in “instances” that provide more advanced network functionality (e.g., routing + NAT).
Quantum API Extensions• Enables innovation in virtual networking. – Tenants can query API to programmatically discover supported extensions. – Overtime, extensions implemented by many plugins can become “core”.• Add properties on top of existing network/port abstractions: – QoS/SLA guarantees / limits – Security Filter Policies – port statistics / netflow• New Services – L3 forwarding, ACLs + NAT (“elastic” or “floating” IPs) – VPN connectivity between cloud and customer site, or another cloud datacenter.
Quantum Architecture Generic OpenStack APIs Operator Selected Backends Compute API KVM Network API OVS plugin Tenant Tools (GUI, CLI, Storage API Ceph API code)An eco-system of A generic tenant API A “plugin” architecturetools that leverage to create and with different back-endthe Quantum API. configure “virtual “engines” networks”
Quantum Architecture (generic)API Clients Quantum Service Backend X Quantum API Tenant Create-net Scripts . Horizon . Plugin GUI . X Create- Orchestration Physical port virtual switch Code Network Nova Compute API Extensions Interfaces from Nova plug into a switch manages by Uniform API the Quantum plugin. for all clients
World’s simplest Quantum Plugin*• API request is dumped into an email, send to your network administrator.• Administrator manually configures network connectivity. * Not recommended for use… ever!
Quantum Plugins Trade-offs• Different back-end “engines” present different trade-offs: – Scalability – Forwarding performance – Hypervisor Compatibility – Network HW Compat (vendor specific? Allow L3 scale-out?) – Manageability / troubleshooting – Advanced Features (exposed as API extensions) – Production testing – High Availability (control & data plane) – Open source vs. Free vs. Paid• Cloud Operators weigh trade-offs, choose a plugin.• Note: Back-end technology hidden behind logical core API – Example: VLANs vs. tunneling
Quantum PluginsOpen source plugins based on Open vSwitch and LinuxBridge exist (works with any hardware switches).The following vendors have publicly stated that they already haveor are developing a Quantum plugin (others exist as well). In somecases, vendor hardware is required.
6 Months Ago…• Incubation release (Essex, April ‘12) – v1 API, basic L2 API abstractions. – Quantum API used by nova-network, but not exposed to tenants. – Plugin architecture to enable choice of back-end technology. – In production at early adopters.
Today• First “core” release (Folsom, Oct. ‘12) – v2 API, with L2 + IP address mgmt (IPAM) – Tenant API with Keystone + Horizon Integration – Updated CLI – Extensions: • L3 “routers” w/floating IPs • “provider networks” mapped to specific VLANs • Tenant quotas • Notifications
What’s going to happen to nova-network?• No forced upgrade in Folsom, or Grizzly.• Existing nova-network stays even with Quantum in core.• Planning an “orderly transition” 1) Freeze on adding new functionality in nova-network (already in effect). 2) Make sure Quantum covers all important nova-network scenarios (target Grizzly) 3) Nova MAY simplifying nova-network code by removing all but basic networking support in subsequent release (possible target H-release)
Should I start using Quantum?• Go back to reasons project was created: – API to build rich network topologies, insert services. – Overcome limitations of traditional networking solutions (e.g., VLANs).• If these are important to your OpenStack deployment, go for it!• Otherwise staying with nova-network is fine.
Taking Quantum for a spin..• Admin Documentation: – http://docs.openstack.org/trunk/openstack- network/admin/content/ – Ubuntu and Red Hat deployments covered. – Please read the entire doc… if something is still unclear, send email to the list• Or use Devstack – http://wiki.openstack.org/QuantumDevstack
Get Hands On!Hands on Quantum Deployment WorkshopThursday 9:00 – 10:30 am @ Manchester E
Two API Deployment Models• Cloud Operator creates networks for tenants – Quantum API is admin only, tenants do not use it. – Similar to nova-network model, but with flexibility around network topology, IP addressing, etc.• Expose API to tenants directly – True “self-service networking”. – Tenants use scripts, CLI, or web GUI to manage networks & subnets.• Can also mix-and-match strategies – Provider creates default network connectivity, tenants can choose to extend.
Single Flat Network Similar to Nova-network Flat or FlatDHCP manager.
Grizzly Quantum: where are we going?• Closing gaps: – Security groups & metadata service compatible with overlapping IPs. – Support L3-forwarding & DHCP on compute nodes (similar to nova “multi_host” flag)• Advanced Services – Load-balancing – VPN
Talks by Quantum Users @ Summit Wed @ 9:30 am Includes production Wed @ 11:00 am Quantum deployments that have been Wed @ 2:40 pm running for 6+ months on Essex! Wed @ 4:10 pm
Key Takeaways• Quantum enables advanced networking in OpenStack: – API to configure rich network topologies. – Plugin architecture for leveraging new network technologies.• With “core” status, expect jump in Quantum production deployments in Folsom.• Quantum team is growing quickly, come join!
Thanks! Questions?Slides available at: http://www.slideshare.net/danwent Dan Wendlandt email@example.com firstname.lastname@example.org OpenStack Quantum Hacker & Project Team Lead twitter - danwendlandt