Re: [openstack-dev] [neutron]What happened when the 3-rd controller restarted?

2015-10-16 Thread Germy Lure
Hi Salvatore, Thanks so much for your continuing answers. What you mentioned is partially where I was going. Indeed, I want to solve the whole consistency issue, not just at startup. I just thought that ensuring consistency at startup and each operation is enough for it. A periodic task need more

Re: [openstack-dev] [neutron]What happened when the 3-rd controller restarted?

2015-10-15 Thread Salvatore Orlando
Hi Germy, It seems that you're looking at solutions for ensuring consistency between the "desired" configuration (Neutron), and the actual one (whatever is in your backend) at startup. This has been discussed several times in the past - not just for synchronization at startup, but also for

Re: [openstack-dev] [neutron]What happened when the 3-rd controller restarted?

2015-10-14 Thread Germy Lure
Hi Salvatore and Kevin, I'm sorry for replying so late. I wanted to see whether the community had considered data sync for these two style(agent and controller) integration. To solve integrating multiple vendor's controllers, I need some help from community. That's the original purpose of this

Re: [openstack-dev] [neutron]What happened when the 3-rd controller restarted?

2015-10-12 Thread Germy Lure
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

Re: [openstack-dev] [neutron]What happened when the 3-rd controller restarted?

2015-10-12 Thread Salvatore Orlando
Inline, Salvatore On 12 October 2015 at 09:29, Germy Lure 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

Re: [openstack-dev] [neutron]What happened when the 3-rd controller restarted?

2015-10-12 Thread Kevin Benton
>*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

Re: [openstack-dev] [neutron]What happened when the 3-rd controller restarted?

2015-10-11 Thread Kevin Benton
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 wrote: > Hi all, > > After

[openstack-dev] [neutron]What happened when the 3-rd controller restarted?

2015-10-10 Thread Germy Lure
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