Open Stack

If there are any errors on the agent connecting to the message bus or
retrieving messages, an exception will be thrown in the main rpc_loop,
which will be caught and a sync flag will be set to true, which will
trigger the sync on the next loop.

However, I briefly looked through the L2 agent code and didn't see a
periodic task to resync the port information to protect from a neutron
server that failed to send a notification because it crashed or lost its
amqp connection. The L3 agent has a period sync routers task that helps in
this regard. Maybe another neutron developer more familiar with the L2
agent can chime in here if I'm missing anything.

On Thu, Mar 12, 2015 at 6:19 AM, Leo Y <minherz at gmail.com> wrote:

> What does it mean under "if that notification is lost, the agent will
> eventually resynchronize"? Is it proven/guaranteed? By what means?
> Can you, please the process with more details? Or point me to resources
> that describe it.
>
> Thank you
>
>
> On Mon, Mar 9, 2015 at 2:11 AM, Kevin Benton <blak111 at gmail.com> wrote:
>
>> Port changes will result in an update message being sent on the AMQP
>> message bus. When the agent receives it, it will affect the communications
>> then. If that notification is lost, the agent will eventually resynchronize.
>>
>> So during normal operations, the change should take effect within a few
>> seconds.
>>
>> On Sat, Mar 7, 2015 at 4:10 AM, Leo Y <minherz at gmail.com> wrote:
>>
>>> Hello,
>>>
>>> What happens when neutron DB is updated to change network settings (e.g.
>>> via Dashboard or manually) when there are communication sessions opened in
>>> compute nodes. Does it influence those sessions? When the update is
>>> propagated to compute nodes?
>>>
>>> Thank you
>>>
>>>
>>> __________________________________________________________________________
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>>
>> --
>> Kevin Benton
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Regards,
>         Leo
> ---------------------------------------------------------
> I enjoy the massacre of ads. This sentence will slaughter ads without a
> messy bloodbath
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Kevin Benton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150312/d872c7b0/attachment.html>