[[ShowPath]] [[PageOutline]] {{{ #!html

WORK IN PROGRESS

}}} = Welcome to '''SALI'''! = Here at Sara we use [http://wiki.systemimager.org SystemImager] to install our nodes on different types of clusters. SystemImager allows you to create a clone of your running system. This clone can than be distributed by various protocols, eg: * rsync * bittorrent * flamethrower When installing an image the target system shall be booted with a kernel/initrd which contains the needed utilities for initializing a SystemImager installation. When the system is booted it will fetch the [http://wiki.systemimager.org/index.php/BOEL BOEL] utilities. The BOEL utilites contains, eg: * kernel modules * partition utility * formatting utilities for ext2, ext3, xfs, ... * various protocols to get the image == Why SALI == Sali is created due the fact that the current kernel/initrd and BOEL utilities are outdated. The trigger 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: * 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]. * The SALI initrd contains all kernel modules and software utilities. In SystemImager this software is distributed as a separate package (BOEL binaries). * Support for various protocols to install an image -- see [http://aria2.sourceforge.net aria2]: * rsync * Bittorent * ftp * http/https * metalink * Drop support for flamethrower/multicast and floppy disk support. * 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 Documentations] * For detailed overview of the changes read this [source:trunk/CHANGELOG changelog] * For now you must set ''SCRIPTNAME='' in the pxelinux file * If ''GRUB2=yes'' is set then we expect a seperate grub2 partition: = Documentation = Visit our online documentation here: * [wiki:SaliRequirements Building Requirements] * [wiki:SaliConfiguration Configuration] * [wiki:SaliBuilding Building] * [wiki:SaliUsage Usage] * [wiki:SaliFAQ Frequently Asked Questions] = Download = You can grab the tarball from our ftp site: * [ftp://ftp.sara.nl/pub/sali/sali.tar.gz]. The changelog can be found [source:trunk/CHANGELOG here]. = Source code = You can browse the current code here: * Release tree: [source:tags/] * Development tree: [source:trunk/] Or you can check out code through subversion: * Release tree: {{{svn co https://subtrac.sara.nl/oss/sali/svn/tags}}} * Development tree: {{{svn co https://subtrac.sara.nl/oss/sali/svn/trunk}}} = Authors / Contributers = == Authors == * Bas van der Vlies * Dennis Stam = Recent changes = [[ChangeLog(/, 6)]]