Ask Your Question
0

How to configure direct public network access with external router and internal DHCP-agent

asked 2013-08-14 15:19:15 -0600

jproulx gravatar image

updated 2013-08-14 15:58:48 -0600

Goal

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.

Current State

My current attempt at this is using the OVS plugin and a vlan based provider network.

On the compute nodes this is working, VMs get on the correct vlan and if I configure an external DHCP server they get addresses and connection (though discovering what address they got is a challenge)

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)

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. But it seems to be the name spaces, as ovs-vswithcd.log contains the following error related to the tap device:

Aug 14 16:45:47|00069|bridge|INFO|created port tap9bc9680d-2a on bridge br-int
Aug 14 16:45:47|00105|netdev_linux|WARN|/sys/class/net/tap9bc9680d-2a/carrier: open failed: No such file or directory
Aug 14 16:45:47|00106|netdev|WARN|failed to get flags for network device tap9bc9680d-2a: No such device
Aug 14 16:45:47|00107|netdev_linux|WARN|ethtool command ETHTOOL_GSET on network device tap9bc9680d-2a failed: No such device
Aug 14 16:45:47|00108|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on tap9bc9680d-2a device failed: No such device
Aug 14 16:45:47|00109|netdev|WARN|failed to get flags for network device tap9bc9680d-2a: No such device
Aug 14 16:45:47|00110|netdev|WARN|failed to retrieve MTU for network device tap9bc9680d-2a: No such device
Aug 14 16:45:47|00127|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap9bc9680d-2a device failed: No such device
Aug 14 16:45:47|00128|netdev_linux|WARN|tap9bc9680d-2a: linux-sys get stats failed 19
Aug 14 16:45:47|00136|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on tap9bc9680d-2a device failed: No such device
Aug 14 16:45:48|00148|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on tap9bc9680d-2a device failed: No such device
Aug 14 16:45:59|00155|netdev|WARN|failed to get flags for network device tap9bc9680d-2a: No such device

Existing Network Setup

  • netblock: 10.10.128.0/18
  • gateway: 10.10.128.1 #on existing routers
  • allocatable range: 10.10.160.0/19
  • vlan tag: 2113

There are existing hosts online in the lower end of the range, including the existing physical hosts

Network Node

Interfaces:

  • bond0: no IP, 2 bonded 10G, multiple trunked vlans
  • bond0.2113: access IP 10.10.128.15
  • tap9bc9680d-2a : virtual interface in dhcp name space

Net Creation:

root@nimbus-0:~# quantum net-create  inet --provider:network_type vlan --provider:physical_network trunk --provider:segmentation_id 2113

root@nimbus-0:~# quantum subnet-create  inet 10.10.128.0/18 --allocation-pool start=10.10.160.0,end=10.10.191.254 --name cloud-net --gateway 10.10.128.1 --dns_nameservers list=true ...
(more)
edit retag flag offensive close merge delete

Comments

Have you tried a non-bonded interface? Was bond0 created using OVS or Linux? Can you provide 'ovs-ofctl dump-flows br-int' and 'ofctl dump-flows bond0-br' and 'ovs-vsctl show' from the netnode.

darragh-oreilly gravatar imagedarragh-oreilly ( 2013-08-14 15:40:45 -0600 )edit

1 answer

Sort by ยป oldest newest most voted
1

answered 2013-08-14 17:06:04 -0600

jproulx gravatar image

Turns out the conflict here is due to the (attempted) multiple use of vlan2113 on the bond0.

bond0.2113 as noted above was the primary IP for the network node (this was configured in the usual linux way not using ovs), so the tagged traffic was (apparently) consumed by that interface.

I'm not sure my analysis is correct but moving the IP to a 1G interface and removing the bond0.2113 device with vconfig made it all go.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

2 followers

Stats

Asked: 2013-08-14 15:19:15 -0600

Seen: 2,682 times

Last updated: Aug 14 '13