Re: [Ryu-devel] [PATCH] try to sync documentation with the reality

hi, > On Mon, 25 Feb 2013 16:14:30 +0900 > YAMAMOTO Takashi wrote: > >> Signed-off-by: YAMAMOTO Takashi >> --- >> doc/source/parameters.rst | 78 >> +-- >> 1 file changed, 34 insertions(+), 44 deletions(-) > > Great! But what tree this can be appli

Re: [Ryu-devel] [PATCH] try to sync documentation with the reality

On Mon, 25 Feb 2013 16:14:30 +0900 YAMAMOTO Takashi wrote: > Signed-off-by: YAMAMOTO Takashi > --- > doc/source/parameters.rst | 78 > +-- > 1 file changed, 34 insertions(+), 44 deletions(-) Great! But what tree this can be applied to? I can't apply

[Ryu-devel] [PATCH] try to sync documentation with the reality

Signed-off-by: YAMAMOTO Takashi --- doc/source/parameters.rst | 78 +-- 1 file changed, 34 insertions(+), 44 deletions(-) diff --git a/doc/source/parameters.rst b/doc/source/parameters.rst index 23e634c..7647b87 100644 --- a/doc/source/parameters.rst +

Re: [Ryu-devel] What is a status of failing mininet tests(ryu/tests/mininet).

Hi Piotr, Thank you. I found the following error message in the log. > Error: run_ryu() : failed to start ryu-manager. Please check the ryu-manager logs: /tmp/test-mn/dump/ryu-manager.*.log In addition, I found the place to be worried about. It is that the flow is not set to ovs. > NXST_FLOW repl

Re: [Ryu-devel] [PATCH v2] xflow: add sflow support

On Mon, 25 Feb 2013 14:30:27 +0900 "watanabe.fumitaka" wrote: > This patch implements sflow packet parser. > I confirmed that it can parse a sflow packet from Open vSwitch. > > > This update(v1->v2) contains the following change. > > use symbolic value for constant. > add super().__init__()

[Ryu-devel] [PATCH v2] xflow: add sflow support

This patch implements sflow packet parser. I confirmed that it can parse a sflow packet from Open vSwitch. This update(v1->v2) contains the following change. use symbolic value for constant. add super().__init__() to some class. avoid '\' for line continuation. avoid unnecessary parens. ren

Re: [Ryu-devel] [PATCH 1/5] add cli ryu application

On Mon, 25 Feb 2013 11:12:55 +0900 (JST) yamam...@valinux.co.jp (YAMAMOTO Takashi) wrote: > are you suggesting to separate the following two? > - management logic which provides some internal api > - user interface backends which consumes the above api Yes. That's how the management interface is

Re: [Ryu-devel] [PATCH 2/3] update an example after option name changes

On Mon, 25 Feb 2013 11:12:59 +0900 (JST) yamam...@valinux.co.jp (YAMAMOTO Takashi) wrote: >> Can you fold this into the first to avoid the breakage? > > do you prefer to fold example/documentation changes into the corresponding > code change in general? Yes about configuration file changes. ---

Re: [Ryu-devel] [PATCH 2/3] update an example after option name changes

> Can you fold this into the first to avoid the breakage? do you prefer to fold example/documentation changes into the corresponding code change in general? YAMAMOTO Takashi > > On Thu, 21 Feb 2013 11:23:33 +0900 > YAMAMOTO Takashi wrote: > >> Signed-off-by: YAMAMOTO Takashi >> --- >> etc/r

Re: [Ryu-devel] [PATCH 1/5] add cli ryu application

hi, > On Fri, 22 Feb 2013 16:39:49 +0900 > YAMAMOTO Takashi wrote: > >> Signed-off-by: YAMAMOTO Takashi >> --- >> ryu/app/cli.py | 70 >> ++ >> 1 file changed, 70 insertions(+) >> create mode 100644 ryu/app/cli.py >> >> diff --git a/ry

Re: [Ryu-devel] [PATCH 2/3] update an example after option name changes

Can you fold this into the first to avoid the breakage? On Thu, 21 Feb 2013 11:23:33 +0900 YAMAMOTO Takashi wrote: > Signed-off-by: YAMAMOTO Takashi > --- > etc/ryu/ryu.conf | 8 > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/etc/ryu/ryu.conf b/etc/ryu/ryu.conf >