>> 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.
Which is a state for each row, for ea
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 with
; To: Zayats, Michael
> Cc: dev@openvswitch.org; ops-...@lists.openswitch.net
> Subject: Re: [ovs-dev] OpenSwitch Project
>
> On Tue, Oct 13, 2015 at 05:28:47PM +, Zayats, Michael wrote:
> > Obvious parts that we would prefer to discuss and develop upstream
> are
> > O
Following the launch of the OpenSwitch project (www.openswitch.net), I would
like to address the Open vSwitch community, explain how OpenSwitch leverages
and aligns with OVS and start a discussion about a collaboration strategy.
OpenSwitch, OPS for short, is built to operate physical switches in
Following the launch of the OpenSwitch project (www.openswitch.net),
I would like to address the Open vSwitch community, explain how OpenSwitch
leverages and aligns with OVS and start a discussion about a collaboration
strategy.
OpenSwitch, OPS for short, is built to operate physical switches in
Hi Ethan,
Regarding some old patch in which you added other_config:lacp-aggregation-key
to the Interface table.
I must be missing a reason of adding it to the Interface and not to the Port,
where it would affect all slaves at once:
when should users configure the key differently on slaves of t
> -Original Message-
> From: Gray, Mark D [mailto:mark.d.g...@intel.com]
> Sent: Thursday, June 11, 2015 11:02 AM
> To: Zayats, Michael; dev@openvswitch.org
> Subject: RE: [ovs-dev] [PATCH] vswitchd: adding plugin infrastructre
>
> >
> > Per this patch ov
