|
 Sun xVM Ops Center 1.1 Home Updating and Patching |
In Sun xVM Ops Center, you can upload and install packages on the managed hosts. Depending on the package, the user can develop scripts, binaries, executables for probes, pre- and post installation jobs for the package. The Sun hosted tier lists the certified components that are available for download from the vendor's site. You have to download the certified components from the vendor's site and locally upload them to the satellite.
Package Formats
The supported package formats are PKGs, RPMs, package stream directories, tar files and jar files.
Use the option Add Software Packages and Uploading Components from a Local Directory in the Sun xVM Ops center to upload the packages and make them available in the Components list. Use Add Software Packages to upload packages of the format PKG and RPMs. You can upload multiple packages using the option Uploading Components from a Local Directory which is not possible using Add Software Packages.
You can also Upload Components from an OS image. You can view uploaded components history in View Upload History option. You can confirm that the components are uploaded onto the following directory of the satellite:
- Solaris OS: /opt/SUNWuce/server/public/private_blobs/CHANNEL_NAME
- Linux OS: /usr/local/uce/server/public/private_blobs/CHANNEL_NAME
The packages should not require user interaction for installation. If the packages have request and response file for installation, use the package wrapper scripts for installation. Refer to the Attachments in this page for the package wrapper script. This wrapper script consists of two scripts: install-pkgadd-fix.sh and undo-pkgadd-fix.sh. Upload the install-pkgadd-fix.sh as Pre-Action script and undo-pkgadd-fix as Post-Action script. Create profiles with these scripts and execute the install-pkgadd-fix.sh script before installing the package and execute the undo-pkgadd-fix.sh script after installing the package.
Viewing Packages in the Components list
The Sun Certified components will be listed in the Packages Components list and the non-certified components will be listed in the Local Components list.
Ideal Job Details for Installing a Package
Create profiles with the uploaded packages, pre-, post and probe scripts, and configuration files.
An ideal job tasks for installing a package would be to:
- Check the system requirements for installing a package. Use Probes scripts to test the managed hosts whether to carry out the installation. For example, check to make sure the system has 512 MB of RAM.
- Run job with pre-action profile before installing the package. Use Pre-Actions scripts to run tasks before carrying out the installation. For example, running the package wrapper script for packages that contain response and request files.
- Run job with package profile to install the package.
- Run job with post-action profile after installing the package. Use Post-Actions scripts to run tasks after installation. For example, executing the script undo-pkgadd-fix to remove the wrapper fix.
- Run job with configuration file profile for the package.
Group all these jobs and run in sequence with the failure policy as Stop at failure and Notify.
Sign up or Log in to add a comment or watch this page.