On Fri, Feb 03, 2012 at 09:21:29AM -0800, Ben Pfaff wrote:
> My understanding is that ordinary Linux bridges don't work that way
> with the RHEL network scripts. Is that correct? I think that it is
> a good idea for OVS and the Linux bridge to act the same way, to the
> extent that it is possible
On Fri, Feb 03, 2012 at 09:37:18AM -0800, Gurucharan Shetty wrote:
> >
> >
> > Guru, should we make that change? I suggested a comma originally
> > because I though it would be easier to write the shell fragments (no
> > need for quotes) but I didn't realize that there was precedent for
> > spaces
>
>
> Guru, should we make that change? I suggested a comma originally
> because I though it would be easier to write the shell fragments (no
> need for quotes) but I didn't realize that there was precedent for
> spaces.
>
> For consistency, it may be a good idea. I will come up with the patch for
On Fri, Feb 03, 2012 at 04:30:36PM +0400, Alexey I. Froloff wrote:
> On Tue, Jan 31, 2012 at 01:53:49PM -0800, Gurucharan Shetty wrote:
> > + case ${OVSDHCPINTERFACES} in
> > + ${OVSINTF#ifcfg-} | \
> > + "${OVSINTF#ifcfg-},"* |
On Tue, Jan 31, 2012 at 01:53:49PM -0800, Gurucharan Shetty wrote:
> + case ${OVSDHCPINTERFACES} in
> + ${OVSINTF#ifcfg-} | \
> + "${OVSINTF#ifcfg-},"* | \
> + *",${OVSINTF#ifcfg-}" | \
> +
On Tue, Jan 31, 2012 at 01:53:49PM -0800, Gurucharan Shetty wrote:
> The current network-script, ifup-ovs does not work well if you
> enable DHCP on the OVS. It will work if we name the bridge
> alphabetically greater than the underlying physical interfaces.
> Even then, it will do multiple DHCP a
The current network-script, ifup-ovs does not work well if you
enable DHCP on the OVS. It will work if we name the bridge
alphabetically greater than the underlying physical interfaces.
Even then, it will do multiple DHCP attempts slowing down the boot
up process.
This patch allows DHCP on an OVS
