Home · About · Download · Documentation · Getting Help · Google+

Ticket #36 (accepted enhancement)

Opened 7 years ago

Last modified 7 years ago

Move package list from mkchroot*.sh to a config file

Reported by: yqin Owned by: gmk
Priority: minor Milestone: Feature Update 3.2
Component: vnfs Version:
Keywords: Cc:


The ideal location would be /etc/warewulf/vnfs.conf. This way it would be a lot easier for people to customize their own VNFS. Currently it is hard coded in mkchroot scripts, e.g.,

yum --tolerant --installroot $VNFSDIR -y install \

SysVinit basesystem bash redhat-release chkconfig coreutils e2fsprogs ...

We may need to be careful about the format of this file though. I'd prefer to change it to:

excludes = /usr/local, /usr/share/doc, /usr/share/locale, /opt

packages = ...

packages = ...

packages = ...


Change History

comment:1 Changed 7 years ago by gmk

  • Status changed from new to accepted

The idea of the mkchroot scripts is to build a starting point for a VNFS, and people can update from there using the packaging system of the host system or from within the VNFS.

The idea of the --name argument to the wwvnfs command is to be able to find a configuration file that matches that name which should be at vnfs/name.conf. I haven't tested this thoroughly so it might need some attention. I see that as a solution to your RFE for multiple section declarations.

I don't think there is anything left in this ticket that needs resolving, but I will wait for confirmation to make sure I read it correctly.


comment:2 Changed 7 years ago by yqin

That is fine. I was just thinking it would be more comprehensive and useful than just a starting point, if we provide that feature so that users can customize their own initial VNFS. But I see your point.

--name is not a valid option of wwvnfs, but from the source code it does check for config file in /etc/warewulf/vnfs/$opt_name.conf, by checking an optional name passed to wwwvnfs :). I'm not sure what to put into this file to suit my needs though, because it only checks for include, exclude, chroot and output.

Note: See TracTickets for help on using tickets.