[Users] Customizing node configuration

[Allen Belletti]

Have since learned that what I did was equivalent to using the "persist" command, and known not to work for modprobe and other things early in the boot process.

Have also discovered that even mounting / read-write and using mount --bind to get at what's "under" /etc doesn't help.  Am assuming that the "live-rw" filesystem is created at boot time from an image, and can't be modified short of building from source.  Is that correct?

It looks like perhaps what I want to do is install the ovirt-node packages onto my OS of choice (CentOS 6.4, currently.)  Will do some reading and trying to see if that's possible.  I see that it's documented on FC19 but would prefer to remain with CentOS.

Any tips are appreciated of course!

Thanks,

Allen Belletti
AVP Ed. Tech Engineering Innovation
Georgia Gwinnett College
678-407-5093
www.ggc.edu

________________________________
From: users-bounces at ovirt.org <users-bounces at ovirt.org> on behalf of Allen Belletti <allen at ggc.edu>
Sent: Wednesday, October 02, 2013 4:40 PM
To: users at ovirt.org
Subject: [Users] Customizing node configuration

Hello All,

I've been searching the archives and not yet managed to find anything on the subject, so I'm hoping that someone can point me in the right direction.

I am using nodes with Intel 10G network cards.  The driver for these cards has been tweaked to complain (and fail to start the interface) if a non-Intel approved optical transceiver is in use.  It's easy to override with the following options:

ixgbe.allow_unsupported_sfp=1

The usual ways of doing this are either to place it on the kernel command line at boot time, or in /etc/modprobe.d/ixgbe.conf where it would read "options ixgbe allow_unsupported_sfp=1".  Unfortunately I have no idea how to make either of these permanent on an oVirt node.

I'm running the ovirt-node-iso-3.0.1-1.0.2.vdsm.el6.iso image.  It has an /etc/modprobe.d directory where changes do not persist across reboots.  It also has /config/etc where I've added modprobe.d and modprobe.d/ixgbe.conf.  By adding this file to /config/files, I've been able to make it appear in /etc/modprobe.d at boot time.  This has no effect.  It appears to take place after the ixgbe driver has already been started.  If I "rmmod ixgbe" and "modprobe ixgbe" manually, it works fine.

So the general question is, how do I make configuration changes which persist across reboots?  Surely others have run into the same situation when trying to support specific devices.

Thanks,

Allen Belletti
AVP Ed. Tech Engineering Innovation
Georgia Gwinnett College
678-407-5093
www.ggc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20131002/b64fc6a9/attachment-0001.html>