Answer by danwent for I am trying to run an all-in-one using stack.sh with the latest (folsom3 and master) branches of Quantum on KVM but the gateway interface does not get created and as a result VM's do not get an IP. I've updated the install to include the steps mentioned here http://wiki.openstack.org/RunningQuantumV2Api (http://wiki.openstack.org/RunningQuan...) and here http://wiki.openstack.org/QuantumDevstack (http://wiki.openstack.org/QuantumDevs...) but never get a gateway interface after creating a network and subnet and spinning up a VM. This is what ovs-vsctl displays (after creating a network and subnet and spinning up a VM: stack@esg-dell-c4-s11:~/devstack$ sudo ovs-vsctl show 5dab4e1c-89c4-421e-a737-03b338eddc1a Bridge br-int Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tap73f2ee73-79" tag: 1 Interface "tap73f2ee73-79" type: internal Port "tapd425d955-15" tag: 2 Interface "tapd425d955-15" type: internal Port br-int Interface br-int type: internal Port "tapc46b72b3-b3" tag: 2 Interface "tapc46b72b3-b3" Bridge br-tun Port patch-int Interface patch-int type: patch options: {peer=patch-tun} Port br-tun Interface br-tun type: internal ovs_version: "1.4.0+build0" Are there any additional steps that need to be run to make this work with the V2 Quantum API? Eoghan

There's some confusion here: 1) unlike nova-network, quantum DHCP does not use the gateway IP address of the subnet. Thus, the lack of a tap device with the gateway IP does not mean that the DHCP server is not running. In fact, by default, quantum runs DHCP in its own isolated network namespace, so you would not see the IP address of the DHCP server from the main test host. 2) The actual gateway is implemented using the quantum-l3-agent, which just landed after F-3. Devstack support for this is still under review (should merge within a few days). The quantum-l3-agent uses namespaces as well though, so by default, you wouldn't see the .1 IP address using ifconfig even using L3 is in use.