Hi,
Why you need to separate wsgi ports for each applications?
I think you can separate the API for each applications by using URI path
pattern.
http://osrg.github.io/ryu-book/en/html/rest_api.html#implementing-simpleswitchcontroller-class
e.g.)
For application1: PATH=/application1
Hi,
> Does anyone know why this error in action format validation occurs? If you
> have any experience in using Ryu with OpenFlow 1.5, please share with me. It
> would be great if there is a sample code.
The cause of this problem is that OVS does not support OpenFlow 1.5 Packet-Out
messages.
Hi,
On 2016年07月22日 13:53, [email protected] wrote:
> Hi all
>
>
> Scenario:
>
>
>
> host1 --> switch 1-> switch2 -> host2
>
>
>
> python script:
>
> -
>
> -
>
>host1 = net.addHost('h1', cls=Host, mac='01:00:00:00:01:00',
> ip='172.16.20.10/24', defaultRou
stplib.py is used in simple_switch_stp_13.py which is an example
on Ryu-Book and supposes OVS as the connected switch.
So stplib is implemented with some assumptions for OVS behaviors
and in some cases, it cannot connect to other switch implementation,
e.g. Lagopus.
The following patches fix this
In Python3, cmp() method is no longer supported and numerical
operations evaluates value type more strictly.
So, stplib get some errors in its calculating process.
This patch fixes these problems and enable to use stplib on
Python3 interpreter.
Signed-off-by: IWASE Yusuke
---
ryu/lib/packet/bpd
According to OpenFlow Spec 1.3.5, OFPT_PORT_STATUS messages with
the reason value OFPPR_MODIFY should be sent the BOTH port state
and config have changed.
On the other hand, OVS does not send OFPT_PORT_STATUS messages
when the port config has changed and only sends when the port
state has changed.
