[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1585520
Title:
Only some specific router or ovs ports which SRI-OV port need to reach
but now can not on the same compute
Status in neutron:
Expired
Bug description:
In some cases, we need to implement that the SRI-OV ports can reach
some specific ovs ports but not all the ovs ports on the same compute
node or the SRI-OV ports can reach the specific router internal ports,
don't need to add all the router ports mac into fdb tables on the same
compute node .
I have seen some code changes and bugs about this problem before. All
solutions are adding the mac of the all ovs ports or router internal
ports into nic fdb tables. I think that the approach is flawed ,and it
would take up and waste the resources of network nic registers. If
there are a lot of ovs ports in the one compute node ,the l2 agent
would add all the mac of ovs ports into fdb table. But because the
number of physical nic registers are limited，some mac which we want to
reach cann't be added into the fdb table . In this case, the SRI-OV
port just can reach some ports which we do not wanted ,and can't reach
the specific ports which wo hope to
In my opinion , adding a port extensions such as
fdb_enable、sriov_enable is more better. CURD operation is very easy
for tenant, and does not need to know the command about linux fdb.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1585520/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
