On 29.01.2016 22:02, Guru Shetty wrote:
> This reverts commit 9b5422a98f817b9f2a1f8224cab7e1a8d0bbba1f.
>
> Reason:
> Calling 'ovs-appctl exit' on ovs-vswitchd will cause ovs-vswitchd
> to destroy all the ports from the datapath. This is an unacceptable
> behavior while restarting the daemons.
Ki
On Mon, Feb 1, 2016 at 12:33 PM, Liran Schour wrote:
> Python idl works now with "monitor_cond" method. Add test
> for backward compatibility with old "monitor" method.
>
> Signed-off-by: Liran Schour
>
> ---
> v2->v3:
> *cond_update() receives a single condition
> ---
> python/ovs/db/data.py |
Python idl works now with "monitor_cond" method. Add test
for backward compatibility with old "monitor" method.
Signed-off-by: Liran Schour
---
v2->v3:
*cond_update() receives a single condition
---
python/ovs/db/data.py | 18 -
python/ovs/db/idl.py | 181 +
Change ovsdb_condition to be a 3-element json array or a boolean value.
It will be used for conditional monitoring.
Signed-off-by: Liran Schour
---
v2->v3:
* Remove condition_add() and condition_remove() and all sub-functions
* Allow single bollean value XOR
---
ovsdb/condition.c| 170
Hold session's conditions in ovsdb_monitor_session_condition. Pass it
to ovsdb_monitor for generating "update2" notifications.
Add functions that can generate "update2" notification for a
"monitor_cond" session.
json_cache is enabled only for session's with nulled or empty condition.
"monitor_cond"
ovsdb-server now accepts "monitor_cond_update" request. On conditions update
we insert all rows of table in a new changes list - OVSDB_MONITOR_ALL that are
being indexed by the transaction-id at the moment of insertion.
JSON cache is being used only for empty condition monitor sessions.
Sees ovsdb-
Add API that allows the user to create condition iteratively
and send condition_update to the server.
Signed-off-by: Liran Schour
---
v2->v3:
* Simplify API to allow iteratively adding clauses to condition
before send monitor_cond_update
* monitor_cond_update receives only a single json condit
This patch series implements conditional monitoring by introducing an OVSDB
RFC extension with 2 new JSON-RPC methods: "monitor_cond" and
"monitor_cond_update". Specification of this extension is defined in the
ovsdb-server (1) man page.
Monitor2 is now merged into monitor_cond. A monitor_cond sess
This commit allows to add non-monitored columns to a monitored table.
It will be used to evaluate conditions on non-monitored columns.
Update notification includes only monitored columns.
Signed-off-by: Liran Schour
---
ovsdb/jsonrpc-server.c | 23 +++
ovsdb/monitor.c
IDL uses now a uuid to specify a monitoring session that is being
sent to the server on "monitor_cond" request.
This uuid will be used to issue ongoing "monitor_cond_change" requests
for this monitoring session.
Signed-off-by: Liran Schour
---
lib/ovsdb-idl.c | 13 +
lib/ovsdb-idl.h
Testsing ovsdb-idl with condition change by "monitor_cond_update"
method.
Signed-off-by: Liran Schour
---
v2->v3:
* monitor_cond_update receives a single condition
* Use generated automatic *_add_clause_*() API
* Test multiple clauses
---
tests/ovsdb-idl.at | 97 ++
Columns indexing is different in ovsdb_row then in ovsdb_monitor_row.
We need mapping between the 2 for condition evaluation.
signed-off-by: Liran Schour
---
v2->v3:
* Describe columns_index_map in comment
* Init columns_index_map with invalid value (-1)
---
ovsdb/monitor.c | 29 +++
\ȽmU<H*ÊÞ$·¤¿z0
媺zA7ÐzjfÑhby~5(Ètv
l:Q,)ï¿,HBh{sAÂJd¿cI]ãÐEL¿7ÙÖ±yËçZá3¶9w
óä?Ùá~W÷I>·C]Ç?ª¾#¹`Ò¸8þa´WÚ
°Ê&¥ëFPjZd¼L¤òèpZ$íùEu»öxæ÷÷'%ó¶/
õµGçÆDò¹E·æ¿}ÔE0c6v¨o(´KÑ"Ô5"¥ªlX¹¢ýRÔ¢[ä7Sc_vV:Ü^öSX
ߣMðÕ1Ý2]»;Ë.ï}ÔFHö°\D©®²£*µd(à¶äq7©.0?Ì¡u¸CmÅa%i¯VL6v¿ëö8p»,¹ï;
30+ Day Old Patches
===
ID State Date Name
-- -
548008 New2015-11-24 11:19:01 [ovs-dev,v4,2/4] ovn: New flows for DHCP
tranffic
548010 New2015-11-24 11:19:02 [ovs-dev,v4,3/4] ovn: Process dhcp
packet-ins and
I find it strange and misleading for full time employees to use aliases on OPEN
SOURCE mailing lists. Is the code OPEN but affiliation is not? Does anyone work
pro bono?
The community will be better off if we all clearly identify our affiliations
Sorry if you find this comment disturbing. My af
15 matches
Mail list logo
