openstack team mailing list archive

[Ilkka Tengvall <ilkka.tengvall@xxxxxxxxxxxx>]

Hi

could someone please explain how to get traffic flowing correctly with 
quantum? We are loosing traffic from quantum-server host back to guest 
network. Guest ping works towards the host, but reply doesn't get sent. 
Guests can also make traffic out of the cloud.

This page tells to setup route back to guest network from metadata server:

http://docs.openstack.org/folsom/openstack-network/admin/content/adv_cfg_l3_agent_metadata.html

The problem is that the instruction on the above page will not work. 
Quantum uses namespaces to set nat rules for the router on 
quantum-server host. The host itself doesn't have ip in the guest 
network, or public network. Thus it fails setting up a route to quantum 
gateway, since the host doesn't have ip in that network in default 
namespace.

We have setup the provider network model using existing vlans according 
to instructions. The main host is running quantum-server, 
metadata-server, l3agent and actually almost every piece of the 
openstack. The other node has only nova-compute and 
quantum-linux-bridge-plugin.

host1: 10.1.1.21/24, vlan1
   |
   |
host1: quantum router gw: 10.1.2.7/25, vlan2
host1: quantum router port: 10.1.3.1/24, vlan3
   |
   |
guest network 10.1.3.0/24, vlan3

So how should the route back to guest network be arranged?
1) adding ip to host into vlan3 guest network
2) using external router (default gw) that routes traffic back to guest 
network outside of openstack
3) somehow adding ip to host into correct tap interface?
4) <insert correct answer here :)>

Obviously the guide is missing some crucial part. What might it be?

BR,

 Ilkka Tengvall