yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #64371
[Bug 1665215] Re: performance degradation in agent<->server port wiring process
Reviewed: https://review.openstack.org/434682
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1be00e8239db3db6e962b30a6b3c2b90144e19b8
Submitter: Jenkins
Branch: master
commit 1be00e8239db3db6e962b30a6b3c2b90144e19b8
Author: Kevin Benton <kevin@xxxxxxxxxx>
Date: Wed Feb 15 23:05:42 2017 -0800
Bulk up port status updating in ML2 RPC
This eliminates the last of the bottlenecks in
get_devices_details_list_and_failed_devices by making the status
updates use a bulk data retrieval as well.
The last remaining thing that will impact performance is the status
update back to ACTIVE on removal of the provisioning blocks. However,
that will require a much larger refactor since it is callback driven
at the individual port level.
Elimination of the L2pop driver will ultimately solve this completely
since we won't need to cycle the port status anymore on every single
agent restart.
Closes-Bug: #1665215
Change-Id: I99c2b77b35e6eabb6e4f633c4e8e2533594c6b55
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1665215
Title:
performance degradation in agent<->server port wiring process
Status in neutron:
Fix Released
Bug description:
The server<->agent communication process for wiring a port is taking a pretty significant amount of time. See the following analysis:
http://lists.openstack.org/pipermail/openstack-dev/2017-February/112266.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1665215/+subscriptions
References