1. Overview of Resource Management
3. Resource Management API Reference
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
What Happens When a Cluster Administrator Upgrades
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. Solaris Cluster Agent Builder
12. Cluster Reconfiguration Notification Protocol
B. Sample Data Service Code Listings
C. DSDL Sample Resource Type Code Listings
E. Requirements for Non-Cluster Aware Applications
F. Document Type Definitions for the CRNP
Cluster administrators must be able to carry out the following tasks:
Install and register a new version of an existing resource type
Allow the registration of multiple versions of a given resource type
Upgrade an existing resource to a new version of the resource type without having to delete and re-create the resource
A resource type that you intend to upgrade is called an upgrade-aware resource type.
Elements of an existing resource type that you might change are as follows:
Attributes of resource type properties
The set of declared resource properties, including standard and extension properties
Attributes of resource properties, such as default, min, max, arraymin, arraymax, or tunability
The set of declared methods
The implementation of methods or monitors
Note - You do not necessarily have to modify a resource type when you modify application code.
You need to understand the requirements for providing the tools that will enable a cluster administrator to upgrade a resource type. This chapter tells you what you need to know to set up these tools.