Quantcast
Channel: Ask OpenStack: Q&A Site for OpenStack Users and Developers - Individual question feed
Viewing all articles
Browse latest Browse all 31

Answer by arosen 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

Next: Answer by slogan-r 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
Previous: Answer by slogan-r 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
$
0
0
Just to confirm did you have q-dhcp in ENABLED_SERVICES? If so I'm not sure why stack.sh isn't starting it for you. Is there an error? screen_it q-dhcp "sudo python $AGENT_DHCP_BINARY --config-file $Q_CONF_FILE --config-file=$Q_DHCP_CONF_FILE"

Viewing all articles
Browse latest Browse all 31

Trending Articles