For the installation of dulak-server you have two choices:

Kickstart installation

Kickstart installation is preferred because it relieves the necessity of manually partitioning, selecting packages, etc. To perform a kickstart installation you need to:

  • if your BIOS allows you: put in the boot order disk before cdrom, while still being able to boot from cdrom,

  • save dulak-server.cfg onto an USB drive, write protect USB drive!

    Note that in the dulak-server.cfg file the initial root password is set to babariba. You must change it:

    • generate new password with:

      openssl passwd -1

      or (the script can be found in the latest version of syslinux):

      sha1pass new_babariba_password

    and modify the dulak-server.cfg file.

  • if you are installing workstation only the installation and not planning to use intel mkl (tested with version 10.1.2.024) you should use selinux = enforcing mode, and install more groups of packages,

  • provide a fast centos mirror instead of the default one, or, if you boot from DVD, enable installation from cdrom drive (instead of from the network) by uncommenting #cdrom, and commenting out url line,

  • review the partitioning layout (see Manual installation below),

  • make (if necessary) corrections to ethX (network section) and disk device used (bootloader, clearpart, part sections),

  • insert USB drive into dulak-server.

  • boot dulak-server from DVD or netinstall CD using: linux text ks=hd:sdb1:/dulak-server.cfg

    This part is tricky, because you have to guess how dulak-server recognizes the USB drive (in this case as /dev/sdb). The best way to find out is to have already another Linux distribution installed and let the system discover the mount on the USB drive. Another option is to boot from DVD using: linux text rescue - and run fdisk -l this will provide the disk information.

    Note ignoredisk --drives=sdb in the dulak-server.cfg file that skips creating of filesystems on your USB drive. If your USB drive is recognized for example as /dev/sdc you have to change this entry. Multiples drives can be specified: ignoredisk --drives=sdb,sdc.

  • due to bugs https://bugzilla.redhat.com/show_bug.cgi?id=366341 you have to press OK two/three times - the installation cannot be performed completely unassisted.

  • after successful installation (it should take less than 1 hour with network installation, less than 15 minutes from cdrom), remove the DVD/CD (system may try to boot from DVD/CD again!) boot the new system, and, as root:

    yum update
    service yum-updatesd stop
    chkconfig --level 35 yum-updatesd off
    reboot

Go to managing users.

Manual installation

Due to systemimager (and intel mkl) incompatibility with SElinux, the installation must use selinux = permissive mode. If you are installing workstation only the installation (without intel mkl) you should use selinux = enforcing mode.

Boot dulak-server from DVD, make sure to install the following groups:

@dns-server

@network-server

@server-cfg

and packages:

sendmail-cf

tftp-server

caching-nameserver

mkisofs

perl-XML-Simple

system-config-services

rpm-build

dhcp

and make sure to create the partitions /dulak-server/home (/home in case of workstation installation) and /scratch, e.g. the following commands work for the sda hardisk:

# /boot must be outside LVM
part /boot --fstype ext3 --size=100 --ondisk=sda --asprimary
part swap --size 4000 --ondisk=sda --asprimary
part pv.01 --fstype ext3 --size=1 --grow --ondisk=sda --asprimary
# --asprimary1 option is important
volgroup VolGroup00 pv.01
logvol / --fstype ext3 --name=lv_root --vgname=VolGroup00 --size=10000
logvol /scratch --fstype ext3 --name=lv_scratch --vgname=VolGroup00 --size=8000
# only the last logvol can --grow within a given volgroup
logvol /dulak-server/home --fstype ext3 --name=lv_dulak_server_home --vgname=VolGroup00 --size=1 --grow

After installation please set the default run level (don't do this on workstation):

cp /etc/inittab /tmp
sed s/id:5:/id:3:/g /tmp/inittab > /etc/inittab

and:

yum update
service yum-updatesd stop
chkconfig --level 35 yum-updatesd off
reboot

Go to managing users.

Troubleshooting

  • during kickstart use ctrl+alt+f3 to see errors log.

  • during kickstart installation you get problem described at https://bugzilla.redhat.com/show_bug.cgi?id=152378 (note double slash):

    Unable to retrieve http://mirror.centos.org//centos/5/os/i386/images/stage2.img

    Do not use fixed-address (see http://www.linuxjunkies.org/articles/dhcp-dejunkified.html) dhcp for dulak-server, i.e., use:

    host dulak-server { hardware ethernet XX:XX:XX:XX:XX:XX; }

    instead of:

    host dulak-server { hardware ethernet XX:XX:XX:XX:XX:XX;
                        fixed-address dulak-server.domain.com;
                      }

    Well, just revert to fixed-address after the installation.

Niflheim: Building_a_Cluster_-_Tutorial/installing_server (last edited 2010-11-04 12:59:47 by OleHolmNielsen)