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 eoghank 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 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
Previous: Answer by louiskang 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
Hi Aaron I did a git pull and tried with this in my stackrc: ENABLED_SERVICES="g-api,g-reg,key,n-api,n-cpu,n-sch,n-vnc,mysql,rabbit,openstackx,q-svc,quantum,q-agt,n-cpu,q-dhcp" Q_PLUGIN=openvswitch I created a network and subnet: quantum net-create private quantum subnet-create b7076534-e1b5-42fc-ac4b-14196fb9f21d 10.0.1.0/24 Then booted up the VM with this: nova boot --image facb609d-5399-4023-808a-bf10fb39e47c --flavor 1 --nic net-id=b7076534-e1b5-42fc-ac4b-14196fb9f21d test From the console log it looks like the VM got an IP but I still cannot ping it: ci-info: lo : 1 127.0.0.1 255.0.0.0 ci-info: eth0 : 1 10.0.1.3 255.255.255.0 fa:16:3e:d3:f2:f1 ci-info: route-0: 0.0.0.0 10.0.1.1 0.0.0.0 eth0 UG ci-info: route-1: 10.0.1.0 0.0.0.0 255.255.255.0 eth0 U cloud-init start running: Fri, 24 Aug 2012 00:22:41 +0000. up 6.52 seconds 2012-08-24 00:22:44,681 - DataSourceEc2.py[WARNING]: 'http://169.254.169.254' failed: url error [timed out] And I still do not see the any gateways. Ifconfig still only shows the tap devices: tap17199918-5d Link encap:Ethernet HWaddr de:c9:18:64:8a:aa inet6 addr: fe80::dcc9:18ff:fe64:8aaa/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:77 errors:0 dropped:0 overruns:0 frame:0 TX packets:35 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:5346 (5.3 KB) TX bytes:3626 (3.6 KB) tap455c4a70-f3 Link encap:Ethernet HWaddr a6:f9:4c:e4:f2:cc inet6 addr: fe80::a4f9:4cff:fee4:f2cc/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:10 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:1836 (1.8 KB) TX bytes:468 (468.0 B) And ovs-vsctl still shows this: 8d3731cf-1ac2-4df8-86e5-47ed0a5106ac Bridge br-int Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tapc0474b52-85" tag: 2 Interface "tapc0474b52-85" type: internal Port br-int Interface br-int type: internal Port "tap196eecae-49" tag: 2 Interface "tap196eecae-49" Port "tap647b6989-d5" tag: 1 Interface "tap647b6989-d5" type: internal 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"

Viewing all articles
Browse latest Browse all 31

Trending Articles