On May 2, 2011, at 11:48 PM, David Erickson wrote:
> Ah ok so ovs-vsctl to this management protocol is similar to what dpctl is to
> OpenFlow?
Ye. In OVS, the utilities map as follows:
ovs-vsctl -> ovsdb-server (OVS management protocol)
ovs-ofctl -> ovs-vswitchd (OpenFlow protocol)
ovs-dpctl -> kernel module (NetLink protocol)
> In an ideal XenServer pool what is the envisioned way that an individual
> bridge on a XenServer gets its controller host ip:port, and any other
> configuration set? Is this possible from the pool master? Or do I need to
> just create scripts to set this on each box in rc.local?
You'd either need a manager (or ovs-vsctl acting as a manger) or local
configuration through something like rc.local. Citrix's Distributed Virtual
Switch (DVS), for example, actually speaks the management protocol to configure
OpenFlow, but it's not freely available. However, the Pool Master itself only
speaks XAPI, which doesn't have hooks for setting the controller.
--Justin
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
