Migrating packages from legacy to modular style

If the control script’s customer-defined section calls any of the following functions, the external script needs to be

edited to update the names as follows:

Table 1. Replaced control script functions

Function Replacement

ps_tree sg_ps_tree

show_users sg_show_users

Table 2. Unsupported control script functions

Disown_dtc

get_ownership_dtc

ha_nfs_file_locks

Disown_dtc

Migrating a simple package

If a package does not have a customer-defined user script and does not include any of its own environment variables in

the package control script, follow these broad steps below (see the examples below for details):

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

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

3. Halt the package.

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

5. Run the package.

The following example migrates the simple package pkg_simple:

Examine the package using cmviewcl

cmviewcl -v -f line -p pkg-simple

name=pkg-simple

type=failover

status=down

state=halted

highly_available=no

summary=critical

autorun=disabled

owner=unowned

id=41475

initial_autorun=enabled

failover_policy=configured_node failback_policy=manual

local_lan_failover_allowed=enabled failfast=disabled

run_script=/etc/cmcluster/pkg/pkg-simple/pkg-simple.control run_script_timeout=320

halt_script=/etc/cmcluster/pkg/pkg-simple/pkg-simple.control

halt_script_timeout=320

priority=no_priority