通常人們在安裝Linux操作系統中,常使用是「光碟安裝」的傳統方式.目前,U盤安裝的方法也逐漸盛行.但是,上述的兩種方法只適用於單機部署,對於大規模化的安裝操作系統,推薦使用網路引導無人值守的自動化安裝操作系統的方式. 我曾經在 "/> 通常人們在安裝Linux操作系統中,常使用是「光碟安裝」的傳統方式.目前,U盤安裝的方法也逐漸盛行.但是,上述的兩種方法只適用於單機部署,對於大規模化的安裝操作系統,推薦使用網路引導無人值守的自動化安裝操作系統的方式. 我曾經在 "/>
server |-- perl-AppConfig-1.52-4.noarch.rpm |-- systemconfigurator-2.2.11-1.noarch.rpm |-- systemimager-common-4.1.6-1.noarch.rpm |-- systemimager-i386boot-standard-4.1.6-1.noarch.rpm `-- systemimager-server-4.1.6-1.noarch.rpm在安裝的過程中,注意軟體包的依賴關係,確保以安裝perl-XML-Simple、 perl-XML-Parser等軟體包.執行如下命令開始安裝:
[root@localhost server]# rpm -ivh *.rpm error: failed to stat /media/RHEL_5.4 i386 DVD: No such file or directory Preparing... ########################################### [100%] 1:perl-AppConfig ########################################### [ 20%] 2:systemconfigurator ########################################### [ 40%] 3:systemimager-common ########################################### [ 60%] 4:systemimager-server ########################################### [ 80%] Stopping xinetd: [ OK ] Starting xinetd: [ OK ] 5:systemimager-i386boot-s########################################### [100%] [root@localhost server]#2、安裝黃金(Golden)客戶端:
client/ |-- perl-AppConfig-1.52-4.noarch.rpm |-- systemconfigurator-2.2.11-1.noarch.rpm |-- systemimager-client-4.1.6-1.noarch.rpm |-- systemimager-common-4.1.6-1.noarch.rpm `-- systemimager-i386initrd_template-4.1.6-1.noarch.rpm執行rpm –ivh *.rpm完成黃金客戶端的安裝:
[root@qiuri client]# rpm -ivh *.rpm Preparing... ########################################### [100%] 1:perl-AppConfig ########################################### [ 20%] 2:systemconfigurator ########################################### [ 40%] 3:systemimager-common ########################################### [ 60%] 4:systemimager-client ########################################### [ 80%] 5:systemimager-i386initrd########################################### [100%] [root@qiuri client]#3、製作黃金客戶端鏡像
[root@qiuri ~]# si_prepareclient --server 172.16.0.10 Welcome to the SystemImager si_prepareclient command. This command may modify the following files to prepare your golden client for having it's image retrieved by the imageserver. It will also create the /etc/systemimager directory and fill it with information about your golden client. All modified files will be backed up with the .before_systemimager-4.1.6 extension. /etc/services: This file defines the port numbers used by certain software on your system. Entries for rsync will be added if necessary. /tmp/fileO0rkKZ: This is a temporary configuration file that rsync needs on your golden client in order to make your filesystem available to your SystemImager server. inetd configuration: SystemImager needs to run rsync as a standalone daemon on your golden client until it's image is retrieved by your SystemImager server. If rsyncd is configured to run as a service started by inetd, it will be temporarily disabled, and any running rsync daemons or commands will be stopped. Then, an rsync daemon will be started using the temporary configuration file mentioned above. See "si_prepareclient --help" for command line options. Continue? (y/[n]): y #輸入「y」,繼續. *********************************** WARNING *********************************** This utility starts an rsync daemon that makes all of your files accessible by anyone who can connect to the rsync port of this machine. This is the case until you reboot, or kill the 'rsync --daemon' process by hand. By default, once you use si_getimage to retrieve this image on your imageserver, these contents will become accessible to anyone who can connect to the rsync port on your imageserver. See rsyncd.conf(5) for details on restricting access to these files on the imageserver. See the systemimager-ssh package for a more secure method of making images available to clients. *********************************** WARNING *********************************** Continue? (y/[n]): y #再次輸入"y". -rw-r--r-- 1 root root 1855956 Apr 10 21:31 /etc/systemimager/boot/kernel Starting or re-starting rsync as a daemon..... done! This client is ready to have its image retrieved. You must now run the "si_getimage" command on your imageserver. Your client has been successfully prepared. Boot kernel (copied from this Linux distribution) and an initrd.img (generated by the initrd_template package) can be found in /etc/systemimager/boot. Automatically create configuration file for systemconfigurator: >> /etc/systemconfig/systemconfig.conf [root@qiuri ~]#我們可以使用ps –ef命令來檢查si_prepareclient 腳本工作是否正常,可以看到一個正在運行的rsync守護進程(使用/tmp/rsyncd.conf文件作為配置文件)在等待發送文件到網路的請求.
[root@qiuri ~]# ps -ef |grep rsync root 3812 1 0 15:46 ? 00:00:00 rsync --daemon --port=873 --config=/tmp/filerqgMEG root 3846 3539 0 15:47 pts/2 00:00:00 grep rsync現在可以在鏡像伺服器上執行si_getimage,將鏡像(即:黃金客戶端上的內容)從黃金客戶端複製到鏡像伺服器.默認情況下,鏡像被存儲在 SystemImager伺服器上的/var/lib/SystemImager/images目錄.
[root@localhost ~]# si_getimage --golden-client 172.16.0.2 -image vfast_backup --post-install reboot -directory /systemimager/ This program will get the "vfast_backup" system image from "172.16.0.2" making the assumption that all filesystems considered part of the system image are using ext2, ext3, jfs, FAT, reiserfs, or xfs. This program will not get /proc, NFS, or other filesystems not mentioned above. *********************************** WARNING *********************************** All files retrieved from a golden client are, by default, made accessible to anyone who can connect to the rsync port of this machine. See rsyncd.conf(5) for details on restricting access to these files on the imageserver. See the systemimager-ssh package for a more secure (but less effecient) method of making images available to clients. *********************************** WARNING *********************************** See "si_getimage --help" for command line options. Continue? ([y]/n):y #輸入"y"繼續黃金客戶端開始複製文件到鏡像伺服器,如下所示:
usr/share/zoneinfo/right/Navajo => usr/share/zoneinfo/right/US/Mountain usr/share/zoneinfo/ right/America/Denver => usr/share/zoneinfo/right/US/Mountain usr/share/zoneinfo/right/America/Shiprock => usr/share/zoneinfo/right/US/Mountain usr/share/zoneinfo/right/America/Los_Angeles => usr/share/zoneinfo/right/US/Pacific usr/share/zoneinfo/right/Pacific/Pago_Pago => usr/share/zoneinfo/right/US/Samoa usr/share/zoneinfo/right/Pacific/Samoa => usr/share/zoneinfo/right/US/Samoa sent 3524467 bytes received 3232535951 bytes 1941830.43 bytes/sec total size is 3411616325 speedup is 1.05 ------------- vfast_backup IMAGE RETRIEVAL FINISHED ------------- Press <Enter> to continue...
There are three ways to assign IP addresses to the client systems on an ongoing basis: 1) DHCP ---------------------------------------------------------------- A DHCP server will assign IP addresses to clients installed with this image. They may be assigned a different address each time. If you want to use DHCP, but must ensure that your clients receive the same IP address each time, see "man si_mkdhcpstatic". 2) STATIC ---------------------------------------------------------------- The IP address the client uses during autoinstall will be permanently assigned to that client. 3) REPLICANT ---------------------------------------------------------------- Don't mess with the network settings in this image. I'm using it as a backup and quick restore mechanism for a single machine. Which method do you prefer? [1]: #直接回車You have chosen method 1 for assigning IP addresses.接下來,讓我們確認配置以及馬上配置si_clusterconfig命令,直接回車即可.到此,整個黃金客戶端鏡像製作完成.可以到存儲鏡像的目錄查看創建好的鏡像.
Are you satisfied? ([y]/n): Would you like to run the "si_clusterconfig" utility now? (y/[n]):文章上半部分完成,查看整篇文章請看(下)
[火星人 ] 自動化安裝Linux系統之「SystemImager」(上)已經有953次圍觀