aryantaheri's profile - activity

2016-05-25 02:35:46 -0500 received badge  Famous Question (source)
2016-01-11 06:54:13 -0500 received badge  Notable Question (source)
2014-09-22 05:53:12 -0500 received badge  Popular Question (source)
2012-11-29 18:47:35 -0500 answered a question 3 nodes are involved: controller, network gateway, compute node. New instances are not communicating at all, no ip addresses.

Dan,

It was not about ICMP, or SSH. The VM didn't get an IP address, DHCP requests were sent, I don't remember how far they got, but the network gateway didn't receive them.

I may change it back and check out how far they get.

2012-11-29 15:38:14 -0500 answered a question 3 nodes are involved: controller, network gateway, compute node. New instances are not communicating at all, no ip addresses.

Thanks Rabi Mishra, that solved my question.

2012-11-29 15:37:55 -0500 answered a question 3 nodes are involved: controller, network gateway, compute node. New instances are not communicating at all, no ip addresses.

Rabi, Thank you

It was extremely strange, changing the "libvirt_vif_driver" to "nova.virt.libvirt.vif.LibvirtOpenVswitchVirtualPortDriver" solved the problem.

--Aryan

2012-11-22 09:29:47 -0500 answered a question 3 nodes are involved: controller, network gateway, compute node. New instances are not communicating at all, no ip addresses.

Well done, I'll check it out.

Just a terminology question, by "trunk" you mean Cisco trunking, not HP trunking? So in HP term, you've tagged those ports, or just left them untouched?

Thanks Aryan

2012-11-22 08:14:30 -0500 answered a question 3 nodes are involved: controller, network gateway, compute node. New instances are not communicating at all, no ip addresses.

Rabi,

Not yet, I'll continue working on it next week. I'll update the question in case of any success.

2012-11-08 16:21:07 -0500 answered a question 3 nodes are involved: controller, network gateway, compute node. New instances are not communicating at all, no ip addresses.

The new configuration is almost the same as previous one. No success yet.

quantum net-list quantum router-list quantum port-list -c id -c fixed_ips -c device_owner output: http://paste.openstack.org/show/25016/

[Network Gateway]

ovs-vsctl show

http://paste.openstack.org/show/25017/

ip netns list

http://paste.openstack.org/show/25018/

ip netns exec qdhcp-e66b8a22-daff-4850-9656-282bee68819d ifconfig

http://paste.openstack.org/show/25019/

[Compute Node]

ovs-vsctl show

http://paste.openstack.org/show/25021/

If I assign the VM's IP manually (10.10.11.4), VM can retrieve the mac address for 10.10.11.2. Now when I ping there is no reply, BUT tcpdump output on both sides show something different !!!

From network gateway to the vm: http://paste.openstack.org/show/25035/ From vm to the network gateway: http://paste.openstack.org/show/25036/

One more thing which may help: I specified vlans from 200 to 250 in the config file. The vlan_allocation table confirms that. But the tag field in "ovs-vsctl show" output shows tag 1. This should not be true. (Using HP ProCurve 2910al-48g, corresponding ports are also on the DEFAULT_VLAN 1, in addition to 200-250)

Thanks.

2012-11-08 08:17:49 -0500 answered a question 3 nodes are involved: controller, network gateway, compute node. New instances are not communicating at all, no ip addresses.

Dan,

Thank you for the feedback.

Yes, I used "Per-tenant Routers with Private Networks".

Unfortunately, I started it from scratch yesterday. But still I have the DB dump: http://paste.openstack.org/show/24956/

I'll come back to you with more information, when the new configuration is in place.

Cheers.

2012-11-06 15:35:04 -0500 asked a question 3 nodes are involved: controller, network gateway, compute node. New instances are not communicating at all, no ip addresses.

Seems something terribly wrong, but before starting from scratch it would be nice if someone give me some hints :)

Previously everything was working with nova-network (FlatDHCP) on the controller node.

Now 3 nodes are involved: controller, network gateway, compute node. New instances are not communicating at all, no ip addresses.

  • Each node has two interfaces, eth0: management, eth1: data

  • Namespace is not disabled

Controller: services: quantum-server, nova-* (but not nova-network), openvswitch-switch ifconfig: http://pastebin.com/8gvGAQLd nova.conf: http://pastebin.com/TzNpMR56 ovs-vsctl show: http://pastebin.com/xrD5u1hX quantum.conf: http://pastebin.com/S9YSKCZ5 ovs_quantum_plugin.ini: http://pastebin.com/KciZ4bin [LOGS] quantum-server.log: http://paste.openstack.org/show/24617/

Network Gateway: services: quantum-l3-agent, quantum-dhcp-agent, quantum-plugin-openvswitch-agent, openvswitch-switch dhcp_agent.ini: http://pastebin.com/2pWVSqqE l3_agent.ini: http://pastebin.com/jNTbQUwG ovs_quantum_plugin.ini: http://pastebin.com/r1gPrXLF ovs-vsctl show: http://pastebin.com/Wuh9r8B7 (and here we go for the strange output without any gw-xxx interface. Note: I created two networks)

This one has only two NICs, so I haven't assigned any interface for external network. It should still work? [LOGS] dhcp-agent.log: http://paste.openstack.org/show/24609/ openvswitch-agent.log: http://paste.openstack.org/show/24613/

Compute Node: services: nova-compute, nova-api-metadata, quantum-plugin-openvswitch-agent ovs-vsctl show: http://pastebin.com/qd6kfNpJ ovs_quantum_plugin.ini: http://pastebin.com/rZVwSxf2 [LOGS] openvswitch-agent.log: http://paste.openstack.org/show/24616/