[ILUG] Interface startup order RHEL/CentOs

[Andrew McGill]

Howdy AJ,

The canonical way to do anything in rhel/centos that needs to be forced, is to 
call your hacky fix-it-all script from /etc/rc.local.  This runs at the end of 
the startup sequence (unlike the debian equivalent, that runs at the start), 
and it seems to be just the place for all manner of post-hoc fixes that the 
system will not do, or which you cannot convince the "system" to do.  If you 
want to do it before xen, then don't autostart xen, and put that in your 
rc.local as well 

you might end up with something like ...
  for tag in 22 23 24 25 26 27 28 29 30 ; do
  ifup bond0.$tag
  ifup xenvlan$tag
  done
  service xend start
  service xendomains start

You could also move the configuration of the dom's network into the xen 
configuration file, which is actually python script.  As a side effect, this 
hack would guarantee you job security through the next three recessions.  You 
can get bonus job security for getting it to work with selinux in paranoid 
mode.  

&:-)

On Thursday 29 October 2009 17:15:55 AJ McKee wrote:
> Howdy all,
> 
> Quick Q, just incase I've missed something simple here,
>  
> Am running several XEN boxes here all with bonding and vlan tagging
> enabled. As we don't let XEN handle the network side od things we have
> our own bridges defined. So we'd have something like this
> 
> cat ifcfg-bond0.30
> DEVICE=bond0.30
> BOOTPROTO=none
> ONBOOT=yes
> VLAN=yes
> BRIDGE=xenvlan30
> 
> cat ifcfg-xenvlan30
> DEVICE=xenvlan30
> BOOTPROTO=none
> ONBOOT=yes
> TYPE=bridge
> 
> Problem I'm seeing at the moment on one host is that it attempts to
> start the xenvlan30 bridge interface before bond0.30 is available,
> 
> Anyone know of a way to force this in RHEL/CentOs so that the bridge
> won't come up till the actual interface is up?
> 
> 
> TIA
> AJ
>