[Users] ovirt-node on Gentoo

[Doron Fediuck]

On Monday 21 November 2011 16:00:26 Doron Fediuck wrote:
> On Monday 21 November 2011 14:49:43 Mike Burns wrote:
> > On Mon, 2011-11-21 at 07:42 -0500, Ayal Baron wrote:
> > > 
> > > ----- Original Message -----
> > > > On Mon, Nov 21, 2011 at 12:58:29PM +0200, Doron Fediuck wrote:
> > > > > Hi Guys,
> > > > > Well, it looks like we've hit our first distro-diversion.
> > > > > 
> > > > > First of all, let's define the issues, and then see how we solve
> > > > > each one;
> > > > > 
> > > > > 1. Dimitrije is referring to vdsm's init script (including
> > > > > vdsm-reg).
> > > > > 
> > > > > 2. What Jared is referring to is relevant to:
> > > > > - Host installation process (AKA bootstrapping and registration)
> > > > > - vdsm operations on host networking
> > > > > 
> > > > > I agree it will be better if we solve each issue using the same
> > > > > code for all distro's. Having said that, we need to see if it's
> > > > > an achievable task.
> > > > > 
> > > > > Taking Dimitrije's issue as an example, we hit the first
> > > > > conflict; Gentoo is using OpenRC by default (and has some BSD-style
> > > > > leftovers), while RedHat and Fedora are using their SysV-style
> > > > > implementation, which confirms to LSB. Also, some Fedora services
> > > > > are moving to systemd implementation. Obviously these
> > > > > implementations
> > > > > are not trivial to bridge. So where Fedora's script will have
> > > > > "Required-Start:"
> > > > > Gentoo will use a depend() function (see vixie-cron as a sample).
> > > > > So unless we find a magical bridge for init standards, we'll have
> > > > > to have several init scripts, and each distro will use it's own
> > > > > script. We can try and generalize it, to make sure distor's
> > > > > with similar implementations use the same script.
> > > > > 
> > > > > As for Jared's networking issues, I believe there's more room
> > > > > here to make the relevant code more flexible, by testing the needed
> > > > > files, and using what we find. Thus, we'll have all in the same
> > > > > codebase. You can start by taking a look at vdsm/netinfo.py in
> > > > > vdsm's git.
> > > > 
> > > > And, as mentioned by Daniel Berrange, Vdsm should probably be changed
> > > > to
> > > > be using netcf to configure host networking. I'm not sure if Gentoo
> > > > has
> > > > netcf back-end, though.
> > > 
> > > Actually we're thinking about NetworkManager, not netcf.
> > 
> > Does NetworkManager have an api or library level package that doesn't
> > pull in all the UI bits?  ovirt-node does not currently include
> > NetworkManager packages at all and we don't want to pull anything that
> > is going to pull in X or another UI.
> > 
> > Mike
> 
> +1
> NetworkManager pulls in gnome, while it's net being used in many cases,
> especially in servers.
> As for netcf in Gentoo, there's not substantial support which will make
> it easy to work with.
> 
Clarifying my cryptic typos- netcf has no proper support in Gentoo.
It will be helpful if vdsm takes a more generic approach.
-- 

/d

"2B | !2B = FF"