[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openvswitch-discuss
Subject:    [ovs-discuss] Regarding parsing controller message to OVS
From:       jpettit () nicira ! com (Justin Pettit)
Date:       2012-10-30 16:33:11
Message-ID: 1A87C438-F7DA-451A-91EC-8F6B7E2F9327 () nicira ! com
[Download RAW message or body]

In the example you've given, the kernel datapath would execute the actions.  However, \
ovs-vswitchd would figure out which OpenFlow rule would be best for the kernel \
datapath to execute for a particular packet.  None of this is specific to a \
controller, though; it doesn't matter whether the controller added that flow or a \
userspace utility like ovs-ofctl.

You may want to look at this presentation from the openvswitch.org website, which \
describes the high-level components and their responsibilities:

	http://openvswitch.org/slides/OVS-Overview-110303.pdf

--Justin


On Oct 30, 2012, at 8:25 AM, Arshad <heyarshad at gmail.com> wrote:

> Hello Ben,
> 
> Thank you for your mail. 
> 
> We need to know what OVS code is being used to process the actions field in the \
> controller. 
> For example;
> 
> When a controller send a message to the OVS, \
> "ip,in_port=1,nw_dst=192.168.10.34,idle_timeout=0,actions=enqueue:3:1", in the OVS, \
> what program will be running to process this "actions". 
> Thanks!
> 
> Regards,
> 
> Arshad Adam
> 
> On Mon, Oct 29, 2012 at 11:18 AM, Ben Pfaff <blp at nicira.com> wrote:
> On Mon, Oct 29, 2012 at 10:43:40AM -0500, Arshad wrote:
> > We need some help in finding the information regarding parsing the message
> > from controller to the OpenvSwitch.
> > 
> > For example; Controller send the message to switch.. Something like this..
> > "ip,in_port=1,nw_dst=192.168.10.34,idle_timeout=0,actions=enqueue:3:1"
> 
> What kind of information are you looking for?
> 
> _______________________________________________
> discuss mailing list
> discuss at openvswitch.org
> http://openvswitch.org/mailman/listinfo/discuss


[prev in list] [next in list] [prev in thread] [next in thread]