Thông tin tài liệu
CHAPTER 6 SETTING UP AUTOMATED INSTALLATION 119 ecjkna6 N?O+orj]`iejeopn]peraopqbbsehh^aecjkna`ej]hh_kleao N?O *orj lnk_aooao6 ]ju66 _bata_`naop]np $_b[^]oa[l]pd%+_bata_` _boanr`naop]np $_b[^]oa[l]pd%+_boanr` _bajr`naop]np $_b[^]oa[l]pd%+_bajr` hejgo6 na`d]pxokh]neoxokh]neot4266 +r]n+_bajceja+^ej+_b]cajp): $_b[^]oa[l]pd%+_b]cajp `a^e]j]hna]`uoapoql]ouihejgbnki+r]n+he^+_bajceja.+^ej pk+qon+^ejokjk_d]jcaonamqena`kjpd]plh]pbkni _klu6 Aranupdejcej+r]n+_bajceja+i]opanbehao+ejlqpokjpdai]opan []j`[aranupdejcejepooq^`ena_pkneaoeo_klea`pkaranudkop* $i]opan[_bejlqp%+`aop9 $skng`en%+ejlqpo+ n9ejb ik`a93,, pula9^ej]nu at_hq`a9&z at_hq`a9& at_hq`a9&(r lqnca9pnqa oanran9 $lkhe_udkop% pnqopgau9pnqa aj_nulp9pnqa seen this ql`]pa*_kjb file before; we’re simply getting it into place without using _b*lna_kjb this time. The convenience of FAI’s b_klu command makes _b*lna_kjb unnecessary here. CHAPTER 6 SETTING UP AUTOMATED INSTALLATION 120 Finally, we had to override an error from the lkopbet installation involving a missing nkkp alias. In the file +onr+b]e+_kjbec+dkkgo+o]rahkc*H=OP*okqn_a, we changed: iuecjknal]ppanjo9TTTTT to: iuecjknal]ppanjo9+ap_+]he]oaoateopo(^qp`kaojkpd]ra]nkkp]he]o This change allows the host to fully install without having to stop for this error. Installing Your First Debian Host Now we’re ready to boot our host etchlamp a higher preference than booting from the hard disk. The last thing you want is an acci- dental reinstallation the next time you reboot the host! If you really prefer to boot from `d_l`*_kjb after successful installation. comes from the FAI Guide; we couldn’t capture this information directly from our exam- ple systems): @D?LI=?=@@N6,,,03130=.0/ @D?L***+ ?HEAJPEL6-5.*-24*-* I=OG6.11*.11*.11*,@D?LEL6-5.*-24*-*.1, C=PAS=UEL6-5.*-24*-*.10 LTAHEJQT/*/-$@a^e]j(.,,3),/),5%?klunecdp$?%-550).,,1D*Lapan=jrej QJ@E`]p]oaciajp]p6,,,5@30, QJ@E`]p]oaciajpoeva6/.40 QJ@E_k`aoaciajp]p6,,,5,,,, QJ@E_k`aoaciajpoeva6.0?, LTAajpnulkejpbkqj`$sadkla%]p5@306,,B2 IuEl]``naoooaaiopk^a?,=4,-?,-5.*-24*-* el9-5.*-24*-* 6-5.*-24*-*.1,6-5.*-24*-*.106.11*.11*.11*, taken from the FAI Guide): CHAPTER 6 SETTING UP AUTOMATED INSTALLATION 121 ))))))))))))))))))))))))))))))))))))))))))))))))) Bqhhu=qpki]pe_Ejop]hh]pekj)B=E B=E/*.( =qc.,,3?klunecdp$_%-555).,,3 Pdki]oH]jca8h]jca<ejbkni]peg*qje)gkahj*`a: ))))))))))))))))))))))))))))))))))))))))))))))))) ?]hhejcp]og[_kjb`en Ganjahl]n]iapano6ejepn`9ejepn`*eic).*2*-4)1)042el9`d_l nkkp9+`ar+jbojbonkkp9+onr+b]e+jbonkkp^kkp9hera B=E[BH=CO9ran^koa(ood`(_na]parpB=E[=?PEKJ9ejop]hh >KKP[EI=CA9rihejqv).*2*-4)1)042 Once you’ve done the imaging and reboots, you should be able to ood into the host: oodap_dh]il)hnkkp nkkp<ap_dh]il#ol]ooskn`6 Pdeoouopaieonqjjejchejqt6hejqt[e242[.[2[-4[2[042[[-[Bne[Fqj[2[ [03[,-[QP?[.,,4 9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9 Ukq]nakj]lner]pa_]ilej*japouopai* Qj]qpdkneva`qoaeolnkde^epa`(]hh]_perepueoikjepkna`* 9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9)9 O=Op]bb6bknhk_]h)kjhu]``epekjodana(lqp_kjpajpej+ap_+ikp`)hk_]h) ap_dh]il6z`b)d BehaouopaiOevaQoa`=r]ehQoa!Ikqjpa`kj +`ar+o`]-/*2C/5,I/*,C !+ pilbo34I,34I,!+he^+ejep+ns q`ar-,I1.G-,I-!+`ar pilbo34I0*,G34I-!+`ar+odi ap_dh]il6z The host has the cfengine- configured +ap_+ikp`, and the disk is partitioned according to our custom settings. In addition, the lo command shows that the Apache server is run- Overall, FAI is a pleasure to work with. The directory names and scripts are self- explanatory, the class mechanism is intuitive and easy to work with, and the packages put useful starting configuration files into place. In addition, the b]e)`k_ package includes sam- ple configurations for the `d_l` and pbpl` from no automated installation system to a fully automated mass- installation system using FAI can happen in a matter of hours. CHAPTER 6 SETTING UP AUTOMATED INSTALLATION 122 Employing JumpStart for Solaris JumpStart, or Custom JumpStart as it’s called by Sun, is an automatic installation system for the Solaris OS. It’s based on profiles, allowing a system to match installation profiles - tem’s CPU architecture. (For more information on the general JumpStart architecture, see dppl6++`k_o*oqj*_ki+]ll+`k_o+`k_+4-3)11,2+fqilop]npkranreas)0;]9reas.) Using JumpStart can be an entirely hands- off process, although an unattended boot from the network, as well as use profiles and install media from the network. In getting started, we again have a chicken-and- egg problem: we need a host to con- 1. Boot server: This system provides network clients with the information they need to boot and install the operating system. 2. Profile server: This system hosts what the JumpStart documentation calls the nqhao file for networked installation clients. The nqhao file contains information on the profile to be used, as well as pre- a local floppy or optical media, if that’s a better option at your site. 3. Install server: This system contains the Solaris disk images used to install the Solaris operating system. One install server can support many different hardware Follow these steps to set up a new JumpStart installation host on our network: 1. 2. Set up the installation server role. a. Copy the Solaris installation media to the local disk. b. Share the installation media via NFS. 3. Set up the profile server. a. Copy the sample profiles from the Solaris installation media to a new profile directory. b. c. Customize the profile information for your first installation client. CHAPTER 6 SETTING UP AUTOMATED INSTALLATION 123 4. Add an installation client. 5. Boot the installation client and watch as unattended installation commences. hemingway (after the famous author), -5.*-24*-*./3. aurora, with the IP address -5.*-24*-*.04,46,,6.,64b63,6a]have placed aurora Setting Up the Install Server The first thing we’ll set up is the install server, which will host the Solaris installation files copied over using o_l: ig`en+ijp+_`nki hkbe]`i)]+fqilop]np+okh-,)ol]n_*eok ikqjp)knk)Bdobo)knk+`ar+hkbe+-+ijp+_`nki ikqjp)knk)Bdobo)knk+`ar+hkbe+-+ijp+_`nki _`+ijp+_`nki+Okh]neo[-,+Pkkho+ - age removable media (the default), simply change the directory to +_`nki+_`nki,+o,+ Okh]neo-,+Pkkho. ig`en)l+fqilop]np+Okh-,ol]n_ *+oapql[ejop]hh[oanran+fqilop]np+Okh-,ol]n_ Ranebuejcp]ncap`ena_pknu*** ?]h_qh]pejcpdanamqena``eogol]_abknpdaOkh]neo[-,lnk`q_p ?]h_qh]pejcol]_anamqena`bknpdaejop]hh]pekj^kkpei]ca ?kluejcpda?@ei]capk`eog*** ?kluejcEjop]hh>kkpEi]cadean]n_du*** Ejop]hhOanranoapql_kilhapa od]na command and cnal the pathname: CHAPTER 6 SETTING UP AUTOMATED INSTALLATION 124 od]naxcnal#+fqilop]np+Okh-,ol]n_# )+fqilop]np+Okh-,ol]n_nk(]jkj9, +ap_+`bo+`bop]^ file for an entry like this: od]na)Bjbo)knk(]jkj9,+fqilop]np+Okh-,ol]n_+ Add the entry it if it’s missing. Once that entry is in place, verify that the NFS service or_oÌhor_6+japskng+jbo+oanran6`ab]qhp If it’s not running, enable it with this command: or_]`iaj]^haor_6+japskng+jbo+oanran6`ab]qhp od]na]hh If you encounter problems, see the Sun docs here: dppl6++`k_o*oqj*_ki+]ll+`k_o+ `k_+4-3)11,0+2igr0jd/e;]9reew. The documentation is thorough, so you should be able to work out any problems. Setting Up the Profile Server The directory containing the nqhao file, the nqhao*kg file, and the profiles is called the JumpStart directory, and the server that hosts the JumpStart directory is called the profile server. First create the directories we’ll use: ig`en+fqilop]np+lnkbehao ig`en+fqilop]np+lnkbehao+]qnkn] _`+fqilop]np+lnkbehao+]qnkn] Next, copy over the sample profiles, which you’ll need to validate the new nqhao file (they’re also useful as a reference): _l)n+ijp+_`nki+Okh]neo[-,+Ieo_+fqilop]np[o]ilha+fqilop]np+lnkbehao+ Next, share out this directory over NFS by adding this line to +ap_+`bo+`bop]^: od]na)Bjbo)knk(]jkj9,+fqilop]np+lnkbehao CHAPTER 6 SETTING UP AUTOMATED INSTALLATION 125 jbo daemon: +qon+o^ej+or_]`inaop]npjbo+oanran Now validate the addition: +qon+o^ej+od]naxcnallnkbeha )+fqilop]np+lnkbehaonk(]jkj9, Creating the Profile The lnkbeha file is a text file that describes the software to be installed on a system. A pro- file describes aspects of the configuration such as the software group to install and the disk partition (slice) layout. The format is easy to understand, and because we’re taking advantage of the sample configuration files included with the Solaris installation media, we can simply modify an existing profile to suit our needs. The Sun online documentation is very good. For the complete syntax and all possible options for JumpStart profiles, please refer to dppl6++`k_o*oqj*_ki+]ll+`k_o+`k_+4-3)11,2+ lnal]na_qopki)1/00.;]9reas. fqilop]np[o]ilha directory: ls` +fqilop]np+lnkbehao+]qnkn] _l**+fqilop]np[o]ilha+dkop[_h]oo* irdkop[_h]oo^]oe_[lnkb ^]oe_[lnkb distribution with the package OQJS?T]hh, and we set up two filesystems and a swap slice. ^]oe_[lnkb: Ejop]hh[pulaejepe]h[ejop]hh Ouopai[pulaop]j`]hkja l]npepekjejcatlhe_ep behaouo_,p,`,o,-,,,,+ behaouo_,p,`,o--,.0os]l behaouo_,p,`,o3bnaa+klp _hqopanOQJS?T]hh The Ejop]hh[pula keyword is required in every profile. Besides ejepe]h[ejop]hh, other possible values for that keyword include qlcn]`a and bh]od[ejop]hh for upgrades and installations via a flash archive, respectively (a flash archive is a system image, not unlike a tarball snapshot of a system). The Ouopai[pula keyword specifies that the system is to be CHAPTER 6 SETTING UP AUTOMATED INSTALLATION 126 +klp filesystem. Next, we’ll test our profile. This step is optional but recommended. In place of +ijp+ _`nki ls` +fqilop]np+lnkbehao+]qnkn] +qon+o^ej+ejop]hh*`+lbejop]hh)@)_+ijp+_`nki+^]oe_[lnkb L]noejclnkbeha -6ejop]hh[pulaejepe]h[ejop]hh .6ouopai[pulaop]j`]hkja For this to work, you need to be on a system running the same OS version and hard- ware platform as the system for which you’re setting up the profile. See dppl6++`k_o*oqj* _ki+]ll+`k_o+`k_+4-3)11,2+lnal]na_qopki).14,4;]9reas for more details. The output of lbejop]hh goes on for many, many screens, but eventually should end with this: Ejop]hh]pekjhkchk_]pekj )+]+r]n+o]`i+ouopai+hkco+ejop]hh[hkc$^abknana^kkp% )+r]n+o]`i+ouopai+hkco+ejop]hh[hkc$]bpanna^kkp% Ikqjpejcnai]ejejcbehaouopaio Ejop]hh]pekj_kilhapa Paopnqj_kilhapa*Atepop]pqo,* Successful completion of lbejop]hh means that our profile is ready. Creating the sysidcfg File The ouoe`_bc file is a preconfiguration file you use to configure a wide variety of basic sys- tem settings, including but not limited to: Information Service) CHAPTER 6 SETTING UP AUTOMATED INSTALLATION 127 The ouoe`_bc file isn’t technically part of the profile (because it’s not included in the nqhao file); it’s used earlier than profile information in the JumpStart installation process. aurora’s JumpStart configu- ration files are kept, simply because it is convenient to do so. (For this reason, we describe it here in the section about setting up your profile server.) Like the rest of our JumpStart files, ouoe`_bc aurora in the +fqilop]np+lnkbehao+]qnkn] directory, with these contents: ouopai[hk_]ha9aj[QO paniej]h9rp-,, j]ia[oanre_a9@JOw`ki]ej[j]ia9_]ilej*japj]ia[oanran9-5.*-24*-*- oa]n_d9_]ilej*jap(dkia*_]ilej*japy japskng[ejpanb]_a9LNEI=NUw`ab]qhp[nkqpa9-5.*-24*-*- japi]og9.11*.11*.11*, lnkpk_kh[elr29jky oa_qnepu[lkhe_u9JKJA peiavkja9QO+L]_ebe_ peiaoanran9hk_]hdkop jbo0[`ki]ej9_]ilej*jap nkkp[l]ooskn`9BKKme0o>=N^]v SYSIDCFG AND IP ADDRESS ASSIGNMENT Note that you cannot specify the IP address of a Solaris system in the ouoe`_bc file after the system gets its IP address from Reverse Address Resolution Protocol (RARP) and the network- boot process (as we’re configuring here). The installation will fail when the host tries to find a matching rule in the nqhao*kg file—you’ll get an error that no matching rules were found. peiaoanran9hk_]hdkop so that the installation would assume that the in an interactive Solaris installation. The Custom JumpStart process uses the ouoe`_bc file to answer these questions automatically. CHAPTER 6 SETTING UP AUTOMATED INSTALLATION 128 For more information on the ouoe`_bc file, see the ouoe`_bc$0% man page or dppl6++ `k_o*oqj*_ki+]ll+`k_o+`k_+4-3)11,0+2igr0jd.i;]9reew. Creating the postinstall Script need to customize our system after the JumpStart installation is complete, but before the host boots for the first time. In many JumpStart scenarios, the system doesn’t boot all the way to the console login prompt, but pauses when partially done with the first boot and prompts the user for information about power management settings or the NFSv4 default domain setting. Our script works around those two issues, and also sets up cfen- this in the following explanation of our lkopejop]hh by section: +^ej+od L=PD9 L=PD6+qon+o^ej ig`en)i3,,+]+*ood a_dkood)`oo====>/Jv]?***F1Atqh_vM99j]pa<okiadkop:+]+*ood+]qpdkneva`[gauo nkkp account’s ]qpdkneva`[gauo file. This allows for secure and easy login to the system. Note The public key placed into the nkkp user’s authorized_keys file is shortened for the purposes of this book. You can find the code samples for this chapter, including the unabbreviated version of this script, in the Downloads section of the Apress web site ( dppl6++sss*]lnaoo*_ki). Note that JumpStart mounts the future root filesystem at +]+ the rest of this script. The next section of code is used to detect the version of Solaris that the system is running: KO[PULA9\qj]ia)no\ _]oa KO[PULAej OqjKO1*-,% [...]... O N The rest of the entries are well commented, and shouldn’t need any additional explanation This concludes our JumpStart script Creating the rules File file is a text file that contains a rule for each system or group of systems on to the system being installed A file entry can match a profile to a system based on the system s hostname or hardware attributes, or it can... Select Pre-Installation Script in the left-hand pane and leave the screen’s text box blank: Postinstallation Script Screen Select Post-Installation Script in the left-hand pane and paste in this small script to copy over some cfengine binaries and to run at boot: C HA P T E R 6 done! Save the file to S E T T I N G U P A U T O M A T E D I N S T A LLA T I O N 149 150 C HAPTER 6 SET TING U P A U TOMA... 145 146 SET TING U P A U TOMA TED INS TA L L A TI O N C HAPTER 6 Under S E T T I N G U P A U T O M A T E D I N S T A LLA T I O N C HA P T E R 6 Under right-hand pane: 147 148 SET TING U P A U TOMA TED INS TA L L A TI O N C HAPTER 6 ... 143 144 C HAPTER 6 SET TING U P A U TOMA TED INS TA L L A TI O N Display Configuration Screen another system if you need to, but otherwise you probably won’t need X on the host In C HA P T E R 6 S E T T I N G U P A U T O M A T E D I N S T A LLA T I O N Package Selection Screen Select the Package Selection entry in the left-hand pane... systems, so our script simply needs to copy the cfengine binary directory to the correct location on the local system, and run upon boot The script takes care of all of this 153 1 54 C HAPTER 6 SET TING U P A U TOMA TED INS TA L L A TI O N Setting Up Network Boot Now that we have our kickstart file ready, we need to set up network booting Trivial File Transfer Protocol (TFTP) and packages,... repository hosted at contains prepackaged freeware for Solaris systems It resembles the popular site, but we prefer Blastwave It is a community of capable developers and users adhering to high-quality standards for the software they upload to the site In addition, you accomplish installation of packages from the repository through a command-line interface tool The Blastwave tool is called ... U P A U TOMA TED INS TA L L A TI O N Creating the Installation Tree and Making It Available Use the command to verify that it is mounted properly: Now you can create the installation tree directory: Next, we need to set up the NFS server Navigate to System Server Settings to configure NFS: Administration C HA P T E R 6 Use the S E T T I N G U P A U T O... path is rt, but on our system it is installed in Try executing both paths inside a terminal window If you don’t have either, install the package and try again Basic Configuration Screen in the configuration with the settings from your existing system will make this process easier to change the password used for the new system The single most... entries to the file The settings in the file are handed out when clients boot using manual steps beyond the step Our host aurora, whose IP address is ing to its serial port and watching the boot messages: Now that our host aurora has all that it needs, we’ll boot it from the network Issue this command at the prompt: C HA P T E R 6 S E T T I N G... Server variant, and the Server directory we’ll set up is rhmaster) host’s IP ( for later installation (in our case it is ) Select In the ), and in Boot Loader Options Screen Next, select Boot Loader Options in the left-hand pane This panel will be disabled if you . on a system running the same OS version and hard- ware platform as the system for which you’re setting up the profile. See dppl6++`k_o*oqj* _ki+]ll+`k_o+`k_ +4- 3)11,2+lnal]na_qopki). 14, 4;]9reas. =qc.,,3?klunecdp$_%-555).,,3 Pdki]oH]jca8h]jca<ejbkni]peg*qje)gkahj*`a: ))))))))))))))))))))))))))))))))))))))))))))))))) ?]hhejcp]og[_kjb`en Ganjahl]n]iapano6ejepn`9ejepn`*eic).*2* -4) 1) 042 el9`d_l nkkp9+`ar+jbojbonkkp9+onr+b]e+jbonkkp^kkp9hera B=E[BH=CO9ran^koa(ood`(_na]parpB=E[=?PEKJ9ejop]hh >KKP[EI=CA9rihejqv).*2* -4) 1) 042 Once you’ve done the imaging and. -5.*- 24* -*./3. aurora, with the IP address -5.*- 24* -*. 04 ,46 ,,6.,64b63,6a]have placed
Ngày đăng: 14/08/2014, 02:20
Xem thêm: Automating Linux and Unix System Administration phần 4 ppsx, Automating Linux and Unix System Administration phần 4 ppsx
