Openfiler – Automated Installing Via Kickstart

Openfiler – Automated Installing Via Kickstart

Introduction

This article explains how to install Openfiler version 2.3 over the network automatically using Kickstart.

The infrastructure used for this article is a Centos 5 server with TFTP installed to provide the PXE server, DHCP, Apache.

Pre-requisites

In order to install Openfiler 2.3 automatically using Kickstart the following pre-requisites must be met :-

  • A copy of the Openfiler 2.3 installation ISO
  • A DHCP server configured to provide the relevant PXE options
  • A TFTP server to provide the boot media
  • An Apache Server to provide the installation media
  • Syslinux installed and configured on the TFTP server

Copying The Installation Files To Your PXE Server

Once you’ve got the installation ISO mount the image, navigate to the images/pxeboot directory and copy the contents to your PXE Server directory (On Centos /tftpboot folder). The following files should now be in your PXE Server directory :-

initrd.img
vmlinux

Configuring For Http Delivery

As with most PXE installation methods of Linux based systems you can provide the files over HTTP or NFS.  The infrastructure used for this article was configured for HTTP delivery due to subnet restrictions on the network.

To provide the remaining files to the PXE client copy the rPath folder from the installation ISO to the root of your web server directory.  On the Apache server used for this installation the rPath folder was copied to/var/www/html.

During the installation of Openfiler select HTTP for the location of the files and when prompted enter the web server name or IP address and the folder where the rPath folder was copied

Modify the PXE Configuration file

Once the files have been copied to the PXE Server directory edit the PXE configuration file (On Centos /var/lib/tftpboot/pxelinux.cfg) and add the following lines :-

label Openfiler-Auto
    menu label Openfiler Kickstart Install
    kernel vmlinux
    append ramdisk=8096 vga=normal ks ksdevice=eth0 initrd=/initrd.img ks=http://{apache server ip}/openfiler.cfg

N.B. the append line includes the ks=http://….. line

Creating The Kickstart Config File

To create the kickstart config file for this article I used the anaconda-ks.cfg log created on another Openfiler server and modified it.

Below is the contents of the openfiler.cfg file used for this installation :-

install
url –url http://{apache server IP/
text

lang en_US.UTF-8
langsupport –default=en_US.UTF-8
keyboard uk

xconfig –card “VESA driver (generic)” –videoram 8192 –hsync 31.5-37.9 –vsync 50-70 –resolution 800×600 –depth 16

network –device eth0 –bootproto static –ip {your openfiler ip} –netmask {net mask as required} –gateway {your gateway ip} –nameserver {your nameserver} –hostname {your hostname}

rootpw {your password}
firewall –enabled –port=8003:tcp –port=8004:tcp

selinux –disabled

authconfig –enableshadow –enablemd5

timezone Europe/London

bootloader –location=mbr –append quiet

clearpart –drives=sda –all
part /boot –fstype ext3 –ondisk=sda –asprimary –size=100
part swap –size=512 –ondisk=sda
part / –fstype ext3 –ondisk=sda –asprimary –size=4000 –grow

reboot

%packages
@ everything
e2fsprogs:lib
e2fsprogs:locale
e2fsprogs:data
kernel:vmware
kernel
e2fsprogs:doc
kernel:build-tree
kernel:configs
e2fsprogs:runtime
e2fsprogs
kernel:runtime

%post
conary updateall

The machine used for this installation was a VMWare virtual machine with a 256Mb RAM, 5Gb SCSI disk, and one Network Card.

The last line in the %post section performs a full update of Openfiler before rebooting.

This will perform a fully automated installation of an Openfiler server including partitioning the disks and updating the configuration at the end.