OpenStack Folsom Design Summit

In folsom, Quantum will become core, and our target is that it will become the default model for Networking with OpenStack (existing network managers will likely continue to exist for backward compat). For this to succeed, we'll need at least one fully open source plugin that can be deployed in a manner similar to any of the three modes of nova-network. This will require non-trivial work, as most network related capabilities are being deprecated in Nova. This includes support for: - IPAM integrated with Quantum (port of Melange) - DHCP injection based on IPAM config (work done here by locaweb + nicira) - security groups (port iptables implementation from nova layer) - L3 + NAT implementation (port iptables logic from nova-network) - "provider networks" (i.e., mapping to a specific vlan in the physical network) - provider firewall (port firewall driver from nova virt layer) - multi-host support for L3 + DHCP - VPN (need input from Vish as to whether this is needed). - Floating IPs In many cases this can be helped by lifting existing code from nova-network or the firewall driver in nova's virt layer. This code should be structured as We probably also want to include plans for various improvements to the existing plugins: - removing polling and instead using something like rabbitmq - restructure code to allow better sharing of code across agents. We also need to consider how we might offer a mechanism to migrate nova networking configuration and state to Quantum. Note: we'll also have to think about different virt layers: libvirt is pretty straightforward, but xenserver uses some interesting tricks witha guest VM to do iptables filtering + L3. ESX is obviously another interesting question. (Session lead is dan wendlandt)