On Sun, Jun 02, 2013 at 11:23:31AM -0400, Alon Bar-Lev wrote:
> ----- Original Message -----
> > From: "Dan Kenigsberg" <dan...@redhat.com>
> > To: "Yaniv Bronheim" <ybron...@redhat.com>
> > Cc: "VDSM Project Development" <firstname.lastname@example.org>
> > Sent: Sunday, June 2, 2013 5:50:52 PM
> > Subject: Re: [vdsm] About vdsmd init script
> > On Wed, May 29, 2013 at 08:38:42AM -0400, Yaniv Bronheim wrote:
> > > Hey,
> > >
> > > If I understand it correctly start_needed_srv and load-needed-modules
> > > is needed only by RedHat family dists, so you can keep it in vdsmd
> > > start function. All the others (systemd, upstat and openrc) have
> > > dependencies mechanism that we can use (as *.service Requires field)
> > I would not pile start_needed_srv and load-needed-modules together.
> > Declaring the needed modules in a /etc/modprobe.d/vdsm.conf file may not
> > be enough, since we would like vdsm and its networking functionality to
> > be functional before the host is rebooting. We may consider moving
> > load-needed-modules to ovirt-host-deploy, though.
> I do not understand, can you please explain so more... what exactly is the
> ovirt-host-deploy should not be mandatory tool, it is automation.
> If we need to load modules, can't we do this using dependencies or
> other mechanism, so that it will be transparent to user?
Maybe we can - I do not know how. We need to have tun, bonding and 8021q
inside the kernel when vdsm starts. That's easy to do after boot
(/etc/modprobe.d/vdsm.conf) but how can we do it just after vdsm is
installed? We cannot use rpm's %post script, as it must never change the
kernel state (think ovirt-node building).
(not very important. This is an execursion to the main question of this
vdsm-devel mailing list