Hi Anil,
Sorry, I meant "will each of the nodes write to the operational data store?" If ovsdb is connected to all the nodes, each will get the ovsdb notification and do a write transaction to the operational for the same data?

Sent from my Android phone using Symantec TouchDown (www.symantec.com)

-----Original Message-----
From: Anil Vishnoi [avishnoi@...]
Received: Wednesday, 02 Sep 2015, 0:20
To: Sharon Aicler (saichler) [saichler@...]; Sam Hague [shague@...]; ovsdb-dev@... [ovsdb-dev@...]
Subject: Re: OVSDB clustering needs from mdsal

Logically there is only one Operational/Config data store for all the nodes in the cluster. As of now persistence of operational data store is disabled, it only persist config data store.

On Wednesday 02 September 2015 05:48 AM, Sharon Aicler (saichler) wrote:

Hi,
Not sure how is it implemented now, if i have a N nodes cluster and the ovsdb is connected to each of the N nodes, does each node in the N cluster persist the operational data to the Data Store?

---

From: ovsdb-dev-bounces@... [ovsdb-dev-bounces@...] on behalf of Anil Vishnoi [avishnoi@...]
Sent: Tuesday, September 01, 2015 7:09 AM
To: Sam Hague; ovsdb-dev@...
Subject: Re: [ovsdb-dev] OVSDB clustering needs from mdsal

I think the only dependency from clustering perspective is controller project. Apart from that we don't have any specific dependency i believe.

Anil

On Tuesday 01 September 2015 05:35 PM, Sam Hague wrote:

Anil,

are there any specific changes needed by OVSDB for clustering from MDSAL?

Trying to get the formal dependencies request in before this Thursday's M2 deadline.

Thanks, Sam