openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #19780
Re: Instance doesn't get an IP (Folsom / Quantum)
Gary,
As I said, I followed that guide...
Can you point me where that guide does not "connect the interface to the
bridge"?
Or, which file should I take a look...?
Maybe /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini within
folsom-compute ?
Tks!
Thiago
On 3 January 2013 08:12, Gary Kotton <gkotton@xxxxxxxxxx> wrote:
> On 01/03/2013 10:57 AM, Martinx - ジェームズ wrote:
>
> Hi Gary!
>
> Thank you for your fast answer!
>
> 1. The plugin described on that guide;
>
> 2.
> quantum-server running on folsom-controller;
> quantum-plugin-openvswitch / quantum-plugin-openvswitch-agent
> installed and/or running within the three nodes;
> quantum-dhcp-agent running on folsom-network;
> quantum-l3-agent running on folsom-network.
>
> 3. Can't find any errors on quantum log files, debug enabled on all
> nodes. What kind of message can I look for?
>
> 4. "ovs-vsctl show" output (no Instance running right now):
>
>
> Can you please look at http://wiki.openstack.org/ConfigureOpenvswitch.
> From what I see below in the ovs output is that it does not look like you
> have connected the interfaces to the bridge.
> Is the tunneling enabled on purpose?
>
> Thanks
> Gary
>
>
> -------
> root@folsom-controller:~# ovs-vsctl show
> 218d7774-104c-4d2d-ae9e-9a8dd9ca2450
> 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"
>
>
> root@folsom-network:~# ovs-vsctl show
> b8b94a53-3294-44ba-855e-002af8fa80ba
> Bridge br-tun
> Port patch-int
> Interface patch-int
> type: patch
> options: {peer=patch-tun}
> Port "gre-2"
> Interface "gre-2"
> type: gre
> options: {in_key=flow, out_key=flow, remote_ip="10.0.0.2"}
> Port br-tun
> Interface br-tun
> type: internal
> Bridge br-ex
> Port "eth2"
> Interface "eth2"
> Port br-ex
> Interface br-ex
> type: internal
> Port "qg-168da5ed-dd"
> Interface "qg-168da5ed-dd"
> type: internal
> Bridge br-int
> Port "tapa0f18fc7-bc"
> tag: 1
> Interface "tapa0f18fc7-bc"
> type: internal
> Port br-int
> Interface br-int
> type: internal
> Port "qr-a8d8fda3-d7"
> tag: 1
> Interface "qr-a8d8fda3-d7"
> type: internal
> Port patch-tun
> Interface patch-tun
> type: patch
> options: {peer=patch-int}
> ovs_version: "1.4.0+build0"
>
>
> root@folsom-compute:~# ovs-vsctl show
> 86ff13f6-960d-48c5-8e03-e8d688364dd0
> Bridge br-tun
> Port patch-int
> Interface patch-int
> type: patch
> options: {peer=patch-tun}
> Port "gre-1"
> Interface "gre-1"
> type: gre
> options: {in_key=flow, out_key=flow,
> remote_ip="10.10.10.1"}
> Port br-tun
> Interface br-tun
> type: internal
> Bridge br-int
> Port patch-tun
> Interface patch-tun
> type: patch
> options: {peer=patch-int}
> Port br-int
> Interface br-int
> type: internal
> ovs_version: "1.4.0+build0"
> -------
>
> I followed that guide word by word. With a few changes (because I found
> errors and missing informations on that guide) between the tries... Always
> with the same result.
>
> BTW, I made a lots of comments on that guide webpage (I am Thiago
> Martins)...
>
> Thank you!
> Thiago
>
> On 3 January 2013 06:38, Gary Kotton <gkotton@xxxxxxxxxx> wrote:
>
>> Hi,
>> In order to be able to help can you please provide the following
>> information:
>> 1. Which plugin are you using? I assume that it is OpenvSwitch from the
>> link :)
>> 2. Are all of the Quantum services running:
>> - quantum-server
>> - quantum-openvswitch-agent
>> - quantum-dhcp-agent
>> 3. Can you please check if there are any messages in quantum log files?
>> 4. Can you also please provide the ovs-vsctl show results (this shows the
>> tap device attached to the ovs)
>> Thanks
>> Gary
>>
>>
>> On 01/03/2013 10:26 AM, Martinx - ジェームズ wrote:
>>
>> Hello!
>>
>> I'm following this guide:
>> http://docs.openstack.org/folsom/basic-install/content/basic-install_intro.html
>>
>> And I'm getting this from my "Instance Log":
>>
>> ----------
>> cloud-init start-local running: Thu, 03 Jan 2013 04:20:52 +0000. up
>> 8.53 seconds
>>
>> no instance data found in start-local
>>
>> cloud-init-nonet waiting 120 seconds for a network device.
>>
>> cloud-init-nonet gave up waiting for a network device.
>>
>> ci-info: lo : 1 127.0.0.1 255.0.0.0 .
>>
>> ci-info: eth0 : 1 . . fa:16:3e:83:06:4f
>>
>> route_info failed
>>
>> Waiting for network configuration...
>>
>> Waiting up to 60 more seconds for network configuration...
>>
>> Booting system without full network configuration...
>> ----------
>>
>> I already tried this guide more than 10 times, always from scratch
>> and everytime I hit this problem.
>>
>> I'm using Ubuntu 12.04 with Ubuntu Cloud Archives enabled.
>>
>> What can I do?
>>
>> Thanks!
>> Thiago
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
>>
>>
>
>
References