Migrating packages from legacy to modular style

usivewrite"

deactivation_retry_count 2

kill_processes_accessing_raw_devices NO

vxvol "vxvol -g \$DiskGroup startall"

fs_umount_retry_count 1

fs_mount_retry_count 0

concurrent_vgchange_operations 1

concurrent_fsck_operations 1

concurrent_mount_and_umount_operations 1

script_log_file /var/opt/sgtest/tmp/cmcluster/pkg-

simple/pkg-simple.log

Halt the package.

$cmhaltpkg pkg-simple

Check the configuration of the new package.

$cmcheckconf -P pkg-simple.conf

cmcheckconf: Verification completed with no errors found.

Use the cmapplyconf command to apply the configuration.

Apply the new configuration.

$cmapplyconf -P pkg-simple.conf

Modify the package configuration ([y]/n)? y

Completed the cluster update

Start the package.

$cmrunpkg pkg-simple

Migrating a package with customer-defined functions

If the package includes a user-defined script, or the control script contains non-Serviceguard functions in the

customer-defined functions area, follow these steps:

1. Run the cmmigratepkg command and generate a new modular package configuration file and external script file:

$cmmigratepkg -p pkgA -x /etc/cmcluster/pkg/pkgA/myexternal.sh -o pkgA.conf

2. Make sure that the location of the external script is correct in the output modular package configuration file.

(The -x option is programmed to expect the full pathname of the external script.)

3. Copy the external script file to each node where the package can run, and make sure that the script is owned by root

and permissions are set to 744.

4. Run cmcheckconf with the new modular package configuration file.

5. Halt the package.

6. Run cmapplyconf with the new modular package configuration file.

7. Run the package.

Note: cmmigratepkg wrongly sets permissions to 555; you need to reset them manually to 744.

cmmigratepkg wrongly sets permissions to 555; you need to reset them manually to 744.