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. On Monday 21 November 2011 06:40:04 Jared Sutton wrote:
I noticed the same things when installing on ArchLinux. I also noticed that vdsm is doing things like re-configuring the network configuration, but it clearly uses redhat-specific methods (like modifying the files in /etc/sysconfig/network-scripts/). I see two possible solutions:
1. Create different support scripts for different distros (not a great solution, clearly). 2. Make the scripts as generic as possible, and use in-script logic to determine the currently-running distro (take a look at VirtualBox's vboxweb start-up script, for example; it has quite a bit of this type of logic).
For the network configuration issue, would it be realistic to rely on a network abstraction layer, such as NetworkManager or Wicd, since they operate across multiple distros?
Jared
On Sun, Nov 20, 2011 at 5:47 PM, Dimitrije Zivkovic <dimitrije.ziv@gmail.com
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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- /d "This message is made with 100% recycled electrons. No new atoms were destroyed in the making of this message."