[ovs-dev] OVN: V2 RFC add a new JSON-RPC selective monitoringmethod

Liran Schour LIRANS at il.ibm.com
Sat Oct 17 16:34:10 UTC 2015


"Zayats, Michael" <michael.zayats at hpe.com> wrote on 16/10/2015 10:07:05 
AM:
>
> I am also very interested in the ?where? clause in ?monitor? for 
> OpenSwitch use and we intended to propose something similar.
> 
> Some questions:
> 
> What will we do when row A is the only reference to row B and row A 
> doesn?t pass the ?where? condition?
> Will A still be sent? or will B exist in IDL without any reference 
> even though B belongs to non root table?
>

In the current proposal only rows that match the conditions will be sent. 
That means that only row B will be sent.
 
> What happens when specific row passes ?where? clause, gets sent to 
> the subscriber, and then stops complying to the condition?
> Will client receive a notification that this row was removed? Should
> it understand that it?s not a real removal?
> 

According to the proposal:
  *  If "delete" is omitted or true, "update" notifications are sent for 
rows deleted from the table that match conditions or for rows modified in 
the table so that their old version does match the conditions and new 
version does not. (deleted row in the client's replica)
Means that client will get update notification to remove that row. No 
indication that it is not a real removal.

> Will OVSDB-server have to remember whether it synced this row for 
> each subscriber in order to send the right inserted/removed 
notifications?
>

Ovsdb-server has to maintain the state for each replica and send the right 
notifications for each client.

- Liran




More information about the dev mailing list