yahoo-eng-team team mailing list archive

[ZongKai LI <lzklibj@xxxxxxxxxx>]

Public bug reported:

We can use following steps to migrate a non-dvr env to dvr env.
1) modify related attributes in config files;
2) restart related services,(like neutron-server, neutron-l3-agent, neutron-openvswitch-agent)
3) update router: neutron router-update --distributed=True ROUTER.
You need do steps 1) and 2) on all compute nodes, and do step 3) on controller node.
You can do migration in order:
a) on controller steps 1)+2), on compute nodes steps 1)+2), then on controller step 3). or
b) on controller steps 1)+2)+3), on compute nodes steps 1)+2).
order b) may enter a non-dvr & dvr co-existed case, neutron network will still work.

I build a 1+2 env. A controller and 2 compute nodes, initially it's a
non-dvr env. A router, attached with two subnets. I booted two instances
on these two subnets, two compute nodes.

When I do dvr migration on my env. I find in some case, not all compute
nodes created router netns qrouter-* on. The compute nodes which dvr
enabled but no netns created in migration case, instances on them will
fail to use neutron network.

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1423067

Title:
  migrate non-dvr to dvr case, not all compute nodes created qrouter
  netns

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  We can use following steps to migrate a non-dvr env to dvr env.
  1) modify related attributes in config files;
  2) restart related services,(like neutron-server, neutron-l3-agent, neutron-openvswitch-agent)
  3) update router: neutron router-update --distributed=True ROUTER.
  You need do steps 1) and 2) on all compute nodes, and do step 3) on controller node.
  You can do migration in order:
  a) on controller steps 1)+2), on compute nodes steps 1)+2), then on controller step 3). or
  b) on controller steps 1)+2)+3), on compute nodes steps 1)+2).
  order b) may enter a non-dvr & dvr co-existed case, neutron network will still work.

  I build a 1+2 env. A controller and 2 compute nodes, initially it's a
  non-dvr env. A router, attached with two subnets. I booted two
  instances on these two subnets, two compute nodes.

  When I do dvr migration on my env. I find in some case, not all
  compute nodes created router netns qrouter-* on. The compute nodes
  which dvr enabled but no netns created in migration case, instances on
  them will fail to use neutron network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1423067/+subscriptions