openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #18530
Re: Quantum Debug
Hello again,
I had some progress now. I followed another guide and now using VLAN+bridge
interface (
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst
)
Now I can ping the instances (after configuring the interface manually
logging via VNC)
- They dont get DHCP service at all. I run udhcpc and it stays in Sending
discover... for ever.
- I cannot ping anything but the instances one to each other. Not the
quantum router (which I think it should be in 10.10.10.1)
Now this is my Quantum configuration in the *cloud controller* node:
root@folsom-cc01:/etc/quantum# cat *dhcp_agent*.ini | grep -v '#'
[DEFAULT]
state_path = /var/lib/quantum
interface_driver = quantum.agent.linux.interface.OVSInterfaceDriver
dhcp_driver = quantum.agent.linux.dhcp.Dnsmasq
use_namespaces = True
root_helper = sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf
root@folsom-cc01:/etc/quantum# cat *l3_agent*.ini | grep -v '#'
[DEFAULT]
debug = True
interface_driver = quantum.agent.linux.interface.OVSInterfaceDriver
auth_url = http://ccontroller:35357/v2.0
auth_region = RegionOne
admin_tenant_name = service
admin_user = quantum
admin_password = password
root_helper = sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf
use_namespaces = True
metadata_ip = 192.168.253.172
root@folsom-cc01:/etc/quantum# cat quantum.conf | grep -v '#'
[DEFAULT]
verbose = True
debug = True
bind_host = 0.0.0.0
bind_port = 9696
core_plugin =
quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2
auth_strategy = keystone
fake_rabbit = False
rabbit_password = password
api_paste_config = /etc/quantum/api-paste.ini
control_exchange = quantum
notification_driver = quantum.openstack.common.notifier.list_notifier
list_notifier_drivers = quantum.openstack.common.notifier.rabbit_notifier
[QUOTAS]
root@folsom-cc01:/etc/quantum# cat plugins/openvswitch/*ovs_quantum_plugin*.ini
| grep -v '#'
[DATABASE]
sql_connection = mysql://quantum:password@ccontroller:3306/quantum
reconnect_interval = 2
reconnect_interval = 2
[OVS]
tenant_network_type=vlan
network_vlan_ranges = physnet1:1:4094
bridge_mappings = physnet1:br-eth1
[AGENT]
polling_interval = 2
root_helper = sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf
Now in the *Compute Node*:
root@folsom-cn1:/var/log/openvswitch# cat /etc/quantum/*quantum*.conf |
grep -v '#'
[DEFAULT]
verbose = True
debug = True
bind_host = 0.0.0.0
bind_port = 9696
core_plugin =
quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2
auth_strategy = keystone
fake_rabbit = False
rabbit_host = ccontroller
rabbit_password = password
api_paste_config = /etc/quantum/api-paste.ini
control_exchange = quantum
notification_driver = quantum.openstack.common.notifier.list_notifier
list_notifier_drivers = quantum.openstack.common.notifier.rabbit_notifier
[QUOTAS]
root@folsom-cn1:/etc/quantum# cat plugins/openvswitch/*ovs_quantum_plugin*.ini
| grep -v '#'
[DATABASE]
sql_connection = mysql://quantum:password@ccontroller:3306/quantum
reconnect_interval = 2
[OVS]
tenant_network_type=vlan
network_vlan_ranges = physnet1:1:4094
bridge_mappings = physnet1:br-eth1
[AGENT]
polling_interval = 2
root_helper = sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf
Some more information:
root@folsom-cn1:/etc/quantum# ovs-vsctl show
ba9aad32-efd0-4891-b78d-feec74ea8b03
Bridge br-int
Port "qvo591594a6-e9"
tag: 1
Interface "qvo591594a6-e9"
Port "qvo8c296e5d-bf"
tag: 1
Interface "qvo8c296e5d-bf"
Port br-int
Interface br-int
type: internal
Port "qvo1b57b973-42"
tag: 1
Interface "qvo1b57b973-42"
Port "qvob0aef54a-03"
tag: 1
Interface "qvob0aef54a-03"
Port "qvo5936a539-a1"
tag: 2
Interface "qvo5936a539-a1"
Port "int-br-eth1"
Interface "int-br-eth1"
Port "qvo1d27e91c-a0"
tag: 1
Interface "qvo1d27e91c-a0"
Bridge "br-eth1"
Port "phy-br-eth1"
Interface "phy-br-eth1"
Port "eth1"
Interface "eth1"
Port "br-eth1"
Interface "br-eth1"
type: internal
ovs_version: "1.4.0+build0"
root@folsom-cc01:/etc/init.d# ovs-vsctl show
4a1a49ba-b6cb-465d-87f1-9d1dbe9c6f81
Bridge "br-eth1"
Port "br-eth1"
Interface "br-eth1"
type: internal
Port "phy-br-eth1"
Interface "phy-br-eth1"
Port "eth1"
Interface "eth1"
Bridge br-int
Port "qr-3c159389-9e"
tag: 1
Interface "qr-3c159389-9e"
type: internal
Port br-int
Interface br-int
type: internal
Port "int-br-eth1"
Interface "int-br-eth1"
Port "tap24284d5b-2b"
tag: 1
Interface "tap24284d5b-2b"
type: internal
Bridge br-ex
Port "qg-42a6ab11-cf"
Interface "qg-42a6ab11-cf"
type: internal
Port br-ex
Interface br-ex
type: internal
Port "eth2"
Interface "eth2"
ovs_version: "1.4.0+build0"
Then I followed this part to create the subnets/routers in Quantum:
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst#12-your-first-vm
Does anyone has any idea?
Kind regards.
On 9 November 2012 22:28, Emilio García <emilio.garcia@xxxxxxxxxxxxxxxx>wrote:
> Hi again,
>
> I won't have access again to the system till Monday so I will test it
> then, but a colleague of mine just told me (he is just trying the same set
> up with similar issues):
>
> when virtual machine is booting on the compute node, on the controller
> node i can see the following:
>
> 22:18:39.500044 IP 10.10.10.2 > 10.10.10.1: GREv0, key=0x1, length 354:
> IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from
> fa:16:3e:d6:1b:12 (oui Unknown), length 300
> 22:18:39.500074 IP 10.10.10.1 > 10.10.10.2: ICMP 10.10.10.1 protocol 47
> port 25944 unreachable, length 382
> 22:18:39.596341 IP 10.10.10.2 > 10.10.10.1: GREv0, key=0x1, length 90:
> IP6 :: > ff02::1:ffd6:1b12: ICMP6, neighbor solicitation, who has
> fe80::f816:3eff:fed6:1b12, length 24
> 22:18:39.596372 IP 10.10.10.1 > 10.10.10.2: ICMP 10.10.10.1 protocol 47
> port 25944 unreachable, length 118
> 22:18:39.936583 IP 10.10.10.2 > 10.10.10.1: GREv0, key=0x1, length 102:
> IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group
> record(s), length 28
>
> 10.10.10.1 - controller node
> 10.10.10.2 - compute node
>
> looks like controller accepts requirest, but doesn't know what to do with
> it
>
> Kind regards.
>
> On 9 November 2012 20:16, Ivan Kolodyazhny <e0ne@xxxxxxxxx> wrote:
>
>> Hello, Emilio.
>>
>> It looks like you use Quantum and Opwn vSwitch plugin wich used network
>> namespaces. Try to pind instance from the router namespace:
>> #
>>
>
>> # ip netnx exec qrouter-1fceeb5c-2792-4b73-b523-d7d55586a1eb ping
>> 10.1.1.20
>>
>> Regards,
>> Ivan Kolodyazhny,
>> Web Developer,
>> http://blog.e0ne.info/,
>> http://notacash.com/,
>> http://kharkivpy.org.ua/
>>
>>
>>
>> On Fri, Nov 9, 2012 at 8:51 PM, Emilio García <
>> emilio.garcia@xxxxxxxxxxxxxxxx> wrote:
>>
>>> Good day everyone,
>>>
>>> I am doing a Folsom install following this guide:
>>> https://github.com/EmilienM/openstack-folsom-guide
>>>
>>> I only have set up the internal network and I can swpan instances but it
>>> doesn't seem like I can connect to them at all, and they cannot find the
>>> metadata host.
>>>
>>> I have 3 interfaces in the cloudcontroller: the management one eth0, the
>>> vm traffic one eth1 and a the external one eth2 which im not using for
>>> anything at the moment.
>>>
>>> The thing is after setting up Quantum in the cloudcontroller I cannot
>>> even ping the compute node in eth1 any more (cc is 10.1.1.10 and cn is
>>> 10.1.1.20).
>>>
>>> My set up was to create a Quantum network, then a subnet (10.1.1.0/24)
>>> and then a router a attach the port to that subnet. I am using Quantum
>>> tunnels too no VLAN.
>>>
>>> Does anyone has any clue? Any recommendantions to debug Quantum? Of
>>> course I cannot ping the instances neither.
>>>
>>> My interfaces are:
>>>
>>> ubuntu@folsom-cc01:~$ ifconfig -a
>>> br-eth1 Link encap:Ethernet HWaddr 00:50:56:a5:1a:40
>>> BROADCAST MULTICAST MTU:1500 Metric:1
>>> RX packets:2938 errors:0 dropped:8 overruns:0 frame:0
>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:0
>>> RX bytes:176290 (176.2 KB) TX bytes:0 (0.0 B)
>>>
>>> br-ex Link encap:Ethernet HWaddr 00:50:56:a5:1a:45
>>> BROADCAST MULTICAST MTU:1500 Metric:1
>>> RX packets:2938 errors:0 dropped:8 overruns:0 frame:0
>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:0
>>> RX bytes:176290 (176.2 KB) TX bytes:0 (0.0 B)
>>>
>>> br-int Link encap:Ethernet HWaddr ba:92:69:aa:06:40
>>> BROADCAST MULTICAST MTU:1500 Metric:1
>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:0
>>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>>>
>>> br-tun Link encap:Ethernet HWaddr 86:ed:48:ab:0e:40
>>> BROADCAST MULTICAST MTU:1500 Metric:1
>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:0
>>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>>>
>>> eth0 Link encap:Ethernet HWaddr 00:50:56:a5:1a:3f
>>> inet addr:192.168.253.172 Bcast:192.168.253.255
>>> Mask:255.255.255.0
>>> inet6 addr: fe80::250:56ff:fea5:1a3f/64 Scope:Link
>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>> RX packets:7926 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:7677 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:1000
>>> RX bytes:3163435 (3.1 MB) TX bytes:4062130 (4.0 MB)
>>>
>>> eth1 Link encap:Ethernet HWaddr 00:50:56:a5:1a:40
>>> inet addr:10.1.1.10 Bcast:10.1.1.255 Mask:255.255.255.0
>>> inet6 addr: fe80::250:56ff:fea5:1a40/64 Scope:Link
>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>> RX packets:2946 errors:0 dropped:4 overruns:0 frame:0
>>> TX packets:2934 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:1000
>>> RX bytes:176780 (176.7 KB) TX bytes:123444 (123.4 KB)
>>>
>>> eth2 Link encap:Ethernet HWaddr 00:50:56:a5:1a:45
>>> inet6 addr: fe80::250:56ff:fea5:1a45/64 Scope:Link
>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>> RX packets:5873 errors:0 dropped:4 overruns:0 frame:0
>>> TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:1000
>>> RX bytes:352390 (352.3 KB) TX bytes:468 (468.0 B)
>>>
>>> lo Link encap:Local Loopback
>>> inet addr:127.0.0.1 Mask:255.0.0.0
>>> inet6 addr: ::1/128 Scope:Host
>>> UP LOOPBACK RUNNING MTU:16436 Metric:1
>>> RX packets:323440 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:323440 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:0
>>> RX bytes:70585630 (70.5 MB) TX bytes:70585630 (70.5 MB)
>>>
>>> And when I try to ping always get:
>>>
>>> ubuntu@folsom-cc01:~$ ping 10.1.1.20
>>> PING 10.1.1.20 (10.1.1.20) 56(84) bytes of data.
>>> From 10.1.1.10 icmp_seq=1 Destination Host Unreachable
>>> From 10.1.1.10 icmp_seq=2 Destination Host Unreachable
>>> From 10.1.1.10 icmp_seq=3 Destination Host Unreachable
>>> ^C
>>> --- 10.1.1.20 ping statistics ---
>>> 6 packets transmitted, 0 received, +3 errors, 100% packet loss, time
>>> 5030ms
>>> pipe 3
>>>
>>> Any help is appreciated.
>>>
>>>
>>> Cloudreach Limited is a limited company registered in England with registered number 06975407
>>>
>>> The above terms reflect a potential business arrangement, are provided solely as a basis for further discussion,
>>> and are not intended to be and do not constitute a legally binding obligation. No legally binding obligations
>>> will be created, implied, or inferred until an agreement in final form is executed in writing by all parties involved.
>>>
>>> This email may be confidential or privileged. If you received this communication by mistake, please don't forward
>>> it to anyone else, please erase all copies and attachments, and please let us know that it has gone to the wrong person.
>>>
>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>
>
> --
>
>
>
>
Cloudreach Limited is a limited company registered in England with registered number 06975407
The above terms reflect a potential business arrangement, are provided solely as a basis for further discussion,
and are not intended to be and do not constitute a legally binding obligation. No legally binding obligations
will be created, implied, or inferred until an agreement in final form is executed in writing by all parties involved.
This email may be confidential or privileged. If you received this communication by mistake, please don't forward
it to anyone else, please erase all copies and attachments, and please let us know that it has gone to the wrong person.
References
