 |
» |
|
|
|
|  | |
This section provides guidance on the various ways in which you can set up three components: a workstation, a boot mechanism, and a repository. The server replication process depends on these components. Selecting a Workstation | |
The workstation is any PC, equipped with a CD writer (and in some cases USB or PXE capability), running any distribution of Linux. You use the workstation to download the SSTK, unpack the SSTK software package, edit the sample scripts, and create a bootable device. You can also use the workstation to host the repository of custom scripts, utilities, hardware configuration files, OS files, and application files. Selecting a Boot Mechanism | |
The SSTK supports three boot mechanisms—CD, USB flash or network boot via a PXE-enabled NIC. The boot mechanism holds the files that boot the server to the toolkit environment and run the main script. The main script gets configuration files, OS files, and application files from the repository, configures the hardware, and installs the software. You can also use a USB flash device, or a network share to host the repository, which gathers all run-time components in one place. Several factors affect your choice of the boot mechanism: Capacity: The choice between CD and other devices is a function of the capacity of the disk. You may not be able to use a CD if you plan to host the repository (including the OS files along with the configuration files, scripts, and utilities) on the same device as the boot files (toolkit environment). Flexibility: The choice between a CD and USB flash drive is determined by the flexibility you need from the toolkit environment and custom scripts. You can quickly edit the Linux boot loader configuration file, a script, or configuration file on a USB flash device though burning a new CD is more complicated. Complexity: The choice between a network boot and a boot device depends on the scope and complexity of your deployment. If you plan to set up over a hundred servers at a time, you should invest in a PXE-enabled installation environment in which the HP Integrity servers boot over the network. On the other hand, if you plan to deploy your servers in more measured increments, the device drives may be an optimal solution. You could burn a dozen CDs at a time, insert each in an HP Integrity servers, reboot, and return to a dozen managed servers.
Configuring the Repository | |
Every server that boots to the SSTK environment must have access to the repository of configuration files, scripts, utilities, OS files, driver files, and application files. The Linux boot loader configuration file, which must be manually edited as described in Chapter 4, specifies the default location of the repository. It can be modified to specify a repository location of your choosing thereby customizing the SSTK environment. If you host the repository on the workstation, the repository must be accessible to the HP Integrity servers being deployed. If, for example, your workstation is on a public network and the servers are on a private isolated network, the SSTK can not work. If you host the repository on a boot device, be sure the device has enough capacity to hold both the SSTK environment and the OS. Using Repository Creation ScriptsThe following scripts are provided to aid you in the creation of your repository: These scripts are located in the utilities/linux/ directory within the SSTK package. To use either of the repository creation scripts, use the following steps: As root, extract the SSTK-LinuxIntegrity-3.1.tgz package, located on your HP Integrity CD, into the directory location that to host the repository. For example, creating the repository in the repository directory you would use the following commands: cp SSTK-LinuxIntegrity-3.1.tgz /repository cd /repository tar zxvf SSTK-LinuxIntegrity-3.1.tgz Run the repository creation script, mkrep.sh, as follows: # cd SSTKLnx3.1/repository/utilities/linux # ./mkrep.sh The SSTK Repository Maker Linux distribution selection menu is displayed. Select the appropriate Linux distribution, and then select OK. An SSTK Repository Maker menu similar to the following is displayed. The Repository Maker main menu provides the three tasks required to create your repository. Default configurations are provided for the destination directory and CD mount points that can be used to immediately create the repository with the Make Repository selection. The Destination Directory default is the directory into which you extracted the SSTK-LinuxIntegrity-3.1.tgz package. The default CDROM devices is /dev/cdrom. To use the default repository configuration skip to the next step, or use the following steps to configure specific repository information: Select Destination Directory and click OK. Select the destination directory by navigating to the correct directory, and then click OK. Select CDROM Device and click OK. Select your CD/DVD device by navigating to the correct directory, and then click OK.
Select Make Repository and click OK. The script creates the necessary directories, files, and symbolic links. You are prompted to insert the OS distribution media, in order, during this process; an error occurs if the expected media is not inserted. Insert the OS distribution media as prompted to complete the repository creation. | | | |  | NOTE: If you are installing SLES9SP3 or SLES9SP4, you must insert the SLES9 media first. Once all files are installed, you are prompted to insert the service pack media. | | | | |
To exit the script, select Exit and click OK. The repository structure created in the /repository/SSTKLnx3.1 directory is as follows: SSTKLnx3.1/
|-- SSTK_DeploymentGuide.pdf
|-- SSTK_DeploymentGuide.txt
|-- boot_files
| `-- efi
| `-- boot
| |-- bootia64.conf
| |-- bootia64.efi
| |-- elilo.conf
| |-- elilo.efi
| |-- linux
| `-- rootfs.gz
|-- data_files
|-- os
| |-- rhel4up4-profile
| |-- rhel4up5-profile
| |-- rhel4up6-profile
| |-- rhel5-profile
| |-- rhel5up1-profile
| |-- sles10sp1-profile
| |-- sles9sp3-profile
| `-- sles9sp4-profile
|-- readme.txt
|-- scripts
| |-- capture.sh
| |-- capture_linux_image.sh
| |-- deploy.sh
| |-- deploy_hba.sh
| |-- deploy_linux_image.sh
| |-- imgfunctions.sh
| |-- linux-setup.sh
| |-- main_toolkit_launch.sh
| |-- raid1-lsi.sh
| |-- rhel_setup.sh
| |-- sles_setup.sh
| `-- sstk.conf
|-- software
| |-- EFI_TOOLS
| |-- rhel4up4
| |-- rhel4up5
| |-- rhel4up6
| |-- rhel5
| |-- rhel5up1
| |-- sles10sp1
| |-- sles9sp3
| `-- sles9sp4
|
|
|
`-- utilities
|-- CLMChecking
|-- allboards.xml
|-- cfggen
|-- conrep
|-- conrep.xml
|-- cpqacuxe
| |-- bld
| | |-- acu.xml
| | |-- ipcelmclient
| | |-- ipcelmclient.php
| | |-- libLLPI.so
| | |-- libcpqhmmo.so
| | |-- libcpqimgr.so
| | |-- libhwmim3.so
| | |-- libossingleton.so
| | |-- locks
| | `-- upgrade.txt
| |-- cpqacuxe
| `-- cpqacuxe.license
|-- dumppci
|-- efibootmgr
|-- efivar
|-- gen-setupldr-options
|-- getuuid
|-- hplpcfg
|-- hpqlarep
|-- hpsetacpi
|-- hpshowdisk
|-- hwdisc
|-- hwquery
|-- ifhw
`-- linux
|-- getmediacode.sh
|-- mke2fs
|-- mkrep-rhel4up4.sh
|-- mkrep-rhel4up5.sh
|-- mkrep-rhel4up6.sh
|-- mkrep-rhel5-dvd.sh
|-- mkrep-rhel5.sh
|-- mkrep-rhel5up1-dvd.sh
|-- mkrep-rhel5up1.sh
|-- mkrep-sles10sp1-dvd.sh
|-- mkrep-sles10sp1.sh
|-- mkrep-sles9sp3.sh
|-- mkrep-sles9sp4.sh
`-- mkrep.sh
|
| | | |  | IMPORTANT: A repository solution is not limited to the previous examples. You can develop a hybrid solution if that works for you. For example, you can boot the model server from a USB flash device, host the repository on the workstation to read the configuration of the model server, customize the scripts and files, create a bootable CD for testing on a few servers, and then set up a network-based installation for a full-scale deployment. | | | | |
|
Printable version
