Unattended network installation in RedHat or Fedora

Analysis of unattended network installation (Kickstart) Demand in RedHat or Fedora: to expand the company's business, you need to create an office LAN. The new machine has been purchased and configured differently (the NIC supports the network startup function ). In pursuit of stability, the leaders decided to adopt the RedHat operating system. If the conventional installation method is used, it is time-consuming, cumbersome, and slightly careless, and the system configuration may be different. It is not conducive to future management. Reference concept: to meet this requirement, RedHat developed the kickstart Security

Network unattended installation (Kickstart) under Red Hat or Fedora)

Requirement Analysis: to expand the company's business, you need to create an office LAN. The new machine has been purchased and configured differently (the NIC supports the network startup function ). In pursuit of stability, the leaders decided to use the Red Hat operating system. If the conventional installation method is used, it is time-consuming, cumbersome, and slightly careless, and the system configuration may be different. It is not conducive to future management.

Reference concept: to meet this requirement, Red Hat developed the kickstart installation method. With the server's lftp and DHCP services, it can implement unattended automatic network installation of clients. This part is the implementation of Kickstart.

Network Structure

The IP address segment of the LAN is 192.168.1.0.

Shared Server A, with the IP address 192.168.1.254

Simple Configuration:

Configure a yum source and access it through ftp: // 192.168.1.254/pub/Red Hat;

Install and configure the Kickstart program.

Install server B with IP address 192.168.1.253

Simple Configuration:

Configure the DHCP service to provide IP addresses for bare metal machines in the LAN, and describe the files required to start the LAN;

Configure the tftp service to allow the client to download the startup image file.

Procedure:

1. Configure the FTP service and yum source on host

Install FTP service

[Root @ localhost Server] # rpm-ivh vsftpd-2.0.5-10.el5.i386.rpm

Start the service

[Root @ localhost Server] # service vsftpd start

Start vsftpd For vsftpd: [OK]

Configure yum Source

Install yum and createpreo software on a CD or other means

[Root @ localhost Server] # rpm-ivh yum-utils-1.0.4-3.el5.noarch.rpm rpm

[Root @ localhost Server] # rpm-ivh createrepo-0.4.4-2.fc6.noarch.rpm

Copy the content on the installation CD to the ftp public directory and modify the yum configuration file. For convenience, we use scripts to update the yum database.

#! /Bin/bash

Cd/var/ftp/pub/Red Hat

Rm-rf Server/. olddata/

Rm-rf VT/. olddata/

Rm-rf Cluster/. olddata/

Rm-rf ClusterStorage/. olddata/

For I in 'Find | grep "xml $" | grep "comps" '; do createrepo-g $ {I #. /*/} $ {I % /*/*. xml}; done

Exit 0

2. Configure the tftp service on machine B

[Root @ localhost Server] # rpm-ivh tftp-server-0.42-3.1.i386.rpm

Make sure the service is enabled

[Root @ localhost Server] # chkconfig-list | grep tftp

Tftp: Disable

[Root @ localhost Server] # chkconfig tftp on

[Root @ localhost Server] # chkconfig-list | grep tftp

Tftp: Enabled

Reload the xinetd daemon that manages the tftp service

[Root @ localhost Server] # service xinetd restart

Stop xinetd: [OK]

Start xinetd: [OK]