| |
Foreword
In the financial industry, I have contacted the main operating system is AIX and SLES (SUSE Linux Enterprise Server), perhaps we usually use a lot more is CentOS, although there are some differences but the principles are interlinked, SMIT and also gray often practical YaST function, we recommend a chance to try the next experience. Because the line on SuSE automated deployment refer to the article less, this automated deployment plan has been verified and the production system for a year and a half, the configuration is relatively mature and stable. Followed Do not Repeat Yourself principle, this paper describes the fully automated installation practice based on SuSE SuSE AutoYaST achieve semi-automatic custom CD and PXE network For a more detailed description of the parameters can be read with reference to expansion of SuSE official website.
AutoYaST automated deployment SuSE gold partner
SuSE automated installation CD
Customized version
SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = 2
Download - https://www.suse.com/zh-cn/download-linux/
AutoYast Profile
AutoYast is SuSE Linux automatic installation tool. By AutoYast, in support DHCP, TFTP, PXE service, through FTP, NFS and other network installation source can be fully automated unattended SuSE Linux installation. However, this approach must be established independently of the server and the client supports PXE network boot, there is no network in the field or at the client system does not support the card scene does not fit, by AutoYast made a key SuSE Linux installation CD meet these scenes. This paper describes the SuSE Linux Enterprise Server 11 (referred to SLES11) a key installation CD-ROMs, other SuSE Linux for reference only.
Generate AutoYaST profile
After AutoYast configured successfully, generate an XML configuration file named autoinst.xml, SuSE Linux operating system installation by the document control.
AutoYast generate configuration files There are three ways:
The system automatically generates installation
After the system is installed by running the command generator
Edited directly generate (lazy optimum posture)
Generate a configuration file when the system is installed
Follow the normal steps to install SLES11, the software must be fully installed. Run to the last step "installation has been completed," check "to copy this AutoYast system", the system begins to generate clone system configuration files, and a pop-up window. Generate a configuration file with about two minutes, the resulting configuration file located in / root directory.
Run command to generate or modify configuration files
If no configuration file is generated when the system is installed, you can run the command generation. Open a terminal in the system, as root run the command yast2 autoyast, AutoYast open the configuration window, select "Tools" -> "create a reference profile" pop-up "Create a Reference Control File" window. Select the item to be configured, such as package selection, language, partition, keyboard layout, firewalls, network settings, etc., AutoYast obtain configuration information from the system according to the selected item. Select "File" -> "Save" pop-up "Save As" window, enter the file name "autoinst.xml", select "Save" to save the system prompts file to the specified directory.
Sometimes we need to make some adjustments to the module, such as disk partitioning, package and so on. Case presentation to adjust the partition modify the configuration file. As root run yast2 autoyast, AutoYast open window, select "File" -> After the "Open", select autoinst.xml file systems read the configuration, display configuration name AutoYast window accessories, modified save.
Fabrication and installation CD
After AutoYast configuration file is generated, you can start making a key installation CD. Making a key installation disc will need the original installation CD SLES11 data.
# SLES11 first copy the original installation CD-ROM data to the specified directory
mkdir / tmp / sles11
cp -R / media / S * / * / tmp / sles11
# Copy autoinst.xml
cp /root/autoinst.xml / tmp / sles11
# Edit isolinux.cfg file, find the # install location
cd boot / x86_64 / loader /
vi isolinux.cfg
# Install
append initrd = initrd autoyast = file: ///autoinst.xml splash = silent showopts
: X!
# Run mkisofs command to generate automatic installation CD
cd / tmp / sles11
mkisofs -R -o /tmp/SLES11-SP2-64-AUTO.iso -b boot / x86_64 / loader / isolinux.bin -c boot.cat -no-emul-boot -boot-load-size 4 -boot-info -table.
My Profile
Default partition
Title Format Size
swap swap 16G
boot ext3 120M
LVM
root ext3 5G
usr ext3 10G
var ext3 5G
opt ext3 10G
home ext3 15G
tmp ext3 10G
Total 71G
Pre-package
KDE Desktop Environment
Oracle Server
Base C / C ++ Compiler and Tools
nmap
java-1_6_0 libstdc ++ 43-devel-32bit
Default language
Main: English
Add: Chinese
Default username / password
root / If you direct reuse my profile please private letter I get the password: D
Default Network Configuration
Disable services: firewall, IPv6
SuSE PXE network installation automation
PXE Fundamentals
What is PXE?
PXE (Pre-boot Execution Environment) is a protocol designed by Intel, which allows the computer to boot through the network. Protocol is divided into client and server ends, the PXE client NIC ROM, when the computer is booted, BIOS into memory to perform the PXE client, and show command menu, the user selects, PXE client will be placed in the distal end operating system downloaded to run locally through a network. Run successfully PXE protocol need to address the following two questions: 1. Since it is transmitted over the network, so when you start the computer, its IP address configuration by whom; 2. what protocol to download the Linux kernel and root file system.
For the first problem, you can solve by DHCP Server, the DHCP server to assign an IP address to the PXE client, DHCP Server DHCP Client protocol is used to dynamically assigned IP addresses, but because this is an IP address assigned to the PXE Client, so when configuring DHCP Server, you need to add the appropriate PXE-specific configuration. As for the second question, the ROM PXE client resides, there has been a TFTP Client. PXE Client use TFTP Client, via the TFTP Server TFTP protocol to download the file. Thus, conditions would have to run the PXE protocol, let's take a look at the work process PXE protocol.
work process
PXE client is required to install Linux computer, TFTP Server and DHCP Server running on another Linux Server. Bootstrap files, configuration files, Linux kernel and the Linux root file systems are placed in the root directory of the TFTP server on Linux Server. PXE client in the course of their work, they need three binary: bootstrap, Linux kernel and the Linux root file system. Bootstrap file is an executable program, which provides users with a simple control interface, and the user's selection, download the appropriate Linux kernel and the Linux root file system.
An Introduction
Such programs need to set up a boot server and an install server (can be configured on the same physical machine), and then start stored on the boot server installation program over the network. The installer automatically accesses stored on the installation server installation configuration and the installation media to complete the installation.
The program involves the technological application of three major technologies: 1. On the PC start the SLES installer PXE protocol from the network 2. Network installation feature SLES installation program (referring to the network to access the installation media) 3. SLES installation unattended installation provides the functionality of the program (SuSE called AutoYast)
This article describes the method according to the hardware and software needs to complete the automated installation, you need the following hardware resources:
A PC and start the machine as the installation server (the machine can also be other architectures)
A PC machine to be installed, it must have a PXE NIC support
Built a LAN, said two machines are connected into the same subnet
To be installed SLES installation media
Configuration tftpd
To simplify the steps, we set up in XP virtual machine DHCP and TFTP server, tftpd with tools to integrate achieve PXE network boot, attention to service and client in the same LAN. Similar principle configuration of services under Linux, specific methods can refer to the Internet.
(1) Download tftpd http://tftpd32.jounin.net/
(2) Start tftpd32 program, select [Settings]
(3) Check the demand, here we select only [TFTP] and [DHCP]
(4) TFTP set as follows Base Directory: the corresponding storage Linux boot file PXE Compatibility: enhance the different types of card network boot support Show Progress bar: Display Progress Translate Unix file names in the network boot process: Conversion Unix filenames Allow "\ "As virtual root: allows virtual path other advanced options: settings include some details and compatibility
(5) DHCP configuration settings and focus attention DHCP address bindings boot files Boot File
(6) tftpboot directory structure
file: // D: \ tftpboot (2 folders, 3 files, 35.86 MB, 36.46 MB in total.)
INITRD 32.20 MB
LINUX 3.64 MB
pxelinux.016.04 KB
pxelinux.cfg (0 folders, 1 files, 193 bytes, 193 bytes in total.)
default193 bytes
tftpd32 (0 folders, 4 files, 620.33 KB, 620.33 KB in total.)
EUPL-EN.pdf 33.51 KB
tftpd32.chm 346.96 KB
tftpd32.exe 200.50 KB
tftpd32.ini 39.36 KB
INITRD and LINUX extracted from the Linux boot image pxelinux.0 is pxe boot image pxelinux.cfg folder under the default configuration file for the boot menu item Edit tftpboot \ pxelinux.cfg, you can customize the access mode and file path autoinst.xml
default linux
# Install Linux
label linux
kernel linux
append initrd = initrd autoyast = ftp: //198.15.0.106/suse/autoinst.xml install = ftp: //198.15.0.106/suse splash = silent showopts
Configuring FTP
(1) Download Filezilla Server http://filezilla-project.org/
(2) set up to allow anonymous ftp access to the account, configure the ftp mirror SLES installation directory path extraction within the directory to ftp
Configuring AutoYaST
SuSE AutoYaST use the tool to generate autoinst.xml, ftp copied to any directory, note the file path and the default configuration is consistent
Network boot the machine
After the previous configuration is completed, here we have a network in unattended mode to install the machine to be installed on
(1) Start the machine to be installed, choose to boot from the network card. Specific methods vary due to BIOS version.
(2) network card PXE code to contact the DHCP server to obtain an IP address and boot image, and then boot image is loaded and running.
(3) Start automatic installation
After installing the add custom modules
I am here to add kernel patches Kernel Case
< Scripts >
< Init-scriptsconfig: type = "list" >
< Script >
< Filename > instkernel.sh < / filename >
< Debug config: type = "boolean" > true < / debug >
< Location > < / location >
< Interpreter > shell < / interpreter >
< Source > < ! [CDATA [
#! / Bin / bash
#
#After Installation, the logfile from this script can be found in
# / Var / adm / autoinstall / logs
#
echo "========================================="
echo "... Starting AutoYAST included script ..."
echo "========================================="
rpm -ivh --root = / ftp://144.131.254.206/update/3.0...-0.6.8.1.x86_64.rpm
rpm -ivh --root = / ftp://144.131.254.206/update/3.0...-0.6.8.1.x86_64.rpm
rpm -ivh --root = / ftp://144.131.254.206/update/3.0...-0.6.8.1.x86_64.rpm
rpm -ivh --root = / ftp://144.131.254.206/update/3.0...-0.6.8.1.x86_64.rpm
]]>
< / Source >
< / Script >
< / Init-scripts >
< / Scripts >
summary
In fact, in the study of automated deployment process, we encounter various pits and only stepped on people can understand them is not easy, if you encounter any problems during testing and use SuSE automated installation, directly below the original welcome message, we learn and grow together. |
|
|
|