Re: [ovs-dev] [PATCH 1/4] docs: OVSDB replication design document

On Fri, Jun 24, 2016 at 04:44:02PM -0700, Ben Pfaff wrote: > From: Mario Cabrera > > The database replication functionality is designed to provide "fail > over" characteristics. There are two participating databases, one of > which is the "active" database and the other is

[ovs-dev] [PATCH 1/4] docs: OVSDB replication design document

From: Mario Cabrera The database replication functionality is designed to provide "fail over" characteristics. There are two participating databases, one of which is the "active" database and the other is the "stand by" database. Replication happens exclusively from the

Re: [ovs-dev] [PATCH 1/4] docs: OVSDB replication design document

[PATCH 1/4] docs: OVSDB replication design document On Tue, Mar 29, 2016 at 09:30:00PM +, Cabrera Vega, Mario Alberto wrote: > This patch series add database replication functionality between two > ovsdb-servers. > The main idea is that an "active" server replicate

Re: [ovs-dev] [PATCH 1/4] docs: OVSDB replication design document

On Tue, Mar 29, 2016 at 09:30:00PM +, Cabrera Vega, Mario Alberto wrote: > This patch series add database replication functionality between two > ovsdb-servers. > The main idea is that an "active" server replicate its database contents to an > "standby" server in order to provide "fail over"

Re: [ovs-dev] [PATCH 1/4] docs: OVSDB replication design document

On Mon, Apr 18, 2016 at 10:02:34AM -0600, Marcelo E. Magallon wrote: > On Mon, Apr 11, 2016 at 03:44:09PM -0700, Ben Pfaff wrote: > > On Fri, Apr 01, 2016 at 10:52:26AM -0700, Ben Pfaff wrote: > > > I don't think it makes sense to stack replication and Raft-based HA. > > > > > > Thinking about

Re: [ovs-dev] [PATCH 1/4] docs: OVSDB replication design document

Hi, sorry about the delay in responding. I was actually catching up with emails on the mailing list to try to gauge if we are indeed trying to accomplish the same thing or not. On Mon, Apr 11, 2016 at 03:44:09PM -0700, Ben Pfaff wrote: > On Fri, Apr 01, 2016 at 10:52:26AM -0700, Ben Pfaff

Re: [ovs-dev] [PATCH 1/4] docs: OVSDB replication design document

On Fri, Apr 01, 2016 at 10:52:26AM -0700, Ben Pfaff wrote: > I don't think it makes sense to stack replication and Raft-based HA. > > Thinking about OpenSwitch, I guess that your use case is something like > this: an OpenSwitch instance maintains, on-box, an authoritative > database instance, and

Re: [ovs-dev] [PATCH 1/4] docs: OVSDB replication design document

I don't think it makes sense to stack replication and Raft-based HA. Thinking about OpenSwitch, I guess that your use case is something like this: an OpenSwitch instance maintains, on-box, an authoritative database instance, and then the replication feature allows that database's content to be

Re: [ovs-dev] [PATCH 1/4] docs: OVSDB replication design document

On Thu, Mar 31, 2016 at 11:26 AM, Marcelo E. Magallon < marcelo.magal...@hpe.com> wrote: > Hi Ben, > > On 03/30/2016 06:13 PM, Ben Pfaff wrote: > > I understand the technical differences between the approaches. My question >> is whether high availability is your actual goal. If it is, then it >>

Re: [ovs-dev] [PATCH 1/4] docs: OVSDB replication design document

Hi Ben, On 03/30/2016 06:13 PM, Ben Pfaff wrote: I understand the technical differences between the approaches. My question is whether high availability is your actual goal. If it is, then it probably does not make sense to have multiple implementations. If you are trying to accomplish

Re: [ovs-dev] [PATCH 1/4] docs: OVSDB replication design document

On Wed, Mar 30, 2016 at 06:03:27PM -0600, Marcelo E. Magallon wrote: > On 03/30/2016 05:27 PM, Ben Pfaff wrote: > >I'm in the midst of implementing high availability for OVSDB, based on > >the Raft algorithm. When I'm done, it should be possible to set up > >OVSDB clusters with automatic

Re: [ovs-dev] [PATCH 1/4] docs: OVSDB replication design document

Hi Ben, On 03/30/2016 05:27 PM, Ben Pfaff wrote: I'm in the midst of implementing high availability for OVSDB, based on the Raft algorithm. When I'm done, it should be possible to set up OVSDB clusters with automatic failover. Is this the same use case as your code? No, in this case the

[ovs-dev] [PATCH 1/4] docs: OVSDB replication design document

This patch series add database replication functionality between two ovsdb-servers. The main idea is that an "active" server replicate its database contents to an "standby" server in order to provide "fail over" characteristics. --- From 511d124fed0f7fcf27327242a9089bce561da411 Mon Sep 17