On Wed, Jan 25, 2012 at 04:54:56PM +0400, Alexey I. Froloff wrote: > On Tue, Jan 24, 2012 at 09:30:15AM -0800, Ben Pfaff wrote: > > Should we skip the "post" call for OVSIntPort? We know that these > > ports are not physical ports, so they will not allow DHCP to complete. > I believe DHCP is allowed on these ports, but you are right - no > need to delay bridge configuration in this particular case. > > > Should we only delay bringing up the bridge port when DHCP is in use? > > It seems nicer to bring up the bridge port immediately if we can. > These scripts are mostly hacks. Open vSwitch support need deeper > integration with initscripts package, which includes > modifications to ifup-eth script. > > Or we could try another solution. For each OVSBridge we should > provide list of physical ports that are added to bridge. > Previously, I didn't like this idea, since you need to maintain > both, the physical port configuration files and list of ports in > bridge config, but we have such list in OVSBond config already...
What if we only added a list of ports that are required to complete DHCP? That would ordinarily be only one port (which might be a bond), and it wouldn't be needed at all if DHCP was not in use. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
