3 creating a spp or psp dependency script – HP Insight Control Software for Linux User Manual
Page 137
1
This agent is installed on servers with iLO 4 management processors. While HP SIM requires hp-ams so that it can use
embedded features of the iLO 4 management processor, Insight Control for Linux does not use it. If you want to use only
the hp-ams agent on your iLO 4–based servers, you must manually remove the other agents.
The Agentless Management Service (AMS) will be responsible for sending all host operating system-specific to the iLO
4 firmware.
2
This component is only required for RHEL5 and SLES10 operating systems.
NOTE:
The RPMs for these SPPs and PSPs are OS- and platform-specific and are usually named
as such.
13.3 Creating a SPP or PSP dependency script
Some utilities contained in the SPP or PSP have RPM dependencies that must be met for them to
install correctly. For PSPs, these dependencies are documented in the HP ProLiant Support Pack
User Guide.
TIP:
For instructions on how to obtain the HP ProLiant Support Pack User Guide, see
.
Insight Control for Linux does not automatically resolve these dependencies. If you plan to install
an SPP or 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 Kickstart or AutoYaST file and add the required packages to the list of software to be
installed.
If the managed system is already installed, Insight Control for Linux provides mechanisms called
s and
s, which can automatically install required
RPMs on a managed system just before an SPP or a PSP is installed.
SPP and PSP dependency scripts are shell scripts that are run as part of the Deploy
→Deploy Drivers,
Firmware, and Agents
→Install SPP or PSP... task.
For an SPP or a PSP dependency script to be called during the SPP or PSP installation process, you
must register it; the script appears in the /opt/repository/pspscript/
example_dependency.sh
directory on the
. A
cannot host an SPP or 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. SPP and PSP dependency scripts are stored in the same location. 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
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.
provides an example of a simple PSP dependency script that installs the kernel-devel
RPM for RHEL6 Update 2 from the repository web server located at IP address 172.0.0.4. This
script assumes that RHEL6 U2 was already registered and copied to the repository.
Example 4 Simple PSP dependency script
#!/bin/sh
# Install the required RPM
rpm -i
13.3 Creating a SPP or PSP dependency script
137