Hi Wayne-
Why not just tell OVS to connect to Beacon and use all the machinery
already in place? Here is a script I run on our XenServers to tell OVS
to connect to Beacon on startup (run from rc.local):
#!/bin/bash
ovs-vsctl set-controller xenbr0
ovs-vsctl set-fail-mode xenbr0 standalone
ovs-vsctl set-controller xenbr0 tcp:192.168.1.11:6633
In Beacon you would then create your own bundle(s) that implement the
functionality you want by adding event handlers. There is a brief
tutorial available at
https://openflow.stanford.edu/display/Beacon/Your+First+Bundle that
should get you started. If you need to do things when a switch
connects/disconnects there are listeners available on the
IBeaconProvider class, as well as the ability to listen for any incoming
OpenFlow message from switches.
Hope that helps.
-David
On 6/27/2011 11:12 PM, Wei-Chih Chen wrote:
Dear all and David,
I am using Xen Cloud Platform (*XCP*), which includes *Open vSwitch*.
Now I would like to use *Beacon* to control Open vSwitch through
OpenFlow protocol.
All tests in Beacon adopt Easy Mock, and I have no idea how to connect
to a real OpenFlow switch (although Open vSwitch is virtual).
The following are steps I think:
1. new an OFSwitch object, /ofSwitch/.
2. Create and new a connection of SocketChannel, /socket/, and set it
to sockectChannel field of /ofSwitch/.
3. Set inStream, outStream, ports fields of OFSwitch
After these steps (perhaps not quite correct), I think I can control
Open vSwitch through ofSwitch.
If successfully connecting to it, I would like to setup *VLAN*s for
VMs on XCP.
This may include create virtual bridges, set VLAN tags ....
Could anyone give more details or examples?
Thanks!
Regards,
Wayne
_______________________________________________
openflow-discuss mailing list
[email protected]
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
_______________________________________________
openflow-discuss mailing list
[email protected]
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
