Public bug reported:
The ``OVNClient.update_floatingip`` method deletes and creates again the
OVN NAT rules when a FIP is updated. However, this process is not
necessary if only the QoS policy is updated. Only the QoS driver call is
needed. That speeds up the FIP process and avoids the
``FIPAddDeleteEvent`` that is called twice, when the NAT register is
deleted first and then added (if there is a fixed port associated to the
FIP).
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2025144
Title:
[OVN] ``update_floatingip`` should handle the case when only the QoS
policy is updated
Status in neutron:
New
Bug description:
The ``OVNClient.update_floatingip`` method deletes and creates again
the OVN NAT rules when a FIP is updated. However, this process is not
necessary if only the QoS policy is updated. Only the QoS driver call
is needed. That speeds up the FIP process and avoids the
``FIPAddDeleteEvent`` that is called twice, when the NAT register is
deleted first and then added (if there is a fixed port associated to
the FIP).
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2025144/+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
