Public bug reported:
I run devstack for dev. I noticed that l2population configuration is not
consistent for lb-agent and ovs-agent.
For lb-agent, l2population is in the section [vxlan], while for ovs-
agent, it is in the section [agent].
Moreover, the devstack is set this configuration in [agent] that causes
lb-agent malfunction.
It is easy to fix it in the devstack, but, in a long run, I think it is
better to deal with it for agent side. I think for both agents, the
common configuration like l2population should be in the [agent] section.
** Affects: neutron
Importance: Undecided
Assignee: Li Ma (nick-ma-z)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Li Ma (nick-ma-z)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1481138
Title:
l2population configuration is inconsistent for different agents
Status in neutron:
New
Bug description:
I run devstack for dev. I noticed that l2population configuration is
not consistent for lb-agent and ovs-agent.
For lb-agent, l2population is in the section [vxlan], while for ovs-
agent, it is in the section [agent].
Moreover, the devstack is set this configuration in [agent] that
causes lb-agent malfunction.
It is easy to fix it in the devstack, but, in a long run, I think it
is better to deal with it for agent side. I think for both agents, the
common configuration like l2population should be in the [agent]
section.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1481138/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
