HP Insight Control for Linux 6.0 User Guide

NOTE: The RPMs for these PSPs are OS- and platform-specific and are named as such, for
example, the HP ProLiant Channel Interface for Red Hat Enterprise Linux 4 (x86_64).
9.3 Creating a PSP dependency script
Some of the utilities contained in the PSP have RPM dependencies that must be met in order for
them to install correctly. These dependencies are documented in the HP ProLiant Support Pack
User Guide and are not listed here.
NOTE: For instructions on how to obtain the HP ProLiant Support Pack User Guide, see
Section 24.3.2 (page 262).
HP Insight Control for Linux does not automatically resolve these dependencies. If you plan to
install a PSP on your managed systems, you must ensure that the required RPMs are installed
first. Otherwise, the PSP installation fails
One way to solve this problem is to install the appropriate packages at installation time. If you
are using Insight Control for Linux installation tools to install your managed system, you can
simply modify the appropriate Kickstart or AutoYaST file and add the required packages to the
list of software that will be installed.
If the managed system is already installed, HP Insight Control for Linux provides a mechanism
called a PSP dependency script, which can automatically install required RPMs on a managed
system just before a PSP is installed.
PSP dependency scripts are shell scripts that are run as part of the Deploy→Deploy Drivers,
Firmware, and Agents→Install ProLiant Support Pack (PSP)... task.
For a PSP dependency script to be called during the PSP installation process, you must register
it; it appears in the /opt/repository/pspscript/example_dependency.sh directory on
the CMS. A remote repository cannot host a PSP dependency script.
You must use the default example_dependency.sh script in the /opt/repository/
pspscript/example_dependency.sh directory as a template for your customized script,
which you must register. Do not modify the example_dependency.sh script. The default
example_dependency.sh script does not perform any actual tasks. It only contains comments
with helpful suggestions about how to create a real dependency script.
Remember that the items in the Insight Control for Linux repository are served to the managed
systems through HTTP over the default repository web server port (usually port 60000). Therefore,
in your dependency script, include code to install required packages directly from the repository
web server.
Example 9-1 provides an example of a simple PSP dependency script that installs the
kernel-devel RPM for RHEL4 Update 6 from the repository web server located at IP address
172.0.0.4. This script assumes that RHEL4 U6 has already been registered and copied to the
repository.
Example 9-1 Simple PSP dependency script
#!/bin/sh
# Install the required RPM
rpm -i
http//172.0.0.4:60000/os/RHEL4ESU6-x64/RedHat/RPMS/kernel-devel-2.6.9-67.EL.x86_64.rpm
# Exit with 0 status - a non zero status will generate an error
exit 0
Managed systems are rebooted when the PSP installation script is finished, regardless of the
outcome of the PSP installation. The reboot is required so that HP SIM can continue to properly
manage the managed system ensures that all drivers and agents are properly started.
106 Installing PSPs on managed systems