On Mon, Jan 20, 2014 at 10:56 PM, Schlacta, Christ <aarc...@aarcane.org> wrote: > I have some unruly virtual machines that don't like to shut down when > requested. This results in vnetn being left connected to openvswitch at the > end of the day. This wouldn't be so bad, except that when the host comes > up, the virtualmachines unlucky enough to need devices numbered equal to or > greater than n don't start. Is there some way to tell openvswitch what the > configuration should look like at boot, and have it actively remove or not > add the unwanted devices? I'm thinking it should be as easy as ovs-vsctl > save-as-initial-config or something like that.. This is one of the few > remaining sticking points preventing my entire cluster of systems from > working perfectly right now.
If you configure your bridges through OVS ifcfg-* scripts (or interfaces if debian/ubuntu), the bridges are deleted and re-created during the reboot. Would that help (assuming that adding virtual interfaces is done separately during every boot)? Are you using libvirt? If so, do they re-add vif interfaces during every boot? > > thank you in advance for an answer to this curious conundrum. > > _______________________________________________ > discuss mailing list > discuss@openvswitch.org > http://openvswitch.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
