How To Add A Linux Update, Service Pack, Or Edition
Article: 20000017
Applies to: Release 6.x onwards
The provided Linux jobs and files may be used as a template to deploy other
Linux updates, service packs, editions, or architecture types.
IMPORTANT: A newer update or service pack may require a code change to
deploy with your current release. If this is the case, then an updated feature
that states support for that update or service pack will be required.
To create a new Linux feature:
| 1. |
On the Deployment Server, copy and rename a related feature folder in <InstallPath>\hpfeatures.
In the new feature, delete the jobs and dist subfolders. Create a dist
subfolder and copy the new distribution to it.
|
| 2. |
In the subfolders, oem\components and oem\drivers (if exists), remove the component and driver files
and replace with the versions specific for this new Linux feature. The oem\drivers folder contains drivers required by the
existing Linux version in order to complete a scripted install, for example, a driver for a network interface card that
doesn't exist in the distribution. The Linux distribution you are adding may already have the driver and doesn't require the
newer driver.
IMPORTANT: The hp-health package is required to install the one-time boot to PXE
functionality on the production operating system. If this package is not installed, the
target will not automatically boot PXE after the operating system is installed.
|
| 3. |
For several distributions to deploy on supported targets,
a modified initrd file is required for a network interface card driver.
Replace the file in the oem subfolder with the version specific for this new feature.
When renaming the file to initrd, be aware that for Windows 2008 the default option
in Windows Explorer is set to Hide extensions for known file types which may cause the file to retain the .img extension.
IMPORTANT: For SLES11 SP1 X86 Successful Deployment user has to Remove or Replace the initrd with appropriate update in the "\hpfeatures\sles11sp1-x86\oem\osupdates" folder then start the deployment.
|
| 4. |
Using a Linux compatible editor, edit the kickstart or control file for any package/rpm changes and
the remove the call to ./drivers/install.sh if newer drivers are not required.
|
| 5. |
In the Deployment Console, copy and rename a related scripted install job and
edit the tasks to use the new feature folder.
For those tasks that are required to run in Linux Managed automation, continue to have them run in the x64 environment.
| a. |
Distribute Disk Image, update the path to GRUB.IMG
IMPORTANT: When using the browse button to update the image file to the new location,
the advanced properties are changed back to defaults.
For a target server with a large amount of storage, greater than 1 TB, the FAT32 partition inside the image
must be set to a small fixed size, e.g. 150MB.
|
| b. |
Run Script - Configure Boot Environment, update the path to configuregrub.sh
Additionally, Red Hat Enterprise Linux 5.4 x86, SUSE LINUX Enterprise Server 10 SP3 x86, and SUSE LINUX Enterprise Server 11 x86
require a special kernel parameter to install on ProLiant G7 series servers that contain an AMD processor. Edit this task
to include the kernel parameter and uncomment/remove the # sign from the export kernparam= line:
For RHEL 5.4 x86 and SLES 11 x86:
export kernparam="apic=bigsmp"
For SLES 10 SP3 x86:
export kernparam="pci=nomsi"
|
| c. |
Run Script - Configure Answer File, update the path to configurexxx.sh file
|
| d. |
Install Package, update the path to xxx-post.sh
|
|
|
Printable version
