[Ryu-devel] [PATCH] add network_awareness module

2016-07-06 Thread 李呈
To whom it may concern, First of all, I have to apologize for sending email again and again. I notice that my email context is so much that hard to display in a email. Thus, I delete the patch information. You can review the code in attached file. Sorry again for bothering you. This is a Ryu App

[Ryu-devel] [PATCH] add network awareness module

2016-07-06 Thread ????-????
To whom it may concern, First of all, I have to apologize for sending email again and again. I notice that my email context is so much that hard to display in a email. Thus, I delete the patch information. You can review the code in attached file. Sorry again for bothering you. This is a R

Re: [Ryu-devel] specify the datapath ID

2016-07-06 Thread Iwase Yusuke
Hi, On 2016年06月27日 14:36, tanvir.ulhu...@data61.csiro.au wrote: > > Hi > > > I have three questions. > > > Question 1: I want to add a data flow in a specific switch among available > switches in the network. > > > I have used the following code with that intention that it will add a data > flow

Re: [Ryu-devel] add flow entry to egress table

2016-07-06 Thread Iwase Yusuke
Hi, According to OpenFlow Spec 1.5, you need to know which table is the first egress table, first. If your switch supports egress table, you can check the capabilities for the egress table by OFPTableFeaturesStatsReply messages. OFPTFF_FIRST_EGRESS capability flag indicates the first egress tabl

[Ryu-devel] [PATCH] fix test packet field value

2016-07-06 Thread Kawai, Hiroaki
To test VLAN_PCP, we must set matcing VLAN_VID. Table miss test was testing VLAN_VID instead of VLAN_PCP, because the packet had mismatching VLAN_VID. --- ryu/tests/switch/of13/match/07_VLAN_PCP.json | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ryu/tests/switch/of13/ma

Re: [Ryu-devel] Handling New Protocols with Ryu

2016-07-06 Thread Sam Snodgrass
Thank you for the response Iwase, Originally my protocol did not reserve any tcp ports. However, in order to test your solution, I added TCP ports with unique values to the protocol, and implemented your changes. Unfortunately, the result is the same (albeit with additional fields): '\xad\x9c\xd

[Ryu-devel] USA Software Directory

2016-07-06 Thread Katrina Alexander
Hi, Are you looking for any of the following software users contact information for your email campaigns or marketing purposes? * ERP-JD Edwards, Infor Baan, SAP, Exact Software, Net Suite, PeopleSoft, etc. * CRM-Salesforce, MS Dynamics, Net Suite, Siebel, TeraData, Epicor,

Re: [Ryu-devel] Handling New Protocols with Ryu

2016-07-06 Thread Sam Snodgrass
Thanks everyone. I realize that what I should actually be doing is modifying the existing openflow protocols with additional fields, not defining new protocols. Sorry for the confusion and thanks again for taking the time to help. I will create a new thread if I run into new problems in that appr

Re: [Ryu-devel] mark the data packet (Hiroaki KAWAI, tanvir.ulhu...@data61.csiro.au)

2016-07-06 Thread Hiroaki KAWAI
Hi, Tanvir NXM_NX_PKT_MARK is heavily dependent on Linux kernel packet processing. And it is not the matter of ryu itself, I'll show an example only with Open vSwitch. It was very hard for me to examine the actual working case, but I found following seems working: - setup Open vSwitch and veth,

Re: [Ryu-devel] [PATCH] fix test packet field value

2016-07-06 Thread Iwase Yusuke
Hi Kawai-San, Thank you for your nice patch! On 2016年07月06日 20:06, Kawai, Hiroaki wrote: > To test VLAN_PCP, we must set matcing VLAN_VID. > Table miss test was testing VLAN_VID instead of VLAN_PCP, > because the packet had mismatching VLAN_VID. Additionally, how about setting vlan_vid=(OFPVID_

[Ryu-devel] [PATCH 0/9] Support some NXAction

2016-07-06 Thread Shinpei Muraoka
Currently, there is NXAction that is not supported by Ryu. The following patches add NXActions that is not supported by Ryu, and Update the parameter of Some NxAction. Additionally, add test cases and documents are updated. Shinpei Muraoka (9): ofproto/nx_actions: Add NXAction used only in Open

[Ryu-devel] [PATCH 6/9] ofproto/nx_actions: Add default argument to specs field of NXActionLearn

2016-07-06 Thread Shinpei Muraoka
Signed-off-by: Shinpei Muraoka --- ryu/ofproto/nx_actions.py | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/ryu/ofproto/nx_actions.py b/ryu/ofproto/nx_actions.py index 74ca14a..cabbe3b 100644 --- a/ryu/ofproto/nx_actions.py +++ b/ryu/ofproto/nx_actions.py @@ -608,7 +6

[Ryu-devel] [PATCH 3/9] ofproto/nx_actions: Update arguments to be compatible with ovs-ofctl

2016-07-06 Thread Shinpei Muraoka
This patch, update the methods that are to be specified in the NXM or OXM. Update the oxm_types specified in the bit format to the string. Update the following NXAction. - NXActionOutputReg - NXActionMultipath - NXActionBundle - NXActionBundleLoad Signed-off-by: Shinpei Muraoka --- ryu/ofpr

[Ryu-devel] [PATCH 7/9] ofproto/nx_actions: Add comment for Ryu documents

2016-07-06 Thread Shinpei Muraoka
Signed-off-by: Shinpei Muraoka --- doc/source/nicira_ext_ref.rst | 42 +- ryu/ofproto/nx_actions.py | 1242 + 2 files changed, 1280 insertions(+), 4 deletions(-) diff --git a/doc/source/nicira_ext_ref.rst b/doc/source/nicira_ext_ref.rst index 562e12a

[Ryu-devel] [PATCH 4/9] ofproto/nx_actions: Support missing NXAction

2016-07-06 Thread Shinpei Muraoka
Actions to be added are as following. - NXActionDecTtlCntIds - NXActionStackPush - NXActionStackPop - NXActionSample - NXActionOutputReg2 - NXActionRegLoad2 - NXActionController2 Signed-off-by: Shinpei Muraoka --- ryu/ofproto/nicira_ext.py | 14 ++ ryu/ofproto/nx_actions.py | 474 +++

[Ryu-devel] [PATCH 5/9] test_parser: Add test data for missing NXAction

2016-07-06 Thread Shinpei Muraoka
Note: The following actions are not implemented yet, because ovs-ofctl command is not supported. - NXActionRegLoad2 - NXActionOutputReg2 Signed-off-by: Shinpei Muraoka --- .../of13/ovs-ofctl-of13-action_controller2.packet | Bin 0 -> 128 bytes .../ovs-ofctl-of13-action_dec_ttl_cnt_ids.packet

[Ryu-devel] [PATCH 8/9] ofproto/nx_actions: Support some NXAction

2016-07-06 Thread Shinpei Muraoka
Actions to be added are as following. - NXActionSample2 - NXActionOutputTrunc Signed-off-by: Shinpei Muraoka --- doc/source/nicira_ext_ref.rst | 2 + ryu/ofproto/nicira_ext.py | 2 + ryu/ofproto/nx_actions.py | 138 ++ 3 files changed, 142 in

[Ryu-devel] [PATCH 1/9] ofproto/nx_actions: Add NXAction used only in OpenFlow1.0

2016-07-06 Thread Shinpei Muraoka
There is NXAction to be used only in OpenFlow1.0. These actions are supported by default in OpenFlow1.2 or later. Therefore, it becomes unnecessary as the NXAction. But, to add the NXAction in order to be able to use in OpenFlow1.0. Actions to be added are as following. - NXActionSetQueue - NXAct

[Ryu-devel] [PATCH 2/9] test_parser: Add test data for NXAction used only in OpenFlow1.0

2016-07-06 Thread Shinpei Muraoka
Signed-off-by: Shinpei Muraoka --- .../of10/ovs-ofctl-of10-action_dec_mpls_ttl.packet | Bin 0 -> 88 bytes .../of10/ovs-ofctl-of10-action_dec_nw_ttl.packet | Bin 0 -> 88 bytes .../of10/ovs-ofctl-of10-action_pop_mpls.packet | Bin 0 -> 88 bytes .../of10/ovs-ofctl-of10-action_push_mpls.packe

[Ryu-devel] [PATCH 9/9] test_parser: Add test data for some NXAction

2016-07-06 Thread Shinpei Muraoka
Signed-off-by: Shinpei Muraoka --- .../of13/ovs-ofctl-of13-action_output_trunc.packet | Bin 0 -> 80 bytes .../of13/ovs-ofctl-of13-action_sample2.packet | Bin 0 -> 96 bytes ryu/tests/packet_data_generator3/gen.py| 12 ++ .../ovs-ofctl-of13-action_output_trunc.packet.json |

[Ryu-devel] [PATCH] fix of13 VLAN_PCP test case

2016-07-06 Thread Kawai, Hiroaki
To test VLAN_PCP, VLAN_VID must match. Table miss test was testing VLAN_VID instead of VLAN_PCP, because the packet had mismatching VLAN_VID. Fixes to set only OFPVID_PRESENT bit in the match field. --- ryu/tests/switch/of13/match/07_VLAN_PCP.json | 12 ++-- 1 file changed, 6 insertions(+)

Re: [Ryu-devel] [PATCH] fix of13 VLAN_PCP test case

2016-07-06 Thread Iwase Yusuke
Hi Kawai-San, Thank you for updating your patch! It looks good to me. Thanks, Iwase On 2016年07月07日 12:01, Kawai, Hiroaki wrote: > To test VLAN_PCP, VLAN_VID must match. > Table miss test was testing VLAN_VID instead of VLAN_PCP, > because the packet had mismatching VLAN_VID. > Fixes to set onl

Re: [Ryu-devel] please help: ovs can't react the "get_schema" method from ryu

2016-07-06 Thread Jason Kölker
On Thu, Jul 7, 2016 at 1:57 AM, 谢磊 wrote: >when i used ovsdb protocol integrated into ryu, i met a problem like > this: >first, i set manager for ovs like this: ovs-vsctl set-manager > tcp:ip:port >second, i write a very simple app in which a handler function handle > NewOV

[Ryu-devel] [PATCH] ofctl_nicira_ext: Update to use new NXAction API

2016-07-06 Thread Jason Kölker
Signed-off-by: Jason Kölker --- ryu/lib/ofctl_nicira_ext.py | 9 +++-- 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/ryu/lib/ofctl_nicira_ext.py b/ryu/lib/ofctl_nicira_ext.py index 3a5c6be..fd77369 100644 --- a/ryu/lib/ofctl_nicira_ext.py +++ b/ryu/lib/ofctl_nicira_ext.py @@ -

Re: [Ryu-devel] please help: ovs can't react the "get_schema" method from ryu

2016-07-06 Thread 谢磊
thank you for your quick reply i use tcpdump in both controller and ovs, and the result is: 1. controller can send ls_dbs method and receive reply from ovs, then send get_schema method but no reply 2. when ovs receive get_schema from controller, it quickly react and send the schema of Open_vSwitch,

Re: [Ryu-devel] please help: ovs can't react the "get_schema" method from ryu

2016-07-06 Thread Jason Kölker
On Thu, Jul 7, 2016 at 6:19 AM, 谢磊 wrote: > thank you for your quick reply > i use tcpdump in both controller and ovs, and the result is: > 1. controller can send ls_dbs method and receive reply from ovs, then send > get_schema method but no reply > 2. when ovs receive get_schema from controller,

Re: [Ryu-devel] [PATCH 4/7] ofproto/nx_actions: Update arguments to be compatible with ovs-ofctl

2016-07-06 Thread Takashi YAMAMOTO
this change broke dragonflow. https://bugs.launchpad.net/dragonflow/+bug/1599367 i thought we aimed to align with on-wire fields rather than ovs-ofctl etc. was the policy changed? On Mon, Jun 6, 2016 at 9:48 AM, Shinpei Muraoka wrote: > This patch, update the methods that are to be specified in