[ovs-dev] [PATCH] debian: Add network integration scripts.

Greg Dahlman gdahlman at hotmail.com
Mon May 7 22:17:06 UTC 2012


Note I failed to respond to this part
> I think that you misunderstand when OVS is supposed to start. Here's
> a previous discussion that may clarify:
> http://openvswitch.org/pipermail/discuss/2011-October/005902.html

In my upstart script I am starting after the local-file-systems are mounted, so this is not as early as to require a relocation to /bin and /sbin although I could argue it should be there.
+ start on (local-filesystems and started dbus)stop on stopping dbus
It is similar to what you are doing in the init script, although I think the current init script 
# Required-Start:    $network $local_fs $remote_fs
Note currently the init scripts are starting at the same point as libvirt-bin and that nfs volumes do not mount sometimes, but I think this is also limited to Ubuntu so far.
As I see no reason for the host to not use an ovs interface for the host if you have DRAC/ILOM to access it if the networking doesn't come up.
I understand that it would be difficult to start ovs before root is rw due to the DB needs, but please realize mostly what I am trying to do is offer a script that works with Ubuntu, vs the current init which blocks reboots and causes long boot times if you do dare to go all ovs.
With upstart I can call the scripts early and test for the files under /usr and exit if they aren't there then after mountall sends a  "emit remote-filesystems" I can test again, this would limit the reboot lag to those who have remote /usr directories.
I think it is more likely that people only have static ovs interfaces though, which would be served by starting after the local-filesystems trigger.
dbus will emit a new net device which should call ifup at that point which could be set to start allow-ovs if's.

From: gdahlman at hotmail.comTo: blp at nicira.com
Date: Mon, 7 May 2012 13:24:54 -0700
CC: dev at openvswitch.com
Subject: Re: [ovs-dev] [PATCH] debian: Add network integration scripts.



<!--
.ExternalClass .ecxhmmessage P
{padding:0px;}
.ExternalClass body.ecxhmmessage
{font-size:10pt;font-family:Tahoma;}

-->
Sorry I should have said "if" they move to systemd.  It is very unlikely they will move to upstart.  I should have a better upstart script in a few days.  I just wanted to share one quickly.

I use Ubuntu on my laptop with kvm.  The interfaces scripts make life easier.  Thank you.

> Date: Mon, 7 May 2012 13:11:09 -0700
> From: blp at nicira.com
> To: gdahlman at hotmail.com
> CC: gshetty at nicira.com; dev at openvswitch.com
> Subject: Re: [ovs-dev] [PATCH] debian: Add network integration scripts.
> 
> On Mon, May 07, 2012 at 01:04:10PM -0700, Greg Dahlman wrote:
> > In Debian yes, at least until they move to systemd.
> 
> I think that your assumption that Debian will move to systemd is
> unwarranted.  The choice of init system is currently under discussion
> on debian-devel.  I haven't been closely following it, but from what
> I've read so far I don't have the impression that there is a consensus
> for systemd.
> 
> > In Ubuntu /etc/init.d/openvswitch-switch will be called too late,
> > the db and switch need to be brought up right after dbus starts or
> > you will go into failsafe, this needs to be done for clients that
> > will have /home mounted via nfs or iSCSI.
> 
> I think that you misunderstand when OVS is supposed to start.  Here's
> a previous discussion that may clarify:
>         http://openvswitch.org/pipermail/discuss/2011-October/005902.html
 		 	   		  

_______________________________________________
dev mailing list
dev at openvswitch.org
http://openvswitch.org/mailman/listinfo/dev 		 	   		  


More information about the dev mailing list