Public bug reported: In neutron, when binding the port, the l2 mechanism agent driver will try to bind the port to the agent which it thinks is "alive". The current L2 agent in neutron will periodically report its health status to neutron-server, this health information is stored into the neutron DB table agent. So the determination of whether the agent is "alive" or not is depending on the timestamp of the periodical report.
In opendaylight case(i.e. networking-odl), there is no l2 agent at all, and opendaylight can find the host status itself and notify networking- odl through websocket. So there is no need to periodically report from networking-odl to neutron about the health status. We need to extend the current agent health status mechanism to support those kind of agent-less situation. i.e. extend the determination of whether the agent is "alive" or not to not based on timestamp of the report in the above agentless cases. ** Affects: neutron Importance: Undecided Status: New ** Tags: rfe -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1677496 Title: [RFE] extent agent health report mechanism to support agentless situation Status in neutron: New Bug description: In neutron, when binding the port, the l2 mechanism agent driver will try to bind the port to the agent which it thinks is "alive". The current L2 agent in neutron will periodically report its health status to neutron-server, this health information is stored into the neutron DB table agent. So the determination of whether the agent is "alive" or not is depending on the timestamp of the periodical report. In opendaylight case(i.e. networking-odl), there is no l2 agent at all, and opendaylight can find the host status itself and notify networking-odl through websocket. So there is no need to periodically report from networking-odl to neutron about the health status. We need to extend the current agent health status mechanism to support those kind of agent-less situation. i.e. extend the determination of whether the agent is "alive" or not to not based on timestamp of the report in the above agentless cases. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1677496/+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