[ovs-dev] asking the example to use openflow protocol to limit the flow rate in openvswitch

trinh tri no8bk at yahoo.com
Thu Jun 28 14:51:20 UTC 2012


Dear Mr Justin!

Yep! I want to connect openvswitch to NOX and let NOX dynamically control the bandwidth providing to each flow.
I viewed from some website, they use this command for the openvswitch to connect to NOX:
./utilities/ovs-openflowd dp0 --datapath-id=0000004E46324304 tcp:192.168.0.100 port 6633 --out-of-band
But in the new version of openvswitch (1.6.1), I cannot find the tool ovs-openflowd. In your last email I think you give me solution of connecting openvswitch to NOX by ovs-ofctl and ovs-vsctl. Could you help me to write what command is equivalant to the above commands?

Thank you very much 
Trinh Minh Tri
-------------------------------------------------
PhD Student, Department of Electrical Engineering
Chulalongkorn University, Bangkok 10330, Thailand.
Phone:0824566602
Email: no8bk at yahoo.com


________________________________
 From: Justin Pettit <jpettit at nicira.com>
To: trinh tri <no8bk at yahoo.com> 
Cc: "dev at openvswitch.org" <dev at openvswitch.org> 
Sent: Thursday, June 28, 2012 12:18 PM
Subject: Re: [ovs-dev] asking the example to use openflow protocol to limit the flow rate in openvswitch
 
What do you mean by hands-on?  From NOX?  I don't think it speaks OVSDB.  I'd probably start off by using ovs-vsctl and ovs-ofctl to manually configure what you want.  Translating from ovs-ofctl to OpenFlow should be pretty straight-forward, since the commands map pretty directly to OpenFlow.  For OVSDB, you could configure ovsdb-server so that you can run ovs-vsctl on the NOX system and connect over TCP/SSL.  Or you could do it programmatically by looking at some of the other programs in the OVS distribution that make use of the database.

--Justin


On Jun 28, 2012, at 1:08 AM, trinh tri wrote:

> Thank you very much Mr. Petit for the prompt reply.
> Do you know any hand-on example to implement that? 
>  
> Trinh Minh Tri
> -------------------------------------------------
> PhD Student, Department of Electrical Engineering
> Chulalongkorn University, Bangkok 10330, Thailand.
> Phone:0824566602
> Email: no8bk at yahoo.com
> From: Justin Pettit <jpettit at nicira.com>
> To: trinh tri <no8bk at yahoo.com> 
> Cc: "dev at openvswitch.org" <dev at openvswitch.org> 
> Sent: Thursday, June 28, 2012 11:49 AM
> Subject: Re: [ovs-dev] asking the example to use openflow protocol to limit the flow rate in openvswitch
> 
> The configuration of QoS is done through the OVSDB protocol, which handle switch-level configuration.  You can then use OpenFlow to direct flows to particular queues that you've configured through OVSDB.  There are C and Python bindings to OVSDB (but I don't think NOX makes use of them) or you can use ovs-vsctl as a CLI interface to OVSDB.
> 
> There's an example of configuring QoS towards the end of the ovs-vsctl man page.  The ovs-ofctl man page describes the enqueue and set_queue actions that can be used to direct flows to the queues you've configured.
> 
> --Justin
> 
> 
> On Jun 28, 2012, at 12:43 AM, trinh tri wrote:
> 
> > Dear openvswitch dev!
> > 
> > I'm trying to implement a system which can dynamically control the flow rate limiting of openvswitch. And would like control that rate from NOX controller via openflow protocol.
> > 
> > Could you suggest me how to implement that system and is there any example about that system to follow? 
>> > Thank you very much
> > Trinh Minh Tri
> > -------------------------------------------------
> > PhD Student, Department of Electrical Engineering
> > Chulalongkorn University, Bangkok 10330, Thailand.
> > Phone:0824566602
> > Email: no8bk at yahoo.com
> > _______________________________________________
> > dev mailing list
> > dev at openvswitch.org
> > http://openvswitch.org/mailman/listinfo/dev
> 
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-dev/attachments/20120628/782b98b2/attachment-0003.html>


More information about the dev mailing list