Migrating packages from legacy to modular style

8
Checklist for migrating a legacy package
Check legacy packages for the following to determine how to migrate the package:
1. Package parameters that are not supported in 11.18
o See the Unsupported Package Parameters table.
2. Any of the following in the package control script:
o Non-Serviceguard parameters:
i. If any non-Serviceguard parameters are defined, note the parameter names
ii. Look at the Serviceguard control script Parameters tables below
cmmigratepkg lists any parameters that are non-Serviceguard parameters
Determine where the non-Serviceguard parameters are defined in the control script:
• If the parameters are defined between the “#START OF CUSTOMER DEFINED” and
“#END OF CUSTOMER DEFINED”, cmmigratepkg can copy the code to the new external script if you
use the -x option to generate an external script
• If the parameters are defined elsewhere in the script, they can be converted to PEVs
• User-created scripts must be modified to use the new environment variable names
o Non-Serviceguard functions:
i. Determine if there are any non-Serviceguard functions in the package control script. If the package
control script was generated using cmmakepkg -s, and no additional functions were added, then there are
no non-Serviceguard functions. Otherwise, check the
Unsupported control script functions and Replaced
control script functions tables. Check whether any of these functions are in the package’s control script.
Run cmmigratepkg and see if the command lists any non-Serviceguard functions.
ii. If the functions are defined between the “#START OF CUSTOMER DEFINED FUNCTIONS” and “#END of
CUSTOMER DEFINED FUNCTIONS”, cmmigratepkg can copy them to an external script if you use
the -x option.
iii. If the functions are not in the customer-defined area of the control script, and are listed under
Unsupported control script functions, then you must manually edit the external script to use the
new names.
iv. If the functions are not covered by any of cases ii-iv above, then you must manually add them to the
external script.
o Modifications to Serviceguard functions
i. Determine if any modifications have been made to any Serviceguard functions defined in the Serviceguard
package control script template. Someone well acquainted with the code in the package control script
must determine this; it entails reviewing the code and manually comparing the Serviceguard template
with this package’s control script.
ii. If there are modifications to any of the Serviceguard package control script functions, and they must be
included in the new package, then you cannot migrate the package.
3. Make sure the subnet and ip_address parameters defined in the legacy package’s control script are defined in the
cluster configuration file as ST
ATIONARY_IP addresses for the nodes in the cluster. If the package includes a subnet
and ip_address that are not configured as a STATIONARY_IP address in the cluster configuration file, add the subnet
as a monitored subnet by adding the address as a STATIONARY_IP to the cluster configuration file. Then, apply the
new cluster configuration. (cmmigratepkg may complete successfully if you fail to do this, but the resulting
package will not run.) See the Managing Serviceguard manuals for HP-UX servers and Linux servers for more
information about the cluster configuration file, and information on applying the configuration.