<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Jon:<div><br></div><div>This is just a stab in a dark, but perhaps it's a vlan tag issue that's causing the openvswitch to not forward the packet? What's the vlan tag on those packets that are arriving at band0 on the network node?</div><div><br></div><div>Also, the bond0.2113 looked a little strange to me on this line: <br><div><br></div><div><div>physical_interface_mappings=trunk:bond0,default:bond0.2113</div></div><div><br></div><div>Is there a manually created bond0.2113 vlan device on the network node? I thought openvswitch manages all of the VLANs with neutron, so there's no need to manually create vlan interfaces like this. </div><div><br></div><div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Take care,</div><div><br></div><div>Lorin</div><div>--</div><div>Lorin Hochstein</div><div>Lead Architect - Cloud Services</div><div>Nimbis Services, Inc.</div><div><a href="https://www.nimbisservices.com/">www.nimbisservices.com</a></div><div><br></div></div></span><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline">
</div>
<br><div><div>On Aug 14, 2013, at 12:47 PM, Jonathan Proulx <<a href="mailto:jon@jonproulx.com">jon@jonproulx.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div><div><div><div><div><div><div>Hi All,<br><br></div>My goal is to setup a network using grizzly-quantum on Ubuntu 12.04 (cloud archive) that will allow VMs direct IP (no nat) connection to an existing network and external router but use quantum-dhcp-agent for IPAM so users can easily discover their address assignments.<br>
<br></div>My current attempt at this is using the OVS plugin and a vlan based provider network.<br><br></div>On the compute nodes this is working, VMs get on teh correct vlan and if I configure an external DHCP server they get addresses and connection (though discovering what address they got is a challenge)<br>
<br></div>The requests get to the network controller on bond0 (what I expect) but they don't get to the dhcp interface (ip netns exec qdhcp-0a1d0a27-cffa-4de3-92c5-9d3fd3f2e74d tcpdump -i tap9bc9680d-2a)<br><br></div>
I don't know if this is incorrect bridge setup (which has tripped me up before in ovs land), or the net namespaces which I'm also unfamiliar with.<br><br></div><div>OVS bits<br><br></div><div>the physical network "trunk" is what was specified in network creation, it's an interface with no IP addr and a small pile of tagged vlans<br>
</div><div><br></div>on the computenodes:<br></div># plugin ini<br><div>bridge_mappings = trunk:eth1-br<br><br>root@nova-58:~# ovs-vsctl list-ports eth1-br <br>eth1<br>phy-eth1-br<br>root@nova-58:~# ovs-vsctl list-ports br-int<br>
int-br-eth1<br>int-eth1-br<br>patch-tun<br>tap66012388-3a <- this is the VM <br><br></div><div>on network node:<br></div><div># plugin ini<br>physical_interface_mappings=trunk:bond0,default:bond0.2113<br>network_vlan_ranges = trunk:2112:2114<br>
bridge_mappings=trunk:bond0-br<br><br>root@nimbus-0:~# ovs-vsctl list-ports bond0-br<br>bond0<br>phy-bond0-br<br>root@nimbus-0:~# ovs-vsctl list-ports br-int<br>int-bond0-br<br>patch-tun<br>qr-08ea752e-e0<br>qr-89a1efea-e9<br>
tap6d0145d5-72<br>tap76d1b368-57<br>tap9bc9680d-2a <- this is the interface in the dhcp server namespace for this net<br><br><br></div><div>why aren't the bits getting from bond0 to the dhcp service?<br></div><div>
<br></div><div>Thanks,<br></div><div>-Jon<br></div></div>
_______________________________________________<br>OpenStack-operators mailing list<br><a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators<br></blockquote></div><br></div></div></body></html>