Thread: [Ryu-devel] FWD:[RYU & GRE Tunnelling]
Brought to you by:
nz_gizmoguy
From: Isaku Y. <isa...@gm...> - 2016-04-02 21:09:44
|
----- Forwarded message from Aykut Kadayifci <ayk...@gm...> ----- Date: Sat, 2 Apr 2016 12:21:02 +0200 Subject: RYU & GRE Tunnelling X-Mailer: Apple Mail (2.2102) Dear Mr. Yamahata, I’ve posted an email to the group regarding to this topic but i guess for me listing is not working that’s why i wanted to write an email to you. Currently we are working on an academic project by using RYU controller for our mobility protocol. We’d like to use GRE tunnelling mechanism in our project. We are using mininet to emulate our topology. I’ve seen your message on the internet to enable GRE you said we need to run these scripts ryu.app.gre_tunnel,ryu.app.quantum_adapter,ryu.app.rest,ryu.app.rest_conf_switch,ryu.app.rest_quantum,ryu.app.rest_tunnel,ryu.app.tunnel_port_updater together. Unfortunately i’m getting this error: File "/home/ubuntu/ryu-oe/ryu/app/quantum_adapter.py", line 26, in <module> from quantumclient import client as q_client ImportError: No module named quantum client Could you share any idea that i can run GRE mechanism along with our RYU application ? (without really using OpenStack) Many thanks. Aykut ----- End forwarded message ----- -- Isaku Yamahata <isa...@gm...> |
From: Isaku Y. <isa...@gm...> - 2016-04-01 18:10:29
|
Forwarding this to ryu-devel. ----- Forwarded message from Raghavan Kripakaran <R.k...@ca...> ----- Date: Thu, 31 Mar 2016 16:06:22 +0000 Subject: Excellent RYU presentation - seek advice user-agent: Microsoft-MacOutlook/14.4.4.140807 Yamahata San, Firstly, thanks for an excellent presentation of "RYU: SDN framework and Python experience" at the PyCon APAC 2013. I watched the video and studied the RYU documentation. You got me excited to have RYU installed and try out the examples. The RYU documentations were detailed, well written and they worked. Amazing. After successfully trying out the examples from the RYU documentation using RYU sample apps and mininet, I thought I'll try RYU and Open vSwitch on a real hardware without mininet. So I took a linux server having multiple ethernet NIC cards and I connected 2 laptops to 2 physical ports for my linux server. I then created 2 ovs-bridges, added each NIC ports to each OVS bridge and tried out the ryu.app.rest_router application with RYU. The idea was to mimic the mininet "--topo=linear,2" topology. I seek your advice and insights. I am stuck on finding information on how to connect the 2 OVS bridges (veth/patch/tun). What might be your advice? Please help Basically, I want to run this demo using 2 hosts(client, server) and 2 ovs bridges as in: https://osrg.github.io/ryu-book/en/html/rest_router.html I have 2 test cases: 1) UDP/TCP packets to be switched from 10.0.0.2:6000 <--> 20.0.0.2:6000 2) UDP/TCP packets when sent from 10.0.0.2:00 --> 10.0.0.1:6000, the RYU controller to make the packet to appear to originate/destined as 20.0.0.1:6000 --> 20.0.0.2:6000 [cid:4F8CB2E3-4858-45C4-A760-A16A69F5C0AC] Appreciate your attention, input and pointers Thanks Regards, Raghavan ----- End forwarded message ----- -- Isaku Yamahata <isa...@gm...> |
From: Isaku Y. <yam...@pr...> - 2016-04-01 18:20:38
|
Forwarding to ryu-devel mailing list. ----- Forwarded message from "HENRYDOSS, JAMES" <JD...@at...> ----- Date: Fri, 1 Apr 2016 16:09:45 +0000 Subject: RYU CONTROLLER Set Up for UCCS SDN Lab Set up Hi Isaku, We need your help. I got your name from the PPT presentation on PyCon APAC 2013 September 14, "Topic Ryu SDN Framework". I have RYU controller installed on my SDN controller machine and trying to connect to the NetFPGA based Open Flow switch. Our OFLow Switch version is 1.1. We are able to connect to FloodLight and POX controllers but RYU Controller is not connecting to OFLOW Version 1.0. Is there any configuration missing in our SDN-C to connect to OFLOW Switch 1.0 verion? Thanks in advance. I am looking forward to speak to you and learn the SDN aspects and experience you have pioneered. Thanks & Regards, James Henrydoss Principal Member Technical AT&T - OC&ATS Operational Certification and Advanced Technical Support Atlanta, GA. Desk: (404) 499-6293 Mobile:(404) 345-2524 Email:jd...@at...<mailto:jd...@at...> [cid:image001.jpg@01CF5349.02A68820] ----- End forwarded message ----- -- Isaku Yamahata <isa...@gm...> |
From: Iwase Y. <iwa...@gm...> - 2016-04-05 02:23:48
|
Hi, Currently, Ryu does not support OpenFlow version 1.1. Ryu supports 1.0, 1.2, 1.3, 1.4 and 1.5 now. http://ryu.readthedocs.org/en/latest/getting_started.html#what-s-ryu AFAIK, OpenFlow 1.0 and 1.3 seem to be more popular among developers. How about using OpenFlow 1.3? Thanks On 2016年04月02日 03:00, Isaku Yamahata wrote: > Forwarding to ryu-devel mailing list. > > ----- Forwarded message from "HENRYDOSS, JAMES" <JD...@at...> ----- > > Date: Fri, 1 Apr 2016 16:09:45 +0000 > Subject: RYU CONTROLLER Set Up for UCCS SDN Lab Set up > > Hi Isaku, > > We need your help. I got your name from the PPT presentation on PyCon APAC 2013 September 14, "Topic Ryu SDN Framework". > > I have RYU controller installed on my SDN controller machine and trying to connect to the NetFPGA based Open Flow switch. Our OFLow Switch version is 1.1. > > We are able to connect to FloodLight and POX controllers but RYU Controller is not connecting to OFLOW Version 1.0. > > Is there any configuration missing in our SDN-C to connect to OFLOW Switch 1.0 verion? > > Thanks in advance. I am looking forward to speak to you and learn the SDN aspects and experience you have pioneered. > > Thanks & Regards, > James Henrydoss > Principal Member Technical > AT&T - OC&ATS > Operational Certification and Advanced Technical Support > Atlanta, GA. > Desk: (404) 499-6293 Mobile:(404) 345-2524 > Email:jd...@at...<mailto:jd...@at...> > [cid:image001.jpg@01CF5349.02A68820] > > > > > ----- End forwarded message ----- > |
From: HENRYDOSS, J. <JD...@at...> - 2016-04-05 11:50:18
Attachments:
Test2RYU.pcap
|
Hi Iwase, Thanks for the quick feedback. Sorry there was a small typo in my problem statement. Actually, we are using NetFPGA based OpenFlow 1.0 based switch and not 1.1. I have attached the PCAP trace for your reference. The switch sends the OPFT_Hello and the controller responds with version not supported. Kindly, let us know whether we need to configure anything at the RYU controller end to interface with OF switch 1.0. We need your help and I would like to see whether we can have a troubleshooting session with you if possible. Thanks & Regards James Henrydoss -----Original Message----- From: Iwase Yusuke [mailto:iwa...@gm...] Sent: Monday, April 04, 2016 10:24 PM To: HENRYDOSS, JAMES <JD...@at...> Cc: ryu...@li... Subject: Re: [Ryu-devel] FWD:[RYU CONTROLLER Set Up for UCCS SDN Lab Set up] Hi, Currently, Ryu does not support OpenFlow version 1.1. Ryu supports 1.0, 1.2, 1.3, 1.4 and 1.5 now. http://ryu.readthedocs.org/en/latest/getting_started.html#what-s-ryu AFAIK, OpenFlow 1.0 and 1.3 seem to be more popular among developers. How about using OpenFlow 1.3? Thanks On 2016年04月02日 03:00, Isaku Yamahata wrote: > Forwarding to ryu-devel mailing list. > > ----- Forwarded message from "HENRYDOSS, JAMES" <JD...@at...> ----- > > Date: Fri, 1 Apr 2016 16:09:45 +0000 > Subject: RYU CONTROLLER Set Up for UCCS SDN Lab Set up > > Hi Isaku, > > We need your help. I got your name from the PPT presentation on PyCon APAC 2013 September 14, "Topic Ryu SDN Framework". > > I have RYU controller installed on my SDN controller machine and trying to connect to the NetFPGA based Open Flow switch. Our OFLow Switch version is 1.1. > > We are able to connect to FloodLight and POX controllers but RYU Controller is not connecting to OFLOW Version 1.0. > > Is there any configuration missing in our SDN-C to connect to OFLOW Switch 1.0 verion? > > Thanks in advance. I am looking forward to speak to you and learn the SDN aspects and experience you have pioneered. > > Thanks & Regards, > James Henrydoss > Principal Member Technical > AT&T - OC&ATS > Operational Certification and Advanced Technical Support > Atlanta, GA. > Desk: (404) 499-6293 Mobile:(404) 345-2524 > Email:jd...@at...<mailto:jd...@at...> > [cid:image001.jpg@01CF5349.02A68820] > > > > > ----- End forwarded message ----- > |
From: Iwase Y. <iwa...@gm...> - 2016-04-06 00:56:06
|
Hi, I checked your pcap file. It seems that Ryu sent OFPT_HELLO message with OpenFlow 1.2. How about specifying OpenFlow version in your RyuApp as follows? https://github.com/osrg/ryu/blob/master/ryu/app/simple_switch.py#L33 Thanks, Iwase On 2016年04月05日 18:16, HENRYDOSS, JAMES wrote: > Hi Iwase, > > Thanks for the quick feedback. Sorry there was a small typo in my problem statement. Actually, we are using NetFPGA based OpenFlow 1.0 based switch and not 1.1. > > I have attached the PCAP trace for your reference. > > The switch sends the OPFT_Hello and the controller responds with version not supported. Kindly, let us know whether we need to configure anything at the RYU controller end to interface with OF switch 1.0. > > We need your help and I would like to see whether we can have a troubleshooting session with you if possible. > > Thanks & > Regards > James Henrydoss > > > -----Original Message----- > From: Iwase Yusuke [mailto:iwa...@gm...] > Sent: Monday, April 04, 2016 10:24 PM > To: HENRYDOSS, JAMES <JD...@at...> > Cc: ryu...@li... > Subject: Re: [Ryu-devel] FWD:[RYU CONTROLLER Set Up for UCCS SDN Lab Set up] > > Hi, > > Currently, Ryu does not support OpenFlow version 1.1. > Ryu supports 1.0, 1.2, 1.3, 1.4 and 1.5 now. > http://ryu.readthedocs.org/en/latest/getting_started.html#what-s-ryu > > AFAIK, OpenFlow 1.0 and 1.3 seem to be more popular among developers. > How about using OpenFlow 1.3? > > Thanks > > On 2016年04月02日 03:00, Isaku Yamahata wrote: >> Forwarding to ryu-devel mailing list. >> >> ----- Forwarded message from "HENRYDOSS, JAMES" <JD...@at...> ----- >> >> Date: Fri, 1 Apr 2016 16:09:45 +0000 >> Subject: RYU CONTROLLER Set Up for UCCS SDN Lab Set up >> >> Hi Isaku, >> >> We need your help. I got your name from the PPT presentation on PyCon APAC 2013 September 14, "Topic Ryu SDN Framework". >> >> I have RYU controller installed on my SDN controller machine and trying to connect to the NetFPGA based Open Flow switch. Our OFLow Switch version is 1.1. >> >> We are able to connect to FloodLight and POX controllers but RYU Controller is not connecting to OFLOW Version 1.0. >> >> Is there any configuration missing in our SDN-C to connect to OFLOW Switch 1.0 verion? >> >> Thanks in advance. I am looking forward to speak to you and learn the SDN aspects and experience you have pioneered. >> >> Thanks & Regards, >> James Henrydoss >> Principal Member Technical >> AT&T - OC&ATS >> Operational Certification and Advanced Technical Support >> Atlanta, GA. >> Desk: (404) 499-6293 Mobile:(404) 345-2524 >> Email:jd...@at...<mailto:jd...@at...> >> [cid:image001.jpg@01CF5349.02A68820] >> >> >> >> >> ----- End forwarded message ----- >> >> >> >> ------------------------------------------------------------------------------ >> >> >> _______________________________________________ >> Ryu-devel mailing list >> Ryu...@li... >> https://lists.sourceforge.net/lists/listinfo/ryu-devel |
From: HENRYDOSS, J. <JD...@at...> - 2016-04-06 03:40:55
|
Hi Iwase, Thanks for the suggestion. I changed from OpenFlow 1.2 to OpenFlow 1.0. It worked. Now our controller connects to OpenFlow Switch. Best Regards James Henrydoss -----Original Message----- From: Iwase Yusuke [mailto:iwa...@gm...] Sent: Tuesday, April 05, 2016 8:56 PM To: HENRYDOSS, JAMES <JD...@at...> Cc: ryu...@li...; jhe...@UC...; sc...@UC... Subject: Re: [Ryu-devel] FWD:[RYU CONTROLLER Set Up for UCCS SDN Lab Set up] Hi, I checked your pcap file. It seems that Ryu sent OFPT_HELLO message with OpenFlow 1.2. How about specifying OpenFlow version in your RyuApp as follows? https://github.com/osrg/ryu/blob/master/ryu/app/simple_switch.py#L33 Thanks, Iwase On 2016年04月05日 18:16, HENRYDOSS, JAMES wrote: > Hi Iwase, > > Thanks for the quick feedback. Sorry there was a small typo in my problem statement. Actually, we are using NetFPGA based OpenFlow 1.0 based switch and not 1.1. > > I have attached the PCAP trace for your reference. > > The switch sends the OPFT_Hello and the controller responds with version not supported. Kindly, let us know whether we need to configure anything at the RYU controller end to interface with OF switch 1.0. > > We need your help and I would like to see whether we can have a troubleshooting session with you if possible. > > Thanks & > Regards > James Henrydoss > > > -----Original Message----- > From: Iwase Yusuke [mailto:iwa...@gm...] > Sent: Monday, April 04, 2016 10:24 PM > To: HENRYDOSS, JAMES <JD...@at...> > Cc: ryu...@li... > Subject: Re: [Ryu-devel] FWD:[RYU CONTROLLER Set Up for UCCS SDN Lab Set up] > > Hi, > > Currently, Ryu does not support OpenFlow version 1.1. > Ryu supports 1.0, 1.2, 1.3, 1.4 and 1.5 now. > http://ryu.readthedocs.org/en/latest/getting_started.html#what-s-ryu > > AFAIK, OpenFlow 1.0 and 1.3 seem to be more popular among developers. > How about using OpenFlow 1.3? > > Thanks > > On 2016年04月02日 03:00, Isaku Yamahata wrote: >> Forwarding to ryu-devel mailing list. >> >> ----- Forwarded message from "HENRYDOSS, JAMES" <JD...@at...> ----- >> >> Date: Fri, 1 Apr 2016 16:09:45 +0000 >> Subject: RYU CONTROLLER Set Up for UCCS SDN Lab Set up >> >> Hi Isaku, >> >> We need your help. I got your name from the PPT presentation on PyCon APAC 2013 September 14, "Topic Ryu SDN Framework". >> >> I have RYU controller installed on my SDN controller machine and trying to connect to the NetFPGA based Open Flow switch. Our OFLow Switch version is 1.1. >> >> We are able to connect to FloodLight and POX controllers but RYU Controller is not connecting to OFLOW Version 1.0. >> >> Is there any configuration missing in our SDN-C to connect to OFLOW Switch 1.0 verion? >> >> Thanks in advance. I am looking forward to speak to you and learn the SDN aspects and experience you have pioneered. >> >> Thanks & Regards, >> James Henrydoss >> Principal Member Technical >> AT&T - OC&ATS >> Operational Certification and Advanced Technical Support >> Atlanta, GA. >> Desk: (404) 499-6293 Mobile:(404) 345-2524 >> Email:jd...@at...<mailto:jd...@at...> >> [cid:image001.jpg@01CF5349.02A68820] >> >> >> >> >> ----- End forwarded message ----- >> >> >> >> ------------------------------------------------------------------------------ >> >> >> _______________________________________________ >> Ryu-devel mailing list >> Ryu...@li... >> https://lists.sourceforge.net/lists/listinfo/ryu-devel |
From: Isaku Y. <isa...@gm...> - 2016-04-22 21:53:36
|
----- Forwarded message from "Malekloo, Ashkan" <ASH...@UC...> ----- Date: Fri, 22 Apr 2016 20:27:53 +0000 Subject: Adding queue to a switch using RYU QoS x-mailer: Apple Mail (2.3124) Hello, Hope you are doing well. I am using Ryu QoS on ubuntu 14.04 and mininet 2.2.1 All I've done is use the exact commands as said in the RYU SDN Framework book. and after this command: curl -X POST -d '{"match": {"ip_dscp": "26"}, "actions":{"queue": "1"}}' http://localhost:8080/qos/rules/0000000000000001 I gtt this error: Invalid rule parameter So, I've restarted everything then I tried Qos per-flow. like before I used ecaxt command as RYU SDN Framework book. After this command: curl -X POST -d '{"match": {"nw_dst": "10.0.0.1", "nw_proto": "UDP", "tp_dst": "5002"}, "actions":{"queue": "1"}}' http://localhost:8080/qos/rules/0000000000000001 I’ve got the exact same error as before: Invalid rule parameter on the other hand, when I use "mark" in my actions command it easily adds the rule and I can confirm it using get. can you help me please solve this? Thank you in advance! ----- End forwarded message ----- -- Isaku Yamahata <isa...@gm...> |
From: Iwase Y. <iwa...@gm...> - 2016-04-25 00:55:27
|
Hi, On 2016年04月23日 06:53, Isaku Yamahata wrote: > ----- Forwarded message from "Malekloo, Ashkan" <ASH...@UC...> ----- > > Date: Fri, 22 Apr 2016 20:27:53 +0000 > Subject: Adding queue to a switch using RYU QoS > x-mailer: Apple Mail (2.3124) > > Hello, > Hope you are doing well. > > I am using Ryu QoS on ubuntu 14.04 and mininet 2.2.1 > > All I've done is use the exact commands as said in the RYU SDN Framework book. and after this command: > curl -X POST -d '{"match": {"ip_dscp": "26"}, "actions":{"queue": "1"}}' http://localhost:8080/qos/rules/0000000000000001 > > I gtt this error: > Invalid rule parameter > > So, I've restarted everything then I tried Qos per-flow. like before I used ecaxt command as RYU SDN Framework book. After this command: > curl -X POST -d '{"match": {"nw_dst": "10.0.0.1", "nw_proto": "UDP", "tp_dst": "5002"}, "actions":{"queue": "1"}}' http://localhost:8080/qos/rules/0000000000000001 > > I’ve got the exact same error as before: > Invalid rule parameter A "numeric string" like {"queue": "1"} causes this problem. First, please try with non-string number like {"queue": 1}. To fix this problem, I wrote the following patch, but please note this patch is under reviewing in our team. >From 5bb93cca1dd5747be854737c6b78f8c2bb4f7532 Mon Sep 17 00:00:00 2001 From: IWASE Yusuke <iwa...@gm...> Date: Thu, 7 Apr 2016 11:46:00 +0900 Subject: [PATCH] ofctl_utils: Enhance user value conversion Currently, OFCtlUtil._reserved_num_from_user() fails to convert an user specified value when it is a numeric string. This patch enhances this conversion to enable to convert an user value as follows. e.g.) - Integer: 1 -> 1 - Numeric string: "1" -> 1 - Reserved number: "OFPP_ANY" -> 0xffffffff - Invalid value: "foobar" -> "foobar" (do not conversion) Signed-off-by: IWASE Yusuke <iwa...@gm...> --- ryu/lib/ofctl_utils.py | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/ryu/lib/ofctl_utils.py b/ryu/lib/ofctl_utils.py index b5fbc9b..832baf0 100644 --- a/ryu/lib/ofctl_utils.py +++ b/ryu/lib/ofctl_utils.py @@ -240,13 +240,18 @@ def __init__(self, ofproto): 'OFPQCFC_EPERM'] def _reserved_num_from_user(self, num, prefix): - if isinstance(num, int): - return num - else: - if num.startswith(prefix): - return getattr(self.ofproto, num) - else: - return getattr(self.ofproto, prefix + num.upper()) + try: + return str_to_int(num) + except ValueError: + try: + if num.startswith(prefix): + return getattr(self.ofproto, num.upper()) + else: + return getattr(self.ofproto, prefix + num.upper()) + except AttributeError: + LOG.warning( + "Cannot convert argument to reserved number: %s", num) + return num def _reserved_num_to_user(self, num, prefix): for k, v in self.ofproto.__dict__.items(): Thanks, Iwase > > on the other hand, when I use "mark" in my actions command it easily adds the rule and I can confirm it using get. > > can you help me please solve this? > Thank you in advance! > > ----- End forwarded message ----- > |
From: Malekloo, A. <ASH...@UC...> - 2016-04-25 06:42:53
|
Hi, Thanks for your response. I would appreciate if could help me on something else. I have a scenario in which I want to change the third scenario of RYU SDN Framework book QoS chapter that described the Meter based QoS. In my scenario I have two queues, EF and AF, on my switches. On the starting node of my flows I want to check these queues and see whether the delay (or rate) of my EF queue degraded or not. If it is the case I want to remark the flows that relates to EF to AF until the EF queue delay gets back to its normal condition. Considering the aforementioned scenario, 1) Can I implement this scenario using just the rules of meter? If so please kindly help me find the right rules to help me achieve this. 2) otherwise, if you think I need to change the source code, what is the appropriate source code module that I need to manipulate. Thanking you in advance, Ashkan On Ordibehesht 6, 1395 AP, at 5:25 AM, Iwase Yusuke <iwa...@gm...<mailto:iwa...@gm...>> wrote: Hi, On 2016年04月23日 06:53, Isaku Yamahata wrote: ----- Forwarded message from "Malekloo, Ashkan" <ASH...@UC...<mailto:ASH...@uc...>> ----- Date: Fri, 22 Apr 2016 20:27:53 +0000 Subject: Adding queue to a switch using RYU QoS x-mailer: Apple Mail (2.3124) Hello, Hope you are doing well. I am using Ryu QoS on ubuntu 14.04 and mininet 2.2.1 All I've done is use the exact commands as said in the RYU SDN Framework book. and after this command: curl -X POST -d '{"match": {"ip_dscp": "26"}, "actions":{"queue": "1"}}' http://localhost:8080/qos/rules/0000000000000001 I gtt this error: Invalid rule parameter So, I've restarted everything then I tried Qos per-flow. like before I used ecaxt command as RYU SDN Framework book. After this command: curl -X POST -d '{"match": {"nw_dst": "10.0.0.1", "nw_proto": "UDP", "tp_dst": "5002"}, "actions":{"queue": "1"}}' http://localhost:8080/qos/rules/0000000000000001 I’ve got the exact same error as before: Invalid rule parameter A "numeric string" like {"queue": "1"} causes this problem. First, please try with non-string number like {"queue": 1}. To fix this problem, I wrote the following patch, but please note this patch is under reviewing in our team. From 5bb93cca1dd5747be854737c6b78f8c2bb4f7532 Mon Sep 17 00:00:00 2001 From: IWASE Yusuke <iwa...@gm...<mailto:iwa...@gm...>> Date: Thu, 7 Apr 2016 11:46:00 +0900 Subject: [PATCH] ofctl_utils: Enhance user value conversion Currently, OFCtlUtil._reserved_num_from_user() fails to convert an user specified value when it is a numeric string. This patch enhances this conversion to enable to convert an user value as follows. e.g.) - Integer: 1 -> 1 - Numeric string: "1" -> 1 - Reserved number: "OFPP_ANY" -> 0xffffffff - Invalid value: "foobar" -> "foobar" (do not conversion) Signed-off-by: IWASE Yusuke <iwa...@gm...<mailto:iwa...@gm...>> --- ryu/lib/ofctl_utils.py | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/ryu/lib/ofctl_utils.py b/ryu/lib/ofctl_utils.py index b5fbc9b..832baf0 100644 --- a/ryu/lib/ofctl_utils.py +++ b/ryu/lib/ofctl_utils.py @@ -240,13 +240,18 @@ def __init__(self, ofproto): 'OFPQCFC_EPERM'] def _reserved_num_from_user(self, num, prefix): - if isinstance(num, int): - return num - else: - if num.startswith(prefix): - return getattr(self.ofproto, num) - else: - return getattr(self.ofproto, prefix + num.upper()) + try: + return str_to_int(num) + except ValueError: + try: + if num.startswith(prefix): + return getattr(self.ofproto, num.upper()) + else: + return getattr(self.ofproto, prefix + num.upper()) + except AttributeError: + LOG.warning( + "Cannot convert argument to reserved number: %s", num) + return num def _reserved_num_to_user(self, num, prefix): for k, v in self.ofproto.__dict__.items(): Thanks, Iwase on the other hand, when I use "mark" in my actions command it easily adds the rule and I can confirm it using get. can you help me please solve this? Thank you in advance! ----- End forwarded message ----- |
From: Iwase Y. <iwa...@gm...> - 2016-04-25 07:55:33
|
Hi, On 2016年04月25日 15:08, Malekloo, Ashkan wrote: > Hi, > > Thanks for your response. > > I would appreciate if could help me on something else. I have a scenario in which I want to change the third scenario of RYU SDN Framework book QoS chapter that described the Meter based QoS. In my scenario I have two queues, EF and AF, on my switches. On the starting node of my flows I want to check these queues and see whether the delay (or rate) of my EF queue degraded or not. If it is the case I want to remark the flows that relates to EF to AF until the EF queue delay gets back to its normal condition. > > Considering the aforementioned scenario, If you could configure queues for AF and EF, I think you should map DSCP value to these queues first, then, install QoS rules. e.g.) ========== ==== ======== ======== (Priority) DSCP Queue ID (QoS ID) ========== ==== ======== ======== 1 BE 1 1 1 EF 2 2 ========== ==== ======== ======== In "Example of the operation of QoS by using Meter Table", the bandwidth of the traffic s1->h1 is separated by the queues of s1. So, I think whether the delay (or rate) of EF queue degraded or not are depending on the s1 queues setting. > > 1) Can I implement this scenario using just the rules of meter? If so please kindly help me find the right rules to help me achieve this. I think you can. Please refer to the following API reference. http://osrg.github.io/ryu-book/en/html/rest_qos.html#set-a-qos-rule Thanks, Iwase > 2) otherwise, if you think I need to change the source code, what is the appropriate source code module that I need to manipulate. > > Thanking you in advance, > Ashkan > > >> On Ordibehesht 6, 1395 AP, at 5:25 AM, Iwase Yusuke <iwa...@gm... <mailto:iwa...@gm...>> wrote: >> >> Hi, >> >> On 2016年04月23日 06:53, Isaku Yamahata wrote: >>> ----- Forwarded message from "Malekloo, Ashkan" <ASH...@UC... <mailto:ASH...@uc...>> ----- >>> >>> Date: Fri, 22 Apr 2016 20:27:53 +0000 >>> Subject: Adding queue to a switch using RYU QoS >>> x-mailer: Apple Mail (2.3124) >>> >>> Hello, >>> Hope you are doing well. >>> >>> I am using Ryu QoS on ubuntu 14.04 and mininet 2.2.1 >>> >>> All I've done is use the exact commands as said in the RYU SDN Framework book. and after this command: >>> curl -X POST -d '{"match": {"ip_dscp": "26"}, "actions":{"queue": "1"}}' http://localhost:8080/qos/rules/0000000000000001 >>> >>> I gtt this error: >>> Invalid rule parameter >>> >>> So, I've restarted everything then I tried Qos per-flow. like before I used ecaxt command as RYU SDN Framework book. After this command: >>> curl -X POST -d '{"match": {"nw_dst": "10.0.0.1", "nw_proto": "UDP", "tp_dst": "5002"}, "actions":{"queue": "1"}}' http://localhost:8080/qos/rules/0000000000000001 >>> >>> I’ve got the exact same error as before: >>> Invalid rule parameter >> >> A "numeric string" like {"queue": "1"} causes this problem. >> First, please try with non-string number like {"queue": 1}. >> >> To fix this problem, I wrote the following patch, >> but please note this patch is under reviewing in our team. >> >> >> From 5bb93cca1dd5747be854737c6b78f8c2bb4f7532 Mon Sep 17 00:00:00 2001 >> From: IWASE Yusuke <iwa...@gm... <mailto:iwa...@gm...>> >> Date: Thu, 7 Apr 2016 11:46:00 +0900 >> Subject: [PATCH] ofctl_utils: Enhance user value conversion >> >> Currently, OFCtlUtil._reserved_num_from_user() fails to convert >> an user specified value when it is a numeric string. >> This patch enhances this conversion to enable to convert an user >> value as follows. >> >> e.g.) >> - Integer: 1 -> 1 >> - Numeric string: "1" -> 1 >> - Reserved number: "OFPP_ANY" -> 0xffffffff >> - Invalid value: "foobar" -> "foobar" (do not conversion) >> >> Signed-off-by: IWASE Yusuke <iwa...@gm... <mailto:iwa...@gm...>> >> --- >> ryu/lib/ofctl_utils.py | 19 ++++++++++++------- >> 1 file changed, 12 insertions(+), 7 deletions(-) >> >> diff --git a/ryu/lib/ofctl_utils.py b/ryu/lib/ofctl_utils.py >> index b5fbc9b..832baf0 100644 >> --- a/ryu/lib/ofctl_utils.py >> +++ b/ryu/lib/ofctl_utils.py >> @@ -240,13 +240,18 @@ def __init__(self, ofproto): >> 'OFPQCFC_EPERM'] >> >> def _reserved_num_from_user(self, num, prefix): >> - if isinstance(num, int): >> - return num >> - else: >> - if num.startswith(prefix): >> - return getattr(self.ofproto, num) >> - else: >> - return getattr(self.ofproto, prefix + num.upper()) >> + try: >> + return str_to_int(num) >> + except ValueError: >> + try: >> + if num.startswith(prefix): >> + return getattr(self.ofproto, num.upper()) >> + else: >> + return getattr(self.ofproto, prefix + num.upper()) >> + except AttributeError: >> + LOG.warning( >> + "Cannot convert argument to reserved number: %s", num) >> + return num >> >> def _reserved_num_to_user(self, num, prefix): >> for k, v in self.ofproto.__dict__.items(): >> >> >> >> Thanks, >> Iwase >> >> >>> >>> on the other hand, when I use "mark" in my actions command it easily adds the rule and I can confirm it using get. >>> >>> can you help me please solve this? >>> Thank you in advance! >>> >>> ----- End forwarded message ----- > > > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications Manager > Applications Manager provides deep performance insights into multiple tiers of > your business applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > > > > _______________________________________________ > Ryu-devel mailing list > Ryu...@li... > https://lists.sourceforge.net/lists/listinfo/ryu-devel > |