Differences between revisions 1 and 24 (spanning 23 versions)
Revision 1 as of 2004-06-30 09:29:55
Size: 3278
Editor: anonymous
Comment:
Revision 24 as of 2020-06-08 04:19:14
Size: 1425
Editor: PaulWise
Comment: cleanup, add links
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## Auto-converted by kwiki2moinmoin v2005-10-07
'''
Automating Linux Installations'''
= Automating Linux Installations =
Line 4: Line 3:
An automated installation service is being used to install the Linux farms in the CERN computing centre and part of the desktop systems since end of 1998. The system is based on the Kickstart software from the RedHat distribution. The configurations for 370 systems are currently registered. The system has been adapted to automatically install CERN's Standard Unix Environment (SUE). A number of Kickstart problems have been solved or circumvented. Work is currently done on a more general system suitable for desktop ["PCs"]. == Requirements ==
Line 6: Line 5:
'''Introduction ''' An automated installation procedure should fulfil several conditions, namely:
Line 8: Line 7:
Linux is becoming a key operating system at CERN. Some 900 PC's running Linux are currently installed on the site, and some 50 new machines are added monthly. A big percentage are part of data processing farms placed at CERN's computing centre, the rest being used as servers or desktop workstations. With the freezing of other ["UNIXes"] and the data and CPU requirements imposed by new experiments like COMPASS and specially LHC's, the amount of Linux PC's is expected to increase dramatically over the next years. Several problems will have to be overcomed, one being the system installation. A typical Linux installation takes around 20 minutes and requires human intervention in order to enter configuration data and monitor the execution. This is too inefficient and error prone with hundreds or even thousands of systems to install or reinstall. An automated procedure should therefore be used.



'''Requirements '''

An automated installation procedure should fulfill several conditions, namely:
{{{
Line 21: Line 12:
}}}
Line 23: Line 13:
Examples of automated installation systems include JumpStart for Solaris, Ignite-UX for HP-UX and Kickstart for RedHat Linux ["4"], the latter being the Linux distribution used at CERN. == Tools for Debian ==
Line 25: Line 15:
 * [[DebianInstaller/Preseed|Debian Installer Preseed]]
 * [[FAI|Fully Automatic Installation]] can install and configure
 Debian and RPM based distributions
Line 26: Line 19:
 ''' Kickstart ''' === Kickstart ===
Line 28: Line 21:
Kickstart is the automated installation method for Linux. A system administrator creates a file (called a Kickstart file) which describes the configuration and the required setup. Kickstart is the automated installation method for Redhat and Fedora Linux distributions. A system administrator creates a file (called a Kickstart file) which describes the configuration and the required setup.
Line 30: Line 23:
This file contains the required disk partition setup, the packages to be installed and other configuration items like the language, time zone, mouse and keyboard setup etc. Kickstart is not available for Debian. There is some [[https://help.ubuntu.com/community/KickstartCompatibility|Kickstart compatibility available in Ubuntu]].
Line 32: Line 25:
A Kickstart file may also contain a post installation procedure, in which a list of shell level commands may be specified which are executed once the normal installation process has finished. === Cobbler ===
Line 34: Line 27:
The target machine is bootstrapped with a down sized kernel and a minimised root file system, the installation server is then NFS-mounted. The installation program starts and is driven by the contents of the Kickstart file. [[https://cobbler.github.io/|Cobbler]] is a Python Framework to manage unattended Linux installs (PXE, DHCP, kickstart, etc) mostly aimed at RPM based distributions.
Line 36: Line 29:
The Kickstart file may be stored on the installation diskette or in a central repository accessed using the network via BOOTP and NFS. Often, a single Kickstart file can be used for installing multiple machines with similar configuration. === See also ===

There are a [[SystemBuildTools|variety of system build tools]] available.

Automating Linux Installations

Requirements

An automated installation procedure should fulfil several conditions, namely:

  • unattended run: Installations should be run without (or minimal) human interaction.
  • concurrent installations: Multiple systems can be installed in parallel.
  • scalable: New clients (and OS releases) can be integrated easily.
  • flexible: A feature-rich configuration should be offered.
  • customisable: It should be possible to adapt the system to a specific environment and settings.

Tools for Debian

Kickstart

Kickstart is the automated installation method for Redhat and Fedora Linux distributions. A system administrator creates a file (called a Kickstart file) which describes the configuration and the required setup.

Kickstart is not available for Debian. There is some Kickstart compatibility available in Ubuntu.

Cobbler

Cobbler is a Python Framework to manage unattended Linux installs (PXE, DHCP, kickstart, etc) mostly aimed at RPM based distributions.

See also

There are a variety of system build tools available.