Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Solaris Cluster Data Services Developer's Guide Oracle Solaris Cluster 4.0 |
1. Overview of Resource Management
3. Resource Management API Reference
Overview of Modifying a Resource Type
Setting Up the Contents of the Resource Type Registration File
Specifying the #$upgrade and #$upgrade_from Directives
Changing the RT_version in an RTR File
Determining Installation Requirements and Packaging
Before You Change the RTR File
Determining the Packaging Scheme to Use
Documentation to Provide for a Modified Resource Type
Information About What to Do Before Installing an Upgrade
Information About When to Upgrade Resources
Information About Changes to Resource Properties
6. Data Service Development Library
8. Sample DSDL Resource Type Implementation
9. Oracle Solaris Cluster Agent Builder
12. Cluster Reconfiguration Notification Protocol
A. Sample Data Service Code Listings
B. DSDL Sample Resource Type Code Listings
C. Requirements for Non-Cluster-Aware Applications
D. Document Type Definitions for the CRNP
Here is what the cluster administrator must do or what happens when he or she upgrades a resource type:
If the existing resource property attributes do not satisfy the validation conditions of the new version of the resource type, the cluster administrator must provide valid values.
The cluster administrator must provide valid values under the following conditions:
When the new version of the resource type does not have a default value and uses a property that is not declared in the earlier version.
When the existing resource uses a property whose value is undeclared or invalid in the new version. Declared properties that are undeclared in a new version of a resource type are deleted from the resource.
Any attempt to upgrade from an unsupported version of a resource type fails.
After an upgrade, resources inherit the resource property attributes for all properties from the new version of the resource type.
If you change the default value of a resource type in the RTR file, the new default value is inherited by existing resources. The new default value is inherited even if the property is declared tunable only AT_CREATION or WHEN_DISABLED. A property of the same type that the cluster administrator creates also inherits this default value. However, if the cluster administrator specifies a new default value for the property, the new default value overrides the default value that is specified in the RTR file.
Note - The cluster administrator can overcome this limitation by specifying values for the properties and thus overriding the defaults.