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