Changes between Version 94 and Version 95 of WikiStart


Ignore:
Timestamp:
02/13/13 11:02:38 (7 years ago)
Author:
dennis
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v94 v95  
    22
    33= Welcome to '''SALI'''! =
    4 For node installation we at [http://www.surfsara.nl SURFsara] used [http://wiki.systemimager.org SystemImager]. We switched to SALI for all our clusters.  SALI allows you to create a clone of your running system. This clone can be distributed  by various protocols ( [http://aria2.sourceforge.net aria2]) eg: rsync, Bittorent, ftp, http/https, metalink
    54
    6 == Why SALI ==
    7 SALI is created due the fact that on the moment of starting SALI:
     5SALI is a acronym for SURFsara Automatic Linux Installation and is widely used on our systems:
     6  - [https://surfsara.nl/systems/lisa LISA]
     7  - [https://surfsara.nl/systems/gpu-cluster GPU]
     8  - [https://surfsara.nl/systems/visualizations  RenderCluster]
     9  - [https://surfsara.nl/systems/shared/archive-file-system Central Archive]
    810
    9  * Systemimager kernel/initrd and BOEL utilities are outdated.  New hardware was not detected/supported
    10  * no ''grub2'' support
    11  * no ext4 support
     11SURFsara formerly used SystemImager for automatic installation of our machines. Due to new hardware we needed more up to date drivers and GRUB2 support. We thought this could be easily added, but during this process we decided to upgrade all software to the newest levels and replace some software components. The biggest hurdle was detecting of which hardware is in the system ([http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html udev]). We believe that SALI is better in detecting which hardware is available in the system than SystemImager.
    1212
    13 The trigger for us was that there is no ''grub2'' support. We thought this could be easily added, but during this process we decided to upgrade all software to the newest levels and replace some software components. The biggest hurdle was detecting of which hardware is in the system ([http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html udev]). We believe that SALI is better in detecting which hardware is in the system than the SystemImager setup. The focus for this project is/was:
    14 
    15  * Easily create a new kernel/initrd when a new kernel is released or one of the software components is updated, eg: [http://www.busybox.net busybox].
    16  * The SALI initrd contains all kernel modules and software utilities. In SystemImager this software is distributed as a separate package (BOEL binaries).
    17  * Drop support for flamethrower/multicast and floppy disk support.
    18  * With some minor [wiki:SaliUsage/UsingYourOldInstallScript adjustments] you can use your old generated SystemImager scripts. These scripts uses ''/etc/init.d/functions'' which is included in the initrd. We have added/changed a lot of functions to hide the complexity. We have reduced the code of the SystemImager scripts significantly, See [source:trunk/example/masterscript.new masterscript.new]. Read the [wiki:SaliUsage/Functions Functions Documentation]
    19  * For detailed overview of the changes read this [source:trunk/CHANGELOG changelog]
    20  * For now you must set ''SCRIPTNAME=<script_name>'' in the pxelinux file
    21  * If ''GRUB2=yes'' is set then we expect a seperate grub2 partition:
    22  * Added [http://code.google.com/p/diskscrub diskscrub],  Diskscrub overwrites hard disks, files, and other devices with repeating patterns intended to make recovering data from these devices more difficult
    23 
    24 == SALI xCAT plugin ==
    25 Currently we are investigating the possibilities to use SALI with xCAT.
    26 
    27 First SALI is used to restore the machine with an image. Then xCAT is used to finalize the installation. In our setup the installation time of 55 minutes is reduced to 15 minutes.
    28 
    29 We have tested this on a Power 6 machine with SLES 11.
    30 
    31 The xCAT module can be found in the [source:trunk/contrib contrib] directory.
     13The main focus for development of SALI is:
     14 - The SALI kernel/initrd contains all kernel modules and software utilities. In SystemImager this software is distributed as a separate package (BOEL binaries).
     15 - We have switch monolithic installation script to a UNIX like runlevel setup. To avoid kernel panics.
    3216
    3317== Documentation ==
     
    8367== Recent changes ==
    8468[[ChangeLog(/, 6)]]
     69
     70== SALI xCAT plugin ==
     71Currently we are investigating the possibilities to use SALI with xCAT.
     72
     73First SALI is used to restore the machine with an image. Then xCAT is used to finalize the installation. In our setup the installation time of 55 minutes is reduced to 15 minutes.
     74
     75We have tested this on a Power 6 machine with SLES 11.
     76
     77The xCAT module can be found in the [source:trunk/contrib contrib] directory.