On Nov 7, 2010, at 11:07 PM, 张跃 wrote: > In the doc: 'The ovs-vsctl "set-controller" command can also be used in > conjunction with ovs-vswitchd to set the controller for one or more bridges. > We recommend using OpenFlow in this manner and in this case you should not > run ovs-openflowd.' > > Is that means there are two ways to get openflow set up? One is using > ovs-openflowd configured by ovs-dpctl, the other is ovs-vswitchd configured > by ovs-vsctl?
Yes. > If so what is the differences between them? Ovs-vswitchd retrieves its > configuration from database at startup but ovs-openflowd seems not? That is correct. More than that, though, ovs-vswitchd acts like a full-featured switch; it includes capabilities such as native VLAN support, mirroring (SPAN and RSPAN), and visibility (NetFlow and sFlow). ovs-openflowd, is really meant just to be an alternative for the OpenFlow reference implementation; it's just a simple wrapper around our OpenFlow library. > The document "Using Open vSwitch as a Simple OpenFlow Switch" is based on the > ovs-openflowd, is it exactly the same with ovs-vswitchd? As I mention above, ovs-openflowd is meant to just be an alternative for the OpenFlow reference implementation. ovs-vswitchd provides many of the features expected from a more full-featured switch. Both support OpenFlow, though. > And it will be nice if you could give some detailed examples about how to > test and verify if the configuration of openflow works. I'd recommend looking at ovs-controller (in the Open vSwitch distribution) or NOX (http://noxrepo.org). --Justin _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
