Public bug reported: When either end of the Arista ML2 driver reloads (Opestack controller running Neutron or Arista EOS), a full sync of DB state between the Neutron DB and EOS State is required to ensure that all tenant networks and ports are appropriately configured on the Arista Hardware.
For large deployments (e.g thousands of networks and thousands of VMs), re-syncing the state, and hence rebuilding the configuration, could take a very long time. We need to introduce a bulk-sync mechanism so that such large syncs could be accomplished in seconds as opposed to minutes. ** Affects: neutron Importance: Undecided Assignee: Shashank Hegde (hegde-shashank) Status: New ** Tags: icehouse ml2 neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1279619 Title: Arista ML2 Driver enhancements to improve the Sync performance for scale deployments Status in OpenStack Neutron (virtual network service): New Bug description: When either end of the Arista ML2 driver reloads (Opestack controller running Neutron or Arista EOS), a full sync of DB state between the Neutron DB and EOS State is required to ensure that all tenant networks and ports are appropriately configured on the Arista Hardware. For large deployments (e.g thousands of networks and thousands of VMs), re-syncing the state, and hence rebuilding the configuration, could take a very long time. We need to introduce a bulk-sync mechanism so that such large syncs could be accomplished in seconds as opposed to minutes. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1279619/+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