[openstack-dev] [neutron] Generic question about synchronizing neutron agent on compute node with DB

Leo Y minherz at gmail.com
Thu Mar 12 13:19:42 UTC 2015


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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150312/a8919fa4/attachment.html>


More information about the OpenStack-dev mailing list