Ask Your Question
1

Openstack Mitaka configuring DVR

asked 2017-03-10 11:52:38 -0500

gustavo gravatar image

updated 2017-03-13 04:24:02 -0500

Hi all,

I've followed the Open vSwitch High availably using DVR guide (https://docs.openstack.org/ocata/networking-guide/deploy-ovs-ha-dvr.html#deploy-ovs-ha-dvr (https://docs.openstack.org/ocata/netw...)) At the point "Verify network operations" they say "On each compute node, verify creation of a qrouter namespace with the same ID." but in my case the qrouter is created in the network node and in only one of the compute node, is that normal, is there an error in the documentation?

It's very what is happening with the router creation:

First of all, my cluster is a kvm virtualised cluster 1 controller/network node and 2 compute node.

when I create the first router and attach a network to it the situation is as follow:

a.- controller/network node

#> ip netns

Output:

snat-4f32a82f-ed71-4b54-b0df-b756d56683bd
qrouter-4f32a82f-ed71-4b54-b0df-b756d56683bd

b.- compute0

#> ip netns

Output:

none

c.- compute1

#> ip netns

Output:

qrouter-4f32a82f-ed71-4b54-b0df-b756d56683bd
qdhcp-94928584-c08a-4b26-a55e-8cc3368796fc

Then I've created a second router and attach another network to it the situation become as follow:

a.- controller/network node

#> ip netns

Output:

snat-99cd0074-bd08-4026-9523-8f375a062d23
qrouter-99cd0074-bd08-4026-9523-8f375a062d23
snat-4f32a82f-ed71-4b54-b0df-b756d56683bd
qrouter-4f32a82f-ed71-4b54-b0df-b756d56683bd

b.- compute0

#> ip netns

Output:

qrouter-99cd0074-bd08-4026-9523-8f375a062d23
qdhcp-d2a62d51-18e0-423c-865f-cf5b6b9be85c

c.- compute1

#> ip netns

Output:

qrouter-4f32a82f-ed71-4b54-b0df-b756d56683bd
qdhcp-94928584-c08a-4b26-a55e-8cc3368796fc

This time the router was created in the controller/network node and in the compute0 node, so the first router was created in the controller/network node and in the compute1 node, the second router was created in the controller/network node and in the compute0 node.

Thanks.

edit retag flag offensive close merge delete

Comments

Your link is for Ocata, but it should also work for Mitaka. AFAIK, the qrouter namespace must be on all compute nodes. Check the config again, restart the services, check the Neutron logs.

Bernd Bausch gravatar imageBernd Bausch ( 2017-03-11 17:09:41 -0500 )edit

I think it is normal. qrouter namespace is created at where it's port(connected to router) exists. you would better to see what happen when you create more vms.

kiseok7 gravatar imagekiseok7 ( 2017-03-14 05:22:34 -0500 )edit

When create a router, the qrouter namespace is created only on the network node, then when I attach a network to the router the qrouter namespace is created on the compute node, but at this point the documentation says the qrouter will be created on all compute nodes in my case this is not true.

gustavo gravatar imagegustavo ( 2017-03-14 08:58:14 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2017-03-16 08:23:31 -0500

Vinoth gravatar image

Try creating VMs in all the compute node. AFAIK, Neutron will create the router namespace only after creating the PORT. Even in the network node, router namespaces will be created only after adding port (GW or Interface) to the router.

edit flag offensive delete link more

Comments

Yes you're right, but the port is created just after a network is added to the router, and as I said before, in my virtual cluster the qrouter namespace is created in only one compute node not in all as documentation says. then if I launch an instance the router namespace is created if not exist yet

gustavo gravatar imagegustavo ( 2017-03-17 03:18:46 -0500 )edit

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

1 follower

Stats

Asked: 2017-03-10 11:52:38 -0500

Seen: 195 times

Last updated: Mar 16 '17