HP Serviceguard Enterprise Cluster Master Toolkit User Guide (5900-2145, April 2013)

The following Attribute Definition File (ADF) is installed in /etc/cmcluster/modules/ecmt/
mysql.
Table 13 ADF File in Modular Package in MySQL
DescriptionFile Name
For every parameter in the legacy toolkit user configuration file, there is an attribute in the ADF. It also has
an additional attribute TKIT_DIR which is analogous to the package directory in the legacy method of
packaging. The ADF is used to generate a modular package ASCII template file.
mysql.1
For the alert mail notification feature, an additional parameter called ALERT_MAIL_ID is introduced
in the ADF. ALERT_MAIL_ID sends an email message to the specified e-mail address when
packages fail. This e-mail is generated only when packages fail, and not when you halt the package.
To send this e-mail message to multiple recipients, a group e-mail ID must be created and specified
for this parameter. If you do not specify and email ID for this parameter, the script does not send
out this email.
Table 15 lists the files that are located in/etc/cmcluster/scripts/ecmt/mysql after
installation.
Table 14 Script Files
DescriptionFile Name
This script is called by the Master Control Script and acts as an interface between the Master Control
Script and the Toolkit interface script (toolkit.sh). It is responsible for calling the Toolkit Configuration
File Generator Script .
tkit_module.sh
This script is called by the Module Script when the package configuration is applied using
cmapplyconf to generate the toolkit user configuration file in the package directory (TKIT_DIR).
tkit_gen.sh
The MySQL database server must be installed on all nodes that run the MySQL Packages in the
HP Serviceguard Cluster. The node where the package runs is termed as primary node. The other
nodes that are ready to take up the service in case of failure are termed as standby nodes. The
MySQL Database Server application runs on the primary node servicing MySQL Database requests
from clients. If the package fails on the primary node, it fails over the standby node. This means
that all necessary configuration information on all nodes must be identical and the resources must
be available to all supporting nodes. The data must be stored on shared disks and these disks must
be accessible by the same pathnames on each node.
MySQL database server supports multiple DB instances running on the same node. This toolkit
helps to create multiple MySQL packages. Each package corresponds to a separate DB server
instance with its own database, toolkit files, and configuration.
MySQL Package Configuration Overview
The database server can be configured in two different ways:
Local Configuration
Local configuration is configured by putting the configuration files on a single node, and then
replicating the files to all other nodes in the cluster. If you decide to store the configuration files on
a local disk, you must replicate the configuration to local disks on all nodes configured to run the
package. If you change the configuration, you must copy the file to all nodes. To ensure that the
systems remain synchronized, HP recommends that you place all configuration and data files on
shared storage.
Shared Configuration
Shared configuration is configured by putting the configuration files in a shared filesystem. This is
the recommended configuration. Here, the configuration and database files are on shared disks,
visible to all nodes. The storage is shared, therefore, there is no additional work to ensure all nodes
have the same configuration at any point in time.
MySQL Package Configuration Overview 89