[Yahoo-eng-team] [Bug 1539387] [NEW] l2 agent should subscribe to dvr_update topic only when dvr is enabled

Public bug reported: In OVS Neutron agent, I see that the dvr_update topic is being added to the consumer list irrespective of DVR being enabled or not. Because of this, even though I have disabled DVR in my environment, I still see the agent subscribe and listen on dvr_update topic. It is expect

[Yahoo-eng-team] [Bug 1495628] [NEW] In DHCP agent's enable_dhcp_helper, its good to call safe_configure_dhcp_for_network

k) Its quite possible that we can get exceptions in configure_dhcp_for_network and its better to call its safer counterpart, which takes care of handling any exceptions. ** Affects: neutron Importance: Undecided Assignee: Sudhakar Gariganti (sudhakar-gariganti) Status: In Pr

[Yahoo-eng-team] [Bug 1495592] [NEW] In DHCP agent, resync only for the required networks when sync_state fails

Gariganti (sudhakar-gariganti) Status: New ** Tags: l3-ipam-dhcp ** Changed in: neutron Assignee: (unassigned) => Sudhakar Gariganti (sudhakar-gariganti) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neut

[Yahoo-eng-team] [Bug 1494682] [NEW] l3 agent avoid unnecessary full_sync

Public bug reported: In _process_router_update method, we set full_sync to true a couple of places which can be avoided. There is even a TODO from Carl saying so. # TODO(Carl) Stop this fullsync non-sense. Just retry this # one router by sticking the update at the end of the queue # at a lower

[Yahoo-eng-team] [Bug 1490308] [NEW] In DHCP agent's sync_state, get_active_networks_info RPC times out, when there are large number of networks.

P.S: Increasing the rpc_timeout is definetly an option, but given the possible room of improvement in agent code, I do not want to call that shot already. ** Affects: neutron Importance: Undecided Assignee: Sudhakar Gariganti (sudhakar-gariganti) Status: New ** Tags: l3-ipam

[Yahoo-eng-team] [Bug 1482554] [NEW] skip setting up firewall filters for ports not attached to any security groups

time because of this unnecessary workflow. Same thing applies to agent restart scenario as well. ** Affects: neutron Importance: Undecided Assignee: Sudhakar Gariganti (sudhakar-gariganti) Status: New ** Tags: ml2 securitygroups ** Changed in: neutron Assignee

[Yahoo-eng-team] [Bug 1386643] [NEW] report_state thread should be started only after the ovs agent initialization is finished

issues in the bridge configuration steps, there is no point having sent a report_state with start_flag, where the agent has actually not started/initialized properly. ** Affects: neutron Importance: Undecided Assignee: Sudhakar Gariganti (sudhakar-gariganti) Status: New ** Tags