FAQ

From SystemImager

Jump to: navigation, search

Contents

Project Related Questions

I have never understood the full connection(s) between SystemImager, SystemInstaller, System Configurator, and SISuite. What are they?

The SystemImager and LUI (Linux Utility for cluster Installation) projects entered into a collaboration in 2001. SystemImager was to be the foundational component, with SystemInstaller and System Configurator being implemented to achieve the specific goals of LUI that were not yet present in SystemImager.

The goal of SystemInstaller (created by Michael Chase-Salerno) was the ability to install a SystemImager image directly to an imageserver, bypassing the need for a golden client.

The goal of System Configurator (created by Sean Dague) was to achieve distribution independence with regard to, well, system configuration details implemented by SystemImager such as network and boot loader settings.

It was determined that the three of these packages should take on a common identity as the System Installation Suite.

-BEF-

What is the current status of SISuite (System Installation Suite)?

Well, SystemInstaller was only ever used (to "our" knowledge) in OSCAR, and it's functionality has been incorporated into other components of the OSCAR framework. Moreover, all the recent distributions have developed their own tools that implement the SystemInstaller functionalities (see for example debootstrap for Debian/Ubuntu, yum for Fedora/Red Hat, YaST for SuSE), so, in case you're not using OSCAR, we strongly suggest to use the tool shipped in your distribution.

System Configurator is maintained by Erich Focht.

SystemImager is maintained by Andrea Righi.

Why a space in the name of System Configurator?

Its creator, Sean Dague, wanted one. -BEF-

Why use bittorrent in transport? Compared to multicast, what are the advantages by using bittorrent?

Read the BitTorrent advantages in this paper and presentation.

Auto-install Questions

During boot there is a 1 minute pause at "get_host_name_from_dns". We don't use that functionality - can it be turned off?

Yes. You have two simple options, either of which will work fine:

  • Have an /etc/hosts style file in /var/lib/systemimager/scripts that has an entry for each host/ip combo that you'll be using:
    /var/lib/systemimager/scripts/hosts
    • Note: It is recommended if you do this, that you make your changes to /etc/hosts and copy it over.
    • Note: si_addclients can create this file for you. When it does, it modified /etc/hosts and copies it over.
  • Set HOSTNAME as a kernel append parameter in your boot loader config.
    HOSTNAME=mybox


Disk Related Questions

What happens when you see partition related errors with cciss disks?

Under some circumstances it has been observed that cciss disks can get into a state such that parted, the partition editor, reports unexpected errors. The results can be anything from the autoinstall script failing OR it succeeding but the resultant system failing to boot completely. At least one known cause of this has been the editing of the partition table with Disk Druid on RedHat systems during installation.

If this occurs, one known solution that has worked is to use the SmartArray configuration tool which is invoked during system boot. Using this tool, one should delete and recreate the disks.

[it was also suggested I add a comment about write 32 blocks of zeros with dd, but I'm reluctant to add this without knowing whether this works or not --mjs]

LVM

How do I use LVM with SystemImager?

Start with the SystemImager LVM HOWTO.

UYOK (Use Your Own Kernel)

The standard SystemImager kernel isn't working. Can I use my own?

Yes. Start with the UYOK page.

Image Server Questions

How do I sync images between multiple image servers?

There are at least two ways to do this.

  1. The simplest method is to use "si_cpimage". It allows you to sync an image from one image server to another, and supports ssh as a transport.
  2. Another way, is to have a top level image server. The basic concept here is:
    • pull a client's image to a second level image server
    • pull that image server's image to a top level image server
    • use that image to deploy other image servers, which in turn can deploy other clients

See also

If you have trouble using SystemImager have a look at the troubleshooting guide.

Personal tools