[openstack-dev] [neutron]What happened when the 3-rd controller restarted?
germy.lure at gmail.com
Mon Oct 12 07:29:05 UTC 2015
*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.
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?
>> OpenStack Development Mailing List (not for usage questions)
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> Kevin Benton
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev