Open Stack

6 minutes is surely the symptom of something wrong. The RPC is
asynchronous. A router_updated notification is sent from the server side as
soon as the floating IP is associated.
The l3 agent apparently is either missing or processing this notification
with a huge delay. Indeed the floating IP might be eventually associated
even if the notification is missed since every operation which changes a
logical router state triggers a complete resync of that router's state.

In order to understand what is going on, I have a few additional questions:
- are there enormous delays even when adding/removing router interfaces, or
setting the router's gateway?
- when you associate a floating IP, how long does it take for the status of
the floating IP to be set to ACTIVE? Is it still 6 minutes, is it less, or
does the status never get to active even if the floating IP is actually
working?

Salvatore

On 2 April 2015 at 16:54, Mike Spreitzer <mspreitz at us.ibm.com> wrote:

> > I think I am seeing a latency on the order of 10 seconds between (a)
> > the time Neutron returns success from that operation and (b) the
> > time when the association is actually functioning.  Is this sort of
> > latency to be expected?  I am using Juno, ML2, OVS, and GRE, if it
> matters.
>
> Sorry, I goofed when I calculated the time; I saw about 6 minutes between
> the return from the floatingip-associate operation and when it took
> effect.  Is the RPC from Neutron server to L3 agent synchronous with that
> API operation?
>
> In this situation I had about 300 floating IPs spread over 4 routers, all
> served by one L3 agent.
>
> Thanks,
> Mike
> _______________________________________________
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20150403/be2b04b2/attachment.html>