This procedure shows you how to create a profile for use with Solaris Live Upgrade. You can use this profile to upgrade an inactive boot environment by using the luupgrade command with the -j option.
For procedures to use this profile, see the following sections:
For an upgrade with a profile, see To Upgrade With a Profile by Using Solaris Live Upgrade (Command-Line Interface).
For a Solaris Flash installation with a profile, see To Install a Solaris Flash Archive With a Profile (Command-Line Interface).
Use a text editor to create a text file.
Name the file descriptively. Ensure that the name of the profile reflects how you intend to use the profile to install the Solaris software on a system. For example, you might name this profile upgrade_solaris9.
Add profile keywords and values to the profile.
Only the upgrade keywords in the following tables can be used in a Solaris Live Upgrade profile.
For an installation using the Install_type keyword values of upgrade or flash_install, see Table 33–2.
For an installation using the Install_type keyword value of flash_update, see Table 33–3.
Keyword |
Description |
---|---|
(Required) Install_type |
Defines whether to upgrade the existing Solaris environment on a system or install a Solaris Flash archive on the system. Use the following values with this keyword:
|
(Required for a Solaris Flash archive) archive_location |
Retrieves a Solaris Flash archive from a designated location. For a list of values that can be used with this keyword, see archive_location Keyword. |
(Optional) cluster (adding or deleting clusters) |
Designates whether a cluster is to be added or deleted from the software group that is to be installed on the system. For a list of values that can be used with this keyword, see cluster Profile Keyword (Adding Software Groups). |
(Optional) geo |
Designates the regional locale or locales that you want to install on a system or to add when upgrading a system. For a list of values that can be used with this keyword, see geo Profile Keyword. |
(Optional) isa_bits |
Specifies whether 64-bit or 32-bit Solaris 9 packages are to be installed. For a list of values that can be used with this keyword, see isa_bits Profile Keyword. |
(Optional) local_customization |
Before you install a Solaris Flash archive on a clone system, you can create custom scripts to preserve local configurations on the clone system. The local_customization keyword designates the directory where you have stored these scripts. The value is the path to the script on the clone system. For information on predeployment and postdeployment scripts, see Creating Customization Scripts. |
(Optional) locale |
Designates the locale packages you want to install or add when upgrading. For a list of values that can be used with this keyword, see locale Profile Keyword. |
(Optional) package |
Designates whether a package is to be added to or deleted from the software group that is to be installed on the system. For a list of values that can be used with this keyword, see package Profile Keyword. |
Table 33–3 Solaris Live Upgrade Profile Keywords and Descriptions For Creating a Differential Archive
Keyword |
Description |
---|---|
(Required) Install_type |
Defines the installation to install a Solaris Flash archive on the system. The value for a differential archive is flash_update. |
(Required) archive_location |
Retrieves a Solaris Flash archive from a designated location. For a list of values that can be used with this keyword, see archive_location Keyword. |
(Optional) forced_deployment |
Forces the installation of a Solaris Flash differential archive onto a clone system that is different than the software expects. If you use forced_deployment, all new files are deleted to bring the clone system to the expected state. If you are not certain that you want files to be deleted, use the default, which protects new files by stopping the installation. |
(Optional) local_customization |
Before you install a Solaris Flash archive on a clone system, you can create custom scripts to preserve local configurations on the clone system. The local_customization keyword designates the directory where you have stored these scripts. The value is the path to the script on the clone system. For information about predeployment and postdeployment scripts, see Creating Customization Scripts. |
(Optional) no_content_check |
When installing a clone system with a Solaris Flash differential archive, you can use the no_content_check keyword to ignore file-by-file validation. File-by-file validation ensures that the clone system is a duplicate of the master system. Avoid using this keyword unless you are sure the clone system is a duplicate of the original master system. |
(Optional) no_master_check |
When installing a clone system with a Solaris Flash differential archive, you can use the no_master_check keyword to ignore a check of files. Clone system files are not checked. A check would ensure the clone was built from the original master system. Avoid using this keyword unless you are sure the clone system is a duplicate of the original master system. |
Save the profile in a directory on the local system.
Ensure that root owns the profile and that the permissions are set to 644.
Test the profile (optional).
For a procedure to test the profile, see To Test a Profile to Be Used By Solaris Live Upgrade.
In this example, a profile provides the upgrade parameters. This profile is to be used to upgrade an inactive boot environment with the Solaris Live Upgrade luupgrade command and the -u and -j options. This profile adds a package and a cluster. A regional locale and additional locales are also added to the profile. If you add locales to the profile, make sure that you have created a boot environment with additional disk space.
# profile keywords profile values # ---------------- ------------------- install_type upgrade package SUNWxwman add cluster SUNWCacc add geo C_Europe locale zh_TW locale zh_TW.BIG5 locale zh_TW.UTF-8 locale zh_HK.UTF-8 locale zh_HK.BIG5HK locale zh locale zh_CN.GB18030 locale zh_CN.GBK locale zh_CN.UTF-8 |
The following example of a profile is to be used by Solaris Live Upgrade to install a differential archive on a clone system. Only files that are specified by the differential archive are added, deleted, or changed. The Solaris Flash archive is retrieved from an NFS server. Because the image was built by the original master system, the clone system is not checked for a valid system image. This profile is to be used with the Solaris Live Upgrade luupgrade command and the -u and -j options.
# profile keywords profile values # ---------------- ------------------- install_type flash_update archive_location nfs installserver:/export/solaris/flasharchive/solaris9archive no_master_check
To use the luupgrade command to install the differential archive, see To Install a Solaris Flash Archive With a Profile (Command-Line Interface).