NOVELL SUSE NCLP 3103课程9

1、Course 3103SUSE Linux Enterprise Server 11 Advanced AdministrationModule 9: Deploy SUSE Linux Enterprise 11,Novell Training Services,Module 9: Deploy SUSE Linux Enterprise 11,Objectives: Introduction to AutoYaST Installation Server: Setup and Use Set Up PXE Boot for Installations Create a Configurat

2、ion File for AutoYaST Perform an Automated Installation,Objective 1: Introduction to AutoYaST,Introduction to AutoYaST,To get a better idea what automated installations are about on SUSE Linux Enterprise 11, you need to understand the following: Autoinstallation Basics Installation Options and Deplo

3、yment Strategies,Autoinstallation Basics,AutoYaST is the tool for automated installations of SUSE Linux Enterprise 11. AutoYaST is optimally used in conjunction with an installation server also providing a TFTP and a DHCP server. The installation server can be accessed via the NFS, HTTP, FTP, and CI

4、FS/SMB protocols. AutoYaST can also be used to copy additional files into the installed system, and it can include scripts which are executed at the end of the installation.,Autoinstallation Basics (continued),It is possible to create a control file at installation time. In the last menu of the inst

5、allation process, you can select the Clone This System option. This will create an autoinst.xml file in the home directory of the root user (/root).,Installation Options and Deployment Strategies,To find the optimum solution for your needs, you have to understand the following: Installation Options

6、Deployment Strategies,Installation Options,SUSE Linux Enterprise 11 can be installed in various ways. There are three aspects you need to consider: Boot Media Installation Source Deployment Strategies,Boot Media,To install a machine, you have to choose a boot medium to boot the machine: Installation

7、 DVD PXE capable network card Floppy or USB disk,Installation Source,You can use different installation sources: Installation DVD Installation Server,Deployment Strategies,Your deployment strategy will depend to a large degree on the number of machines to deploy. Consider three different orders of m

8、agnitude: Deploy up to 10 Workstations Deploy up to 100 Workstations Deploy More than 100 Workstations,Deploy up to 10 Workstations,The approach that takes the least preparation is a manual installation using the installation DVD. You might still consider using an installation server.,Deploy up to 1

9、00 Workstations,If you have to deploy more than 10 workstations, an installation server and the use of the remote installation capabilities of SUSE Linux Enterprise 11 greatly facilitate the task.,Deploy More than 100 Workstations,The roll-out of a large number of machines is facilitated by AutoYaST

10、. AutoYaST controls the installation with an XML file which contains the machine specific information. AutoYaST allows you to create profiles containing all configuration information. If the differences in hardware are significant, it is also possible to create rules that determine which of several

11、AutoYaST files should be used for the hardware found.,Objective 2: Installation Server: Setup and Use,Installation Server: Setup and Use,To provide such an installation server in your network, you need to understand how to do the following: Set Up an Installation Server Use the Installation Server,S

12、et Up an Installation Server,The following steps are required: Fill the Installation Repository Make Add-on-Products Available,Fill the Installation Repository,Create a directory where you want to store the installation repository, such as / srv/install-repo/sled11 for SLED11, using the command mkdi

13、r -p /srv/install-repo/sled11 Insert the SUSE Linux Enterprise Desktop 11 installation DVD and copy all files on it to the repository: cp -a /media/SUSE_SLED-11-0-0.001/* /srv/install-repo/sled11,Make Add-on-Products Available,To access the add-on products repository during the automatic installatio

14、n, you can either include a pointer to it in the AutoYaST control file or add an add_on_products.xml file to the root of your product installation repository. This course covers the following two approaches: Yast Add-On-Creator Module and autoinst.xml Manual Creation of Repository and add_on_product

15、s.xml file,Yast Add-On-Creator Module and autoinst.xml,Take the following steps to create an add-on repository and to modify your control file: 1.(Conditional) If you have not created a gpg key pair, in a terminal window (as root) enter the command gpg -gen-key and follow the prompts to create your

16、own key pair. 2.Copy the RPM files you want to include in your add-on repository to a temporary directory, such as /tmp/repo-files. 3.Start YaST and select Miscellaneous Add-On Creator.,Yast Add-On-Creator Module and autoinst.xml (continued),To create an add-on repository from scratch, select Create

17、 an Add-On from the Beginning and click Next.,Yast Add-On-Creator Module and autoinst.xml (continued),4.In the Add-On Product Creator dialog that appears, fill in the text boxes with the name and version of your repository and the directory that holds your RPM files.,Yast Add-On-Creator Module and a

18、utoinst.xml (continued),To continue click Next.,Yast Add-On-Creator Module and autoinst.xml (continued),Yast Add-On-Creator Module and autoinst.xml (continued),5.In the Product Definition dialog, select Vendor and click Edit. In the dialog that appears, enter a vendor name. In the Product Definition

19、 dialog click Next. The Package Descriptions dialog appears. 6.The Package Descriptions dialog lists the packages that are part of your add-on repository. To continue click Next. The Editor for Patterns dialog appears. 7,In the Editor for Patterns dialog, you can create Patterns for your add-on prod

20、ucts. To continue click Next.,Yast Add-On-Creator Module and autoinst.xml (continued),Yast Add-On-Creator Module and autoinst.xml (continued),8.In the Path to Output Directory text box, type the directory where you want your add-on product repository to reside. To continue click Next. A Signing the

21、Add-On Product dialog appears. 9.In the GPG Key ID text box, type the ID, such as the e-mail address you entered during the creation of your key pair, of the GPG key you want to use to sign the content file in the root of the repository. Type the passphrase to unlock the private key. Click Next to c

22、ontinue. An Overview dialog appears. 10.In the Overview dialog review your settings and click Finish.,Yast Add-On-Creator Module and autoinst.xml (continued),Yast Add-On-Creator Module and autoinst.xml (continued),11.In the Add-On Creator Overview, click Build. (Optional) If a message appears that i

23、nforms you that the obs-productconverter package needs to be installed, click Install. 12.Click Finish to close the Add-On Creator module.,Yast Add-On-Creator Module and autoinst.xml (continued),13.Open the AutoYaST profile used to install machines in an editor and add the following lines below the

24、line starting with profile ., nfs://srv/install-repo/Add-On My Add-Ons / My Add-Ons ,Yast Add-On-Creator Module and autoinst.xml (continued),14.In the AutoYaST profile, look for the line Change the value from false to true. The line should look like the following: Save the file and close t

25、he editor.,false,true,Manual Creation of Repository and add_on_products.xml file,Take the following steps to set up your repository and use the add_on_products.xml file during installation: 1.(Conditional) If you have not created a gpg key pair, in a terminal window (as root) enter the command gpg -

26、gen-key and follow the prompts to create your own key pair. 2.Install the inst-source-utils package if it is not yet installed by entering the following as root in a terminal window: rpm -q inst-source-utils | yast -i inst-source-utils,Manual Creation of Repository and add_on_products.xml file (cont

27、inued),3.Run the following command with the root of your installation repository as argument: 4.Using the mkdir -p command, create the updates/suse/ architecture/ directory and copy any RPM files you want to make available to that directory.,da10: # create_update_source.sh /srv/install-repo/sled11/

28、Creating /srv/install-repo/sled10/updates.,Manual Creation of Repository and add_on_products.xml file (continued),5.Change to the updates/suse directory and run the following command:,da10:/srv/install-repo/sled11 # cd updates/suse da10:/srv/install-repo/sled11/updates/suse # da10:/srv/install-repo/

29、sled11/updates/suse # create_package_descr -x setup/descr/EXTRA_PROV using settings: datadirs: . languages: english output dir: ./setup/descr/ is not a directory: ignoring extra_provides: setup/descr/EXTRA_PROV done processed 1 packages now recoding to UTF-8: packages packages.DU packages.en da10:/s

30、rv/install-repo/sled11/updates/suse #,Manual Creation of Repository and add_on_products.xml file (continued),6.Change to the directory updates/suse/setup/descr and create an updated directory.yast file:,da10:/srv/install-repo/sled11/updates/suse/setup/descr # ls directory.yast,Manual Creation of Rep

31、ository and add_on_products.xml file (continued),7.Change back to the updates directory and run the create_sha1sums x -n command. The result is a contents file that contains SHA1 hashes for the files created in the previous step:,da10:/srv/install-repo/sled11/updates/ # create_sha1sums -x -n da10:/s

32、rv/install-repo/sled11/updates/ # cat content CONTENTSTYLE 11 . SUMMARY SUSE Linux Enterprise Server VENDOR SUSE LINUX Products GmbH, Nuernberg, Germany VERSION 11 META SHA1 b907a3d5593c3a2f0108f9ba27e3c5b8ef0121d5 packages META SHA1 4a0c3656cd8c61a68cccf2c75ec83f1f132556ec packages.DU META SHA1 94e

33、8d1bf3d7b53fd7c8ce32d6f6ea70cf47ede87 packages.en,Manual Creation of Repository and add_on_products.xml file (continued),8.Create an add_on_products.xml file in the root of your installation repository that points to the servers and directories with add-on products:, SLED11 Add-on nfs://sr

34、v/install-repo/sled11/ updates / false true ,Manual Creation of Repository and add_on_products.xml file (continued),9.Create a file containing the SHA1 sum of the add_on_products.xml file. Run the sha1sum command to create the checksum: 10.Sign the SHA1SUMS file with the gpg command:,da10:/srv/insta

35、ll-repo/sled11/ # sha1sum add_on_products.xml SHA1SUMS da10:/srv/install-repo/sled11/ # cat SHA1SUMS e13af51a0b1993bf20d597408c457681aea382c0 add_on_products.xml,da10:/srv/install-repo/sled11/ # gpg -b -sign -armor SHA1SUMS,Manual Creation of Repository and add_on_products.xml file (continued),11.Si

36、gn the content file you created in Step 7 with gpg as well. 12.The key to verify the signatures has to be available in the root of the installation repository. You also have to update the directory.yast file in the root directory of your installation repository. Run the following commands:,da10:/srv

37、/install-repo/sled11/ # gpg -export -armor your_keyid SHA1SUMS.key da10:/srv/install-repo/sled11/ # ls directory.yast,Manual Creation of Repository and add_on_products.xml file (continued),13.The last step is to include your public key in the initrd. The initrd is in the /boot/i386/loader/ directory

38、 on the installation DVD. Copy the initrd and my-key.gpg to a directory of your choice, such as /tmp, and add the my-key.gpg file to the initrd as shown in the following:,da10:/srv/install-repo/sled11/ # cp SHA1SUMS.key /tmp/my-key.gpg da10:/srv/install-repo/sled11/ # cd /tmp/ da10:/tmp/ # mv initrd

39、 initrd.gz da10:/tmp/ # gunzip initrd.gz da10:/tmp/ # find my-key.gpg | cpio -o -A -F initrd -H newc da10:/tmp/ # gzip initrd da10:/tmp/ # mv initrd.gz initrd,Use the Installation Server,To use the installation server, you have to specify the server when the initial boot screen shows up. With the Do

40、wn key, move to Installation, then press F4. From the menu, select the installation server type you want to use.,Use the Installation Server (continued),Use the Installation Server (continued),Instead of selecting NFS from the menu and specifying the IP address and path in the dialog, you can type i

41、nstall=nfs:/IP_address/path/to/repository/ in the Boot Options field.,Set Up an Installation Server,Complete Exercise 9-1. In this exercise, you copy the files of the installation DVD to a directory and make this directory accessible over the network using NFS. Then you prepare the installation repo

42、sitory to provide additional RPMs that are not part of the installation media.,Objective 3: Set Up PXE Boot for Installations,Set Up PXE Boot for Installations,To set up PXE boot, you need to understand how to do the following: Install and Configure tftp Configure pxelinux Install and Configure the

43、DHCP Server Set Up PXE Boot for Installations,Install and Configure tftp,Install the tftp package with the yast -i tftp command. As the TFTP server is started via xinetd, it is necessary to edit /etc/xinet.d/tftp. It should look similar to the following example:,# default: off # description: tftp se

44、rvice is provided primarily for # booting or when a router needs an upgrade. Most sites # run this only on machines acting as boot servers. service tftp socket_type = dgram protocol = udp wait = yes user = root server = /usr/sbin/in.tftpd server_args = -s /tftpboot -r blksize # disable = yes ,Instal

45、l and Configure tftp (continued),To access the TFTP server, it is necessary to start xinetd with the rcxinetd start command. If you want xinetd to start during system boot, add it to the proper runlevel directories with the insserv xinetd command.,Configure pxelinux,To configure pxelinux for network

46、 boot, you have to understand the following: pxelinux Files and Directories Configure pxelinux,pxelinux Files and Directories,The first step is to install the syslinux package using the yast -i syslinux command. Then copy the /usr/share/syslinux/pxelinux.0 file to /tftpboot/. From the SUSE Linux Ent

47、erprise Server 11 installation DVD, copy the linux, initrd, and message files from the /mountpoint/boot/i386/loader/ directory to /tftpboot/.,Configure pxelinux,To configure pxelinux, you have to understand the following: Configuration Filename Convention Configuration File Content,Configuration Fil

48、ename Convention,pxelinux will search for the configuration file on the boot server in the following way: First it will search for a configuration file based on the MAC address of the NIC of the client in lower hexadecimal notation, and the ARP type (Ethernet: ARP type 1). Next it will search for th

49、e configuration file using the IP address of the client in hexadecimal notation. If that file is not found, it will remove one hexadecimal digit and try again.,Configuration File Content,The content of the file defines which kernel and initrd are loaded. The content of the file could look like the f

50、ollowing:,default harddisk # SLED11 label SLED11 kernel linux_sled11 append initrd=initrd_sled11 ramdisk_size=65536 insmod=e100 netdevice=eth0 install=nfs://srv/install-repo/sled11 vga=0 x317 # SLES11 label SLES11 kernel linux_sles11 append initrd=initrd_sles11 ramdisk_size=65536 insmod=e1

51、00 netdevice=eth0,Configuration File Content (continued),. # hard disk (default) label harddisk localboot 0 implicit 0 display message prompt 1 timeout 100,Configuration File Content (continued),In a message file, you can include an explanation of each possible choice, as in the following example: T

52、o install SLED11, enter SLED11 at the prompt.,To boot from harddisk, just press . Available boot options: SLED11 - AutoYaST-Installation of SLED11 SLES11 - AutoYaST-Installation of SLES11,Install and Configure the DHCP Server,To install the DHCP server, select the YaST Software Management module and

53、 then in the Software Management dialog, search for “dhcp”, select dhcp-server on the right, and then click Accept. There are two configuration files that need to be edited: /etc/sysconfig/dhcpd /etc/dhcpd.conf,/etc/sysconfig/dhcpd,The /etc/sysconfig/dhcpd file contains configuration options which a

54、re submitted as parameters to the DHCP daemon by the /etc/init.d/dhcpd start script. The first parameter defines the interfaces which the DHCP server listens on for requests. If the DHCP server listens on the two interfaces eth0 and eth1, set the variable DHCPD_INTERFACE to the following: DHCPD_INTE

55、RFACE=eth0 eth1,/etc/sysconfig/dhcpd (continued),Two other variables enhance the security of the server: DHCPD_RUN_CHROOTED=yes and DHCPD_RUN_AS=dhcpd,/etc/sysconfig/dhcpd (continued),As the server processes are running in a chroot environment, the additional configuration files have to be copied in

56、to the chroot environment. The following is an example: DHCPD_CONF_INCLUDE_FILES=/etc/dhcpd.conf.shared /etc/dhcpd.conf.d”,/etc/dhcpd.conf,The configuration file for the DHCP server is /etc/dhcpd.conf. The entries in the configuration file belong to two categories: Parameter statements Declarations,

57、/etc/dhcpd.conf (continued),Starting with DHCP server version 3, dynamic updates of a DNS server are possible. If no dynamic update is done (as in this example), specify none as the parameter to this statement:,# # /etc/dhcpd.conf # ddns-update-style none;,/etc/dhcpd.conf (continued),The following a

58、re statements regarding the lease times (the validity period for assigned IP addresses):,# # specify default and maximum lease time # default-lease-time 86400;max-lease-time 86400;,/etc/dhcpd.conf (continued),The following section of dhcpd.conf shows how to provide information on the DNS domain to b

59、e used: As the last parameter, specify the addresses of routers in the subnet:,# # What is the DNS domain and where is the name server? # option domain-name ; option domain-name-servers , 0;,# # This is a router # option routers ;,/etc/dhcpd.conf (continued),There are several options that are needed to enable booting using PXE: Define the range of addresses that can be used for assigning IP addresses to clients.,allow bootp; next-server ; server-name ; filename pxelinux.0;,# # Which IP addresses may be assign