Resource Type Properties in the Sample RTR File

Language:

The sample RTR file begins with comments followed by resource type properties that define the HA-DNS configuration, as shown in the following listing. The example assumes that previous versions of the resource type exist, so #$upgrade directives are included. See Specifying the #$upgrade and #$upgrade_from Directives for more information.

Note - Property names for resource groups, resources, and resource types are not case sensitive. You can use any combination of uppercase and lowercase letters when you specify property names.

#
# Copyright (c) 1998, 2011, Oracle and/or its affiliates.
# All rights reserved.
#
# Registration information for Domain Name Service (DNS)
#

#pragma ident   “@(#)ORCL.sample   1.3   00/05/24”

Resource_type = “sample”;
Vendor_id = ORCL;
RT_description = “Domain Name Service on Oracle Solaris Cluster”;

RT_version =”3”;
API_version = 2;
Failover = TRUE;

RT_basedir=/opt/ORCLsample/bin;
Pkglist = ORCLsample;

Start         =   dns_svc_start;
Stop          =   dns_svc_stop;

Validate      =   dns_validate;
Update        =   dns_update;

Monitor_start =   dns_monitor_start;
Monitor_stop  =   dns_monitor_stop;
Monitor_check =   dns_monitor_check;

#$upgrade
#$upgrade_from "1" when_disabled
#$upgrade_from "2" anytime

Tip - You must declare the Resource_type property as the first entry in the RTR file. Otherwise, registration of the resource type fails.

The following information describes these properties:

You can specify the resource type name by the Resource_type property alone (sample) or by using the vendor-id as a prefix, followed by a period (.), followed by the resource type property (ORCL.sample).
If you specify vendor-id, use the stock exchange symbol of the company that is defining the resource type. The resource type name must be unique in the cluster.
The RT_version property identifies the version of the sample data service as specified by the vendor.
The API_version property identifies the Oracle Solaris Cluster version. For example, API_version = 11 indicates that the data service can be registered on any version of Oracle Solaris Cluster starting with 3.3, assuming that the application is compatible with that version of Oracle Solaris Cluster software. However, API_version = 11 also indicates that the data service cannot be registered on any version of Oracle Solaris Cluster that was released before 3.3. This property is described in more detail in the rt_properties(5) man page.
Failover = TRUE indicates that the data service cannot run in a resource group that can be online on multiple nodes at the same time.
RT_basedir points to /opt/ORCLsample/bin as the directory path to complete relative paths, such as callback method paths.
Start, Stop, and Validate provide the paths to the respective callback method programs that are run by the RGM. These paths are relative to the directory that is specified by RT_basedir.
Pkglist identifies ORCLsample as the package that contains the sample data service installation.

Resource type properties that are not specified in this RTR file, such as Single_instance, Init_nodes, and Installed_nodes, are set to their default values. Resource Type Properties contains a complete list of the resource type properties, including their default values.

The cluster administrator cannot change the values for resource type properties in the RTR file.