| 2020-05-27 14:57:32 |
Maciej Jozefczyk |
description |
I noticed on upstream and downstream gates that while creating FloatingIP for action like:
neutron floatingip-create public
For ml2/ovs and ml2/ovn this operation takes minimum ~4 seconds.
The same we can find on u/s gates from rally jobs [1].
While we put the load on Neutron server it normally more than 10 seconds.
For ML/OVN creating a FIP doesn't end with creating NAT entry in OVN NBDB row. So its clearly only API operation.
Maybe we can consider profiling it?
[1] https://98a898dcf3dfb1090155-da3b599be5166de1dcb38898c60ea3c9.ssl.cf5.rackcdn.com/729588/1/check/neutron-rally-task/dd55aa7/results/report.html#/NeutronNetworks.associate_and_dissociate_floating_ips/overview |
I noticed on upstream and downstream gates that while creating FloatingIP for action like:
neutron floatingip-create public
For ml2/ovs and ml2/ovn this operation takes minimum ~4 seconds.
The same we can find on u/s gates from rally jobs [1].
While we put the load on Neutron server it normally takes more than 10 seconds.
For ML/OVN creating a FIP doesn't end with creating NAT entry in OVN NBDB row. So its clearly only API operation.
Maybe we can consider profiling it?
[1] https://98a898dcf3dfb1090155-da3b599be5166de1dcb38898c60ea3c9.ssl.cf5.rackcdn.com/729588/1/check/neutron-rally-task/dd55aa7/results/report.html#/NeutronNetworks.associate_and_dissociate_floating_ips/overview |
|
