The following patch adds server support for saving the generated kickstart into a machine-specific directory. That kickstart is then available through http, ftp, and nfs. The snake-server administrator is required to setup and enable those services. Additionally, snake-server will only copy the kickstart file into the machine-specific directory:
/var/lib/snake/machines/${machine_id}/ks.cfg
Snake servers can then make this available by using local bind-mounts to expose that directory to the appropriate service. For example:
# for FTP ...
$ service vsftpd on
$ mkdir /var/ftp/ks
$ mount -obind /var/lib/snake/machines /var/ftp/ks
# for NFS ...
$ service nfs on
$ echo "/var/lib/snake/machines *(ro)" > /etc/exports
# for HTTP ... (depends on local site setup)
$ service httpd on
$ mkdir /var/www/html/ks
$ mount -obind /var/lib/snake/machines /var/www/html/ks
Additionally, the snake-server needs to know where to tell the client to download the kickstart files. This can be accomplished by setting values in /etc/snake.conf. Using the examples above, one would use the following configuration options:
ftp_root = /ks
nfs_dir = /var/lib/snake/machines
http_root = /ks
In the future, the snake-server will handle creation of the bind-mounts for you. All that would be required is setting up and enabling the appriopriate service (e.g. vsftpd, nfs, or httpd).
Comments/concerns/bugs welcome.
Thanks,
James
--
==========================================
James Laska -- jlaska(a)redhat.com
Quality Engineering -- Red Hat, Inc.
==========================================