Integrating HP tools for Linux deployment (HP SIM, SSSTK, LinuxCOE, and PSP)

Transcription

1 Integrating HP tools for Linux deployment (HP SIM, SSSTK, LinuxCOE, and PSP) HOWTO Abstract... 2 Pre-integration tasks... 2 Pre-integration configuration... 2 Dynamic Host Configuration Protocol (DHCP)...3 Domain Name Service (DNS)... 3 Network Time Protocol (NTP)... 3 Network File System (NFS)... 3 Trivial File Transfer Protocol (TFTP)... 3 Setting up installation repositories... 4 Creating a HP SIM Web launch tool for LinuxCOE...4 Configuring LinuxCOE... 5 Configuring SSSTK... 5 Deploying the PSP... 5 Using the deployment service... 8 Possible deployment service enhancements For more information Call to action... 19

2 Abstract The purpose of this HOWTO is to help experienced Linux administrators integrate HP tools to manage Linux deployments. The following HP tools provide the capability to manage the hardware, firmware, provisioning, and agent installation. These tools also provide a framework for monitoring and basic configuration management: HP Systems Insight Manager (SIM) SmartStart Scripting Toolkit (SSSTK) Linux Common Operating Environment (LinuxCOE) ProLiant Support Pack (PSP) Pre-integration tasks To prepare for installation, review the respective documentation and complete the following tasks: IMPORTANT The remainder of this document assumes you utilize the default locations and configurations for these tool installations. HP Systems Insight Manager Install HP SIIM; it will be configured as the primary management and deployment interface. For information on HP SIM, see _USEN. HP SmartStart Scripting Toolkit (SSSTK) Install the SSSTK onto the server configured with HP SIM. For information on the SSSTK, see Enhanced Scripts for Linux Overlay the Enhanced Scripts for Linux into the same installation path as the SSSTK. For information on the Enhanced Scripts for Linux, see Common Operating Environment (LinuxCOE) Install LinuxCOE as the provisioning web interface. For information on LinuxCOE, see HP ProLiant Support Pack (PSP) Obtain the desired versions of the PSP for your target systems. For information on the PSP, see 002_USEN. Pre-integration configuration For simplicity, all of the necessary components and services will be co-located on one deployment service host (referred to as LinuxDeploymentHost). This includes the four main tools, plus the ancillary items that are required to provide such a service for Linux target systems. Test the success of your installation process so far by access the following web interfaces: HP SIM LinuxCOE Begin the base integration for the Linux deployment implementation by configuring the following services on top of the existing installation of the four main tools: 2

3 Dynamic Host Configuration Protocol (DHCP) Domain Name Service (DNS) Network Time Protocol (NTP) Network File System (NFS) Trivial File Transfer Protocol (TFTP) Dynamic Host Configuration Protocol (DHCP) When integrating the HP tools, DHCP provides the primary link between the Linux deployment service and the Preboot execution Environment (PXE) and the Trivial File Transfer Protocol (TFTP) services. After configuring DHCP on a system, it can access a network bootable kernel and file system. The following is an example of the directives that apply to any hosts needing Linux deployments: next-server IPAddress ; filename pxelinux.0 ; The Linux deployment server can be designated as the IPAddress parameter for "next server," to provide the TFTP service for PXE booting so that all of the related files may be managed on a single host. DHCP is loosely coupled to the implementation. However, some level of synergy is achieved if this service resides on the same host as the Linux deployment service. Another possible configuration option is to couple this service with DNS through Dynamic DNS options so that it can update the hostname to IP mapping automatically. Domain Name Service (DNS) For both Dynamic DNS and Static DNS, make sure that the service is available for use in the environment. DNS is loosely coupled to the implementation. Network Time Protocol (NTP) Configure a reliable network time source. Make sure this service is running and that DHCP delivers such information to its DHCP offers. NTP is also a loosely coupled service. Network File System (NFS) Files are served to the host being installed over NFS. In particular, the Linux deployment host should export the following: The prefix of the SSSTK installation An area for SSSTK profiles, to store captured configuration information To configure SSSTK, complete the following /etc/exports entries and then restart the NFS services: /opt/ssstk *(ro,sync,no_root_squash) /opt/ssstk_profiles *(rw,sync,no_root_squash) Trivial File Transfer Protocol (TFTP) The TFTP service usually resides on the Linux deployment host, since many of the files are already there or generated there upon demand. With hosts capable of PXE, the network boot process relies on the DHCP next server directive, which points to the host offering this service. Copy, or link, the designated files of the SSSTK and Enhanced Scripts for Linux to your TFTP daemon's serving directory, and make sure that the filename designated in the DHCP settings is present and accessible. 3

4 Setting up installation repositories Most often, for community or freely available Linux distributions, the locations of Linux repositories referenced by the installed LinuxCOE instance will be satisfactory. If necessary, the repository references can be modified to point to local mirrors of the distribution, usually maintained via rsync. When deploying one of the Enterprise Linux offerings from Oracle, Novell, or RedHat, create a repository from the ISO images that are available for download with your registration or subscription. For this situation, a tool, such as mrepo, can create a repository, complete with apt or yum indices. In any of the above scenarios, make sure that LinuxCOE is configured to use the repositories by completing the following steps (all relative to the LinuxCOE installation prefix): Locate the respective file for the Linux distribution in the directory osvend.d. Copy the file to etc/osvend.d. Modify the six parameters following the OSVEND keyword to match the access path of the repository, accounting for the desired values regarding distribution, version, and architecture. Creating a HP SIM Web launch tool for LinuxCOE To integrate HP SIM and LinuxCOE, such that HP SIM can directly call this tool from its menus, follow these steps: 1. Create a temporary file as follows: NOTE Make sure to use appropriate values for the SomeUser and LinuxDeploymentHost placeholder tokens. <?xml version="1.0" encoding="utf-8"?> <tool-list> <web-launch-tool name="linuxcoe-systemdesigner" revision=" "> <category>local Tools</category> <description>linuxcoe SystemDesigner</description> <execute-as-user>someuser</execute-as-user> <toolbox-enabled value="true" /> <web-block accepts-targets="true"> <main-url> <target-format>%f%z%(,%f%z%)</target-format> </web-block> <attribute name="menu-path">deploy Operating System</attribute> <!--attribute name="target-frame">wjaframe</attribute--> </web-launch-tool> </tool-list> 4

5 2. From the command line of your HP SIM host, run (as root) the following command to complete this integration: mxtool -a -f FullPathToAboveFile 3. The new item displays in the Deploy -> Operating Systems menu. After selecting a target (or multiple), you will be able to work through the interface. Configuring LinuxCOE To configure LinuxCOE to deliver the necessary files to the target systems during network booting, complete the following steps: 1. Locate the etc/linuxcoe.rc file in the installation prefix for LinuxCOE. 2. Change the following lines: #SIM /SomeWritableDirectoryPath #POST_TRIGGER /opt/systemdesigner/4/test_trigger - To - SIM /opt/ssstk/data_files/coe_data POST_TRIGGER /opt/ssstk/extra_utils/linuxcoe/copy-coe-data 3. Save the etc/linuxcoe.rc file. 4. Reload the LinuxCOE interface from the HP SIM menu. After completing these steps, specify one or more serial numbers of your HP ProLiant server to associate with the installation. The server's serial number identifies the ProLiant server (as key for SSSTK) and can be found in the following locations: The serial number is listed on the outside of the shipping box and on the system itself. The serial number is visible from ilo access. The serial number can be determined for systems running Linux through the command line dmidecode utility. Configuring SSSTK To configure SSSTK to use the file that LinuxCOE now delivers, complete the following steps: 1. Locate the file /opt/ssstk/scripts/includes 2. Modify the contents, setting export LinuxCOE=1 Deploying the PSP To simplify PSP deployment, configure a Value-Add Module to be included with LinuxCOE deployments, by completing the following steps: 1. Obtain and download the latest PSP versions that match your particular hardware set and Linux distribution needs. 5

6 NOTE The following example uses the PSP version 8.25 for RedHat Enterprise Linux version Following the Value-Add Module documentation in the LinuxCOE administration guide to perform the following steps: 1. Locate the etc/linuxcoe.rc file in the installation prefix. 2. Modify the file to include the line ADDONS PSP. NOTE The PSP parameter can be appended, if the ADDONS line is already present. 3. In the LinuxCOE installation prefix, create the file PSP in the addons directory. Below is an example addons/psp file (path adjustments may be necessary for your local situation): ## # PSP Value-Add Module configuration: ## # CONFIG -> Absolute filesystem path to the Value-Add Module configuration file CONFIG /srv/linuxcoe/psp/8.25/psp.cfg # HELP_URL -> what path to present for 'Click on bundle for help' # # What entries in yum.conf reference this depot? YUM-RPM = { [PSP] name=proliantsupportpack baseurl=@method@@waystation@/linuxcoe/psp/8.25/yum/@distro@/@ VERSION@/@ARCH@ } DEFAULT-BUNDLES = { PSP-8.25 } 3. Create the actual repository to deliver the PSP to the target systems at installation time by completing the following steps: 1. Obtain the LinuxCOE SystemDesigner-contrib file: value-add-module.tar from the project download site, which has the basic structure of a Value-Add Module repository and tools to set up and maintain it. 2. Unpack value-add-module.tar in the directory /srv/linuxcoe/psp/

7 3. Move to the /srv/linuxcoe/psp/8.25 directory. 4. Create a PSP.cfg file for the module configuration to reference the bundle of packages you are installing. An example PSP.cfg file follows: PSP-8.25 : RedHat : 5.3Server : i386 : PSP-help.html : cpqacuxe, cpq_cciss, hpacucli, hpahcisr, hpdiags, hp-fc-enablement, hp-health, hp-ilo, hpmouse, hponcfg, hp-openipmi, hpsmh, hp-smh-templates, hp-snmp-agents, mptlinux 5. Setup the repository structure:./bin/setup-rpm RedHat 5.3Server i Unpack the PSP you downloaded into this newly created directory structure: cd RedHat/5.3/i386/RPMS tar -zxvf <PSPFileName> cd - 4. Create the yum indices by completing the following steps: 1. Ensure you have the createrepo packaged installed. 2. Move to the top-level of your module cd /srv/linuxcoe/psp/ Modify the content of etc/yum-ize.cf to match your respective settings and ensure you have the specified log directory setup with permissions allowing write for the user invoking the command. #! /bin/sh ORIGIN="HP" URL="/LinuxCOE" PREFIX="/srv/LinuxCOE" ADDON="PSP" ADDON_VER="8.25" COMPONENT="PSP" SRCDIR=${PREFIX}/${ADDON} TOPDIR=${PREFIX}/${ADDON}/${ADDON_VER}/yum export PATH=/usr/local/bin:$PATH LOGDIR=/var/log/yum-ize LOGFILE=${LOGDIR}/${ADDON}_`basename $0` SOURCES_LIST=${TOPDIR}/yum.conf 5. Invoke bin/yum-ize -F -f etc/yum-ize.cf. 7

8 Using the deployment service To use the Linux deployment service to install and configure a target system, complete the following steps: 1. Start the HP SIM homepage 2. Log in to the application. Figure 1. HP SIM homepage 3. Select Deploy > Operating System > LinuxCOE SystemDesigner, and then select a target ProLiant server to deploy. NOTE This integration is loosely coupled, in that the target selection is not applied to further LinuxCOE processing. 4. Choose the Boot Image option, and enter the serial number of one (or more) ProLiant servers. 8

9 5. Select the desired distribution, version, and architecture and then click Continue. Figure 2. LinuxCOE SystemDesigner 6. Select Custom - You choose what to install for System Profile, and then select the install method, boot image, and network interface for your environment. 9

10 7. Click Continue. Figure 3. Defining image parameters 10

11 8. Select a valid waystation and the localization settings for your environment, and then click Continue. Figure 4. Localization settings 11

12 9. In the bundles sections, ensure that the configured PSP displays or review that portion of the setup process. Select the file sets and the PSP bundle appropriate for your environment to install, and then click Continue. Figure 5. Components to install 12

13 10. Adjust the simple partitioning parameters for your environment, and then click Continue. Figure 6.Disk partitioning parameters 13

14 11. Review the settings, enter an install time root password, and then click Go For It!. Figure 7. Confirm data 14

15 12. After the image is created, a page appears that shows a set of files to boot from based on the target ProLiant serial number. Figure 8. File sets 13. Connect to the ilo console of the ProLiant server, either through the web interface or directly through the secure shell. 14. Start the boot process and press the F12 key during startup to perform a network boot. 15

16 15. When the SSSTK boot information displays, select Capture to boot the server, query, and store all the parameters. Figure 9. Server parameters 16. Upon completion, the system reboots using the network boot. Enter Toolkit to install the target system according to your designated LinuxCOE SystemDesigner preferences. Figure 10. Boot toolkit 17. The remaining process are unattended and complete as follows: 1. The SSSTK refreshes the stored hardware and firmware settings to the last captured state. 16

17 2. The SSSTK transfers the installation information to a temporary on-disk location. Figure 11. Deployment processes 18. The system reboots to complete the installation, and depending upon the settings, may even reboot into the final installed system. Figure 12. Installation completion 17

18 After the above process completes, the configuration is complete. Figure 13. Installation complete Possible deployment service enhancements The deployment services outlined in this document provide the ability to design an HP ProLiant server, with its associated serial number, to receive a Linux deployment. By integrating the various component services, a completed server can be installed with minimal manual interaction. Possible enhancements for the deployment process could include the following: The HP SIM LinuxCOE integration is still loosely coupled at this point. It would be nice to have the target selection deliver the appropriate serial number, and then help launch the respective ilo interface. The SSSTK can also perform firmware upgrades. This can be done by integrating the HP Smart Update Manager. Explore the other modes of the LinuxCOE, especially the use of profiles and the capability to retrofit value-add modules on an existing system. As configured above, the PSP installs only on the target system. Given some further configuration, the PSP agents can be pointed at HP SIM to deliver traps and notifications to your control panel. Additionally, you can utilize the HP Software Delivery Repository to obtain and install the PSP. 18

19 For more information For additional information, refer to the resources listed below. Resource Hyperlink HP Linux Common Operating Environment (LinuxCOE) ProLiant Support Pack mrepo p/index.html?jumpid=reg_r1002_usen rsync SmartStart Scripting Toolkit HP Enhanced Scripts for Linux (SSSTK) HP Software Delivery Repository tion.html#scr HP Linux Common Operating Environment (LinuxCOE) ProLiant Support Pack p/index.html?jumpid=reg_r1002_usen Call to action Send comments about this paper to: 2009 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. AMD, AMD Opteron, and AMD-V are a trademark of Advanced Micro Devices, Inc. Intel and Itanium is a or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries Microsoft, Windows Server, and Hyper-V are US registered trademarks of Microsoft Corporation. TC091201HT, December 2009