yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #47212
[Bug 1552085] Re: Router Interfaces Are Instantiated in Compute Nodes Which do not need them.
Hmmm, I think the nature that's how it should work, isn't it?
If you are connected to a router, my expectation would be that I could
ping all of the routers interfaces (e.g. for test purposes). And what
if another vm on another subnet is spawned on another compute node,
would you expect that this interface is being added on your local
compute node?
I'm not a DVR expert, so setting this bug to opinion to get further
input from other memebers of the DVR team as well.
** Changed in: neutron
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1552085
Title:
Router Interfaces Are Instantiated in Compute Nodes Which do not need
them.
Status in neutron:
Opinion
Bug description:
Pre-Conditions: three node dvr topology created with devstack script
from master branch
step-by-step:
as " source openrc admin admin" (adminstrator)
Dvr routers is created
Three Subnets are attached to it.
Only one vm is instantiated and attach to only one subnet.
Expected Output:
The router is instantiated in the same compute node as the vm with only ONE qr- interface attached to BR-INT bridge
Actual Output:
The router is instantiated on the same compute node as the vm and THREE qr- interfaces are added to the BR-INT bridge.
One for each of the subnets attached to the router.
Problem:
Only one interface is needed on the BR-INT, the one for the subnet the vm is attached to.
The other two are not doing anything except consuming resources.
Version: Mitaka (master on March 1st, 2016)
Ubuntu
Perceived Severity:
probably low. The presence of the other two unused interfaces does not affect functionality
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1552085/+subscriptions
References