I have been helping a DevOps group roll out Open vSwitch for isolating pods of Docker containers across hosts using VxLAN without using a separate controller [1]. Although OVS works quite well for their situation, rule persistence seems to be a problem. We rigged chef scripts to regenerate the rules on reboots or periodically (so as to restore rules when OVS segfaulted and restarted).
We believe a cleaner approach will be to preserve some rules within OVSDB and replay them. That way, we don't need a separate rule maintenance mechanism and we're not forced to use a controller solution that may be unnecessarily heavyweight fr this DevOps envrionment. Would the community be willing to accept a schema for persistent flows (Not all flows need to be persistent) and a patch that allows archiving and replaying those rules on startup? Or is there a better approach that folks can suggest? Thanks Srini. [1] LorisPack toolkit for multi-host Docker networking using OVS: http://github.com/lorispack/loris On Thu, Jan 31, 2013 at 10:29 PM, Ben Pfaff <[email protected]> wrote: > On Fri, Feb 01, 2013 at 02:24:07PM +0800, Kris zhang wrote: > > First i created a bridge br0, and then I added some flow entries into br0 > > (for example: ovs-ofctl add-flow br0 dl_vlan=10,action=normal). but i > found > > the flow entries disppearred after i restart the ovs. (i use the command > > ovs-ofctl dump-flows br0). How can i let the flow entries persistence in > > OVS-DB even if the computer reboot? > > The usual way would be to use an OpenFlow controller. If this is the > only feature you need then you can use ovs-controller with the > --with-flows option. > > Also, OVSDB doesn't store flows. > _______________________________________________ > discuss mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/discuss >
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
