On Jul 14, 2010, at 11:27 AM, Jens Brunsen wrote: > What we now need is something to define a fix VIF to port relation or > anything similar. Also persistent ports could be something possible. I cannot > believe that this is not possible. Can you deliver or show me a function that > can resolve this issue?
We don't have any way to maintain state about ports across reboots, since XenServer expects to completely destroy and recreate these ports from scratch. This sort of state would have to be stored in the XAPI database, which we can't query at port creation time due to timing constraints in XenServer's networking scripts. I believe these same sorts of issues would even be present with the bridge, since XenServer isn't consistent with the VIF names it uses across reboots. Regardless of the practical limitations, OpenFlow is really designed to be used with a controller, which would have enough context to push the kinds of flows that you are trying to generate statically. You could script a program to monitor changes to the "Interface" table in ovsdb-server and have it rewrite your flows. Another alternative would be to modify the XenServer "vif" script to setup the flows, since it has enough context and is called on port creation and destruction. Looking at the flows you are generating, it appears that you are attempting to do some sort of port isolation. We are currently designing native support for this and hope to have it added before long. If you'd be interested in taking part in the design discussion, please let us know. --Justin _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
