wrote:

Hi, after few hours of playing around with ovirt-node and following http://www.ovirt.org/wiki/Ovirt_Quickstart guide, I've managed to get all the way to installing vdsm on gentoo server. At this point, it is not even the issue of creating the ebuild file for vdsm, the blocker for me was the following: - after compiling vdsm and installing it, order of files and install locations are clearly following redhat system - when starting vdsm by startup script (which is in /etc/rc.d/init.d, which, in turn, does not exists in Gentoo), from errors thrown at me I see that it is redhat startup script So, I will look through the code, when time allows, but if someone could help out by some info or advice, it would be appreciated... So far, I would start by porting /etc/init.d/functions from fedora and then continue to solve the problem with conf files being on different locations. Any thoughts on this? Is this the wa to go, in the first place? Dimitrije _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

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.

Adding vdsm-devel, which is where such changes should be considered. It looks like in the future this may be a good choice, but we'll still need to support existing implementations, as well as colleague distro's who still do not have a proper systemd implementation. BTW, Gentoo is using ~29-r1 which is still unstable in portage tree. Any input from vdsm dev's on systemd scripts?

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.

----- 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.

> > I'm sure that there are plenty of other Fedoraisms lurking in Vdsm. > We > would have to take them down one by one. > > Dan. > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

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.

> Actually we're thinking about NetworkManager, not netcf. > Also note that NetworkManager doesn't currently support bridge creation which I thought was something we needed to do (and I assumed was why we were manually interacting with the 'old' network configuration method in the first place).