Open Stack

>*But there is no such a feature in Neutron. Right? Will the community
merge it soon? And can we consider it with agent-style mechanism together?*

The agents have their own mechanisms for getting information from the
server. The community has no plans to merge a feature that is going to be
different for almost every vendor.

We tried to come up with some common syncing stuff in the recent ML2
meeting, the various backends had different methods of detecting when they
were out of sync with Neutron (e.g. headers in hashes, recording errors,
etc), all of which depended on the capabilities of the backend. Then the
sync method itself was different between backends (sending deltas, sending
entire state, sending a replay log, etc).

About the only thing they have in common is that they need a way detect if
they are out of sync and they need a method to sync. So that's two abstract
methods, and we likely can't even agree on when they should be called.

Echoing Salvatore's comments, what is it that you want to see?

On Mon, Oct 12, 2015 at 12:29 AM, Germy Lure <germy.lure at gmail.com> wrote:

> Hi Kevin,
>
> *Thank you for your response. Periodic data checking is a popular and
> effective method to sync info. But there is no such a feature in Neutron.
> Right? Will the community merge it soon? And can we consider it with
> agent-style mechanism together?*
>
> Vendor-specific extension or coding a periodic task private by vendor is
> not a good solution, I think. Because it means that Neutron-Sever could not
> integrate with multiple vendors' controller and even the controller of
> those vendors that introduced this extension or task could not integrate
> with a standard community Neutron-Server.
> That is just the tip of the iceberg. Many of the other problems resulting,
> such as fixing bugs,upgrade,patch and etc.
> But wait, is it a vendor-specific feature? Of course not. All software
> systems need data checking.
>
> Many thanks.
> Germy
>
>
> On Sun, Oct 11, 2015 at 4:28 PM, Kevin Benton <blak111 at gmail.com> wrote:
>
>> You can have a periodic task that asks your backend if it needs sync info.
>> Another option is to define a vendor-specific extension that makes it
>> easy to retrieve all info in one call via the HTTP API.
>>
>> On Sat, Oct 10, 2015 at 2:24 AM, Germy Lure <germy.lure at gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> After restarting, Agents load data from Neutron via RPC. What about 3-rd
>>> controller? They only can re-gather data via NBI. Right?
>>>
>>> Is it possible to provide some mechanism for those controllers and
>>> agents to sync data? or something else I missed?
>>>
>>> Thanks
>>> Germy
>>>
>>>
>>>
>>> __________________________________________________________________________
>>> 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
>>
>>
>
> __________________________________________________________________________
> 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/20151012/d64e969c/attachment.html>