[Ryu-devel] [PATCH] Extend OVSDB api

From: Alan Quillin Adds more ovsdb methods for setting key/values to other_config and external_ids, adds bility to set the controller for a bridge, and adds the ability to create a new port/interface on a bridge Signed-off-by: Alan Quillin --- ryu/services/protocols/ovsdb/api.py | 273

[Ryu-devel] [PATCH] Enable filtering the OVSDB schema tables/columns

tables/columns to help with scale problems on hosts with a large number of bridges and interfaces. Signed-off-by: Alan Quillin --- ryu/services/protocols/ovsdb/client.py | 70 - ryu/services/protocols/ovsdb/manager.py | 23 ++- 2 files changed, 90 insertions

[Ryu-devel] [PATCH] Added support for the tcp flags nicira extension

From: Alan Quillin Adds support for setting TCP flags using the nicira extensions for OF1.0 and OF1.2+ Allows using the extensions with OF1.2+ for OVS versions < 2.4 where the TCP flags OF extension is not yet supported. Signed-off-by: Alan Quillin --- ryu/ofproto/nx_match.py |

[Ryu-devel] Issue setting tcp_flags in flow mod with ovs 2.3.2

I have some flows that we we need to push down to OVS which work fine when using ovs 2.4+, but when we connected up an instance running ovs 2.3.2, it was failing with a BAD_FIELD message. Here is an example of the debug logs. DEBUG : bison.flows: Sending message with xid (b74c612a): version=Non

Re: [Ryu-devel] [PATCH] bgp: Added support to indicate the next hop IP address for the BGP module

age first. This changes to logic to use the check for the > > next hop in the order prefix/path->peer config->speaker config. This > > will allow for sending the nexthop as part of the add_prefix message and > > allow for overiding the nexthop of the peer if one is set

[Ryu-devel] [PATCH] Added support to indicate the next hop IP address for the BGP module

From: Alan Quillin If the path has a next hop value set, it should be used in the BGP Update message first. This changes to logic to use the check for the next hop in the order prefix/path->peer config->speaker config. This will allow for sending the nexthop as part of the add_prefix m

Re: [Ryu-devel] [PATCH] Modified BGP Update logic to use the path nexthop value first

, then use the nexthop from the path, else fall into the other logic to use nexthop value set on the peer or the ip of the RyuBGP1. Please let me know if my assumptions here are correct. Thanks, - Alan Quillin From: Toshiki Tsuboi [t.tsubo2...@gmail.com

[Ryu-devel] (no subject)

t to check the reg_bits and if > 0 then set the flow format to NXT. If I did not format these correctly, or did not format this email correctly please let me know, this is mt first project that uses this type of change management. Thanks, -Alan Quillin binqRblxG2n5f.bin Description: 0001-