Migrating packages from legacy to modular style

24
Input options
-t Displays a preview of what the command does.
legacy_package_name
Name of an existing toolkit legacy package to migrate. If the specified toolkit package has any dependent packages,
then modular configuration files are generated only for dependent CFS mount point and/or disk group, and toolkit
packages.
-c cfs_package_names
Specify the legacy and/or modular CFS package names to be consolidated. Supports only disk group and mount point
packages. You can consolidate the disk groups and mount points into individual packages or into a single package. To
consolidate multiple packages into a single package, specify the disk groups and mount points separated by a colon (:).
-o output_directory
The directory where the generated modular configuration files have to be placed.
• If the -o output_directory option is not specified then the modular package configuration files created are placed in
the following locations:
– A directory each with name <pkg_name>_MODULAR is created for the toolkit package and its dependent toolkit
packages. These files are placed in the respective /etc/cmcluster/<pkg_name>_MODULAR directories.
– For all CFS packages, the files are placed in /etc/cmcluster/cfs directory.
Package parameter changes for CFS packages
script_log_file
The generated modular package configuration file will have script_log_file set to
/var/adm/cmcluster/log/<pkg_name>.log
package_name
When you consolidate multiple CFS Mount Point &Disk Group packages, the package_name will be different from the CFS
package names which are specified in the command. cmeasymigrate takes the first package specified with -c option and
extracts cfs_mount_point and cvm_disk_group parameter from the package and appends it with the prefix “cfs_agg” to
generate the new modular package name.
Migrating a toolkit package without any dependencies
If the toolkit package doesn’t have any dependencies follow the broad steps mentioned below.
1. cmeasymigrate <toolkit_pkg> and generate the new modular configuration file
2. Halt the toolkit legacy package using cmhaltpkg.
3. Verify the new modular configuration file using cmcheckconf.
4. Manually verify the external script generated by cmeasymigrate.
5. Apply the new modular configuration file using cmapplyconf.
6. Bring up the modular package using cmrunpkg.
Note: If a toolkit package does not have any dependencies, the modular package configuration file generated by cmeasymigrate can be
applied without deleting the legacy package from the cluster.