On Wed, Jul 27, 2016 at 4:15 PM, Zhou, Han wrote:
>
>
> On Wed, Jul 27, 2016 at 7:15 AM, Russell Bryant
> wrote:
>
>>
>>
>> On Wed, Jul 27, 2016 at 5:58 AM, Kevin Benton wrote:
>>
>>> > I'd like to see if we can solve the problems more generally.
>>>
>>> We've tried before but we very quickly r
On Wed, Jul 27, 2016 at 7:15 AM, Russell Bryant wrote:
>
>
> On Wed, Jul 27, 2016 at 5:58 AM, Kevin Benton wrote:
>
>> > I'd like to see if we can solve the problems more generally.
>>
>> We've tried before but we very quickly run into competing requirements
>> with regards to eventual consisten
On Wed, Jul 27, 2016 at 5:58 AM, Kevin Benton wrote:
> > I'd like to see if we can solve the problems more generally.
>
> We've tried before but we very quickly run into competing requirements
> with regards to eventual consistency. For example, asynchronous background
> sync doesn't work if some
> I'd like to see if we can solve the problems more generally.
We've tried before but we very quickly run into competing requirements with
regards to eventual consistency. For example, asynchronous background sync
doesn't work if someone wants their backend to confirm that port details
are accepta
On Fri, Jul 22, 2016 at 9:37 PM, Zhou, Han wrote:
> However, I didn't figure out how errors are handled with this approach.
> For example, a port is created in Neutron but ODL controller failed to
> create it although the journal thread successfully sent the request to ODL.
> And I didn't see how
On Fri, Jul 22, 2016 at 7:51 AM, Numan Siddique wrote:
> Thanks for the comments Amitabha.
> Please see comments inline
>
> On Fri, Jul 22, 2016 at 5:50 AM, Amitabha Biswas
> wrote:
>
>> Hi Numan,
>>
>> Thanks for the proposal. We have also been thinking about this use-case.
>>
>> If I’m reading
ack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [Neutron][networking-ovn][networking-odl] Syncing
neutron DB and OVN DB
Thanks for the comments Amitabha.
Please see comments inline
On Fri, Jul 22, 2016 at 5:50 AM, Amitabha Biswas
mailto:azbis...@gmail.com
Thanks for the comments Amitabha.
Please see comments inline
On Fri, Jul 22, 2016 at 5:50 AM, Amitabha Biswas wrote:
> Hi Numan,
>
> Thanks for the proposal. We have also been thinking about this use-case.
>
> If I’m reading this accurately (and I may not be), it seems that the
> proposal is to
Hi Numan,
Thanks for the proposal. We have also been thinking about this use-case.
If I’m reading this accurately (and I may not be), it seems that the proposal
is to not have any OVN NB (CUD) operations (R operations outside the scope)
done by the api_worker threads but rather by a new journal
Adding the proper tags in subject
On Wed, Jul 13, 2016 at 1:22 PM, Numan Siddique wrote:
> Hi Neutrinos,
>
> Presently, In the OVN ML2 driver we have 2 ways to sync neutron DB and OVN
> DB
> - At neutron-server startup, OVN ML2 driver syncs the neutron DB and OVN
> DB if sync mode is set to rep
Hi Neutrinos,
Presently, In the OVN ML2 driver we have 2 ways to sync neutron DB and OVN
DB
- At neutron-server startup, OVN ML2 driver syncs the neutron DB and OVN
DB if sync mode is set to repair.
- Admin can run the "neutron-ovn-db-sync-util" to sync the DBs.
Recently, in the v2 of networkin
11 matches
Mail list logo
