[ovs-dev] [suse 1/7] xenserver: Add LSB init info to scripts.
Patrick Mullaney
pm.mullaney at gmail.com
Thu Dec 30 21:41:23 UTC 2010
I'm all for bringing them closer together. This is an area where there
could be some distro specific differences. My main goal was to get
something for the LSB headers into this script. This one can be
xenserver specific.
The description fields can be the same. Lets take the debian ones. I'm
not sure about using the runlevel 4 in my suse specific script but
I can patch that in my rpm for now.
As as side note, I ran into a problem with this since I posted this
patch. It seems I need to have "# Required-Start: $local_fs" so that
openvswitch will start before network(and not in parallel with it). This
enforces that openvswitch comes up before the network config is applied.
The network config(ifcfg on suse) can include existing bridge
configuration. This ordering is an area where there may be some
distro differences also.
The next problem that using local_fs above causes is that many of
the ovs utilities are installed in /usr(this is the remote_fs). It would
be nice to variablize this is the spec. I'll look into this when I get
the chance.
I'm curious - do we have the same issue with xenserver/centos?
On Tue, 2010-12-28 at 10:59 -0800, Justin Pettit wrote:
> On Dec 15, 2010, at 11:18 AM, Ben Pfaff wrote:
>
> > +### BEGIN INIT INFO
> > +# Provides: vswitch
> > +# Required-Start: $remote_fs
> > +# Required-Stop: $remote_fs
> > +# Default-Start: 2 3 5
> > +# Default-Stop:
> > +# Short-Description: vswitch
> > +# Description: virtual switch
> > +### END INIT INFO
>
> I'm not that familiar with naming and description conventions here, but I would have expected more references to this coming from the Open vSwitch project (to distinguish it from potentially other vswitches). We have a similar definition for our Debian integration, but quite a few of the particulars are different:
>
> ### BEGIN INIT INFO
> # Provides: openvswitch-switch
> # Required-Start: $network $named $remote_fs $syslog
> # Required-Stop: $remote_fs
> # Default-Start: 2 3 4 5
> # Default-Stop: 0 1 6
> # Short-Description: Open vSwitch switch
> ### END INIT INFO
>
> Is there a reason not to bring them more in sync?
>
> > +### BEGIN INIT INFO
> > +# Provides: openvswitch-xapi-update
> > +# Required-Start: $network $remote_fs
> > +# Required-Stop: $network
> > +# Default-Start: 3 5
> > +# Default-Stop:
> > +# Short-Description: openvswitch-xapi-update
> > +# Description: reconfigures Open vSwitch based on XAPI configuration
> > +### END INIT INFO
>
>
> Is there a reason that neither of these define Default-Stop values? On my Ubuntu system, network has stop levels for 0 and 6.
>
> --Justin
>
>
More information about the dev
mailing list