Overview of the GDSv2
Oracle Solaris Cluster supports both versions of GDS (GDS and
GDSv2).
This section contains information about the following:
-
The ORCL.gds and
ORCL.gds_proxy resource
types
-
RGM callback methods for the GDSv2 resource
types
-
The
method_command
Sequence
Resource Types
The GDSv2 uses
ORCL.gds and
ORCL.gds_proxy resource types.
A proxy resource type is typically used to reflect the state of a
resource from another cluster framework. The proxy resource type was
initially developed to proxy state information of the Oracle RAC
database running under the control of the Oracle Solaris Cluster
Ready Service, now known as Oracle Clusterware. However, a proxy
resource type is not limited to proxying state information from
another cluster framework and instead could reflect the state of any
application. In the examples that are provided, the demo resource of
type ORCL.gds_proxy reflects the state of the SMF
system log service.
RGM Callback Methods
The ORCL.gds and
ORCL.gds_proxy resource types include RGM
callback methods and associated
method_command
extension properties.
The ORCL.gds resource type includes the following
RGM callback methods and associated
method_command
extension properties:
|
|
Boot
|
Boot_command
|
Fini
|
Fini_command
|
Init
|
Init_command
|
Start
|
Start_command
|
Stop
|
Stop_command
|
Validate
|
Validate_command
|
Method_start
|
Probe_command
|
Method_stop
|
|
Method_check
|
|
Update
|
|
|
The ORCL.gds_proxy resource type includes the
following RGM callback methods and associated
method_command
extension properties:
|
|
Boot
|
Boot_command
|
Init
|
Init_command
|
Fini
|
Fini_command
|
Prenet_start
|
Prenet_start_command
|
Postnet_stop
|
Postnet_stop_command
|
Validate
|
Validate_command
|
|
The GDSv2 also includes the following:
-
Useful housekeeping KSH function scripts for
GDSv2 resource types.
-
Demo resources of type ORCL.gds and
ORCL.gds_proxy to showcase
functionality.
-
Enhanced GDSv2 probing algorithm to
minimize probe timeouts.
-
Enhanced Oracle Solaris Cluster Agent Builder GUI and
CLI commands to create new resources of type
ORCL.gds and
ORCL.gds_proxy, as well as new
resources from sub-classed
ORCL.gds or
ORCL.gds_proxy resource
types.
The method_command
Sequence
To see a complete list of all callback methods executed by the RGM,
see RGM Callback Methods. The RGM
callback method and subsequent GDSv2
method_command
sequences are listed in the following sections.
The ORCL.gds
method_command
Sequence
The table below lists the ORCL.gds
method_command
extension properties.
|
|
|
Resource creation
|
Validate
|
Validate_command
If set, the
Validate_command is executed on
all nodes within the resource group's node
list.
|
|
Init
|
Init_command
If set, the Init_command
is executed on all nodes identified by the
Init_nodes property.
|
Resource enable
|
Start
|
Start_command
Start_command is a
required property.
|
|
Monitor start
|
Probe_command
Monitor_start will only execute
Probe_command if it is set. If
Probe_command is not set but
PMF_managed=TRUE is set, then
Monitor_start will start an internal probe.
|
Resource disable
|
Monitor stop
|
Probe_command
Monitor_stop will only stop the probe if
Probe_command was set. If
Probe_command was not set but
PMF_managed=TRUE was set, then
Monitor_stop will stop the internal probe.
|
|
Stop
|
Stop_command
Stop_command is only
executed if it is set. If
Stop_command is not set but
PMF_managed=TRUE is set, then
Stop_signal is sent to the
application process tree if
Stop_command failed to stop the
application.
|
Resource delete
|
Fini
|
Fini_command
If set, Fini_command is
executed on all nodes within the resource group's
node list.
|
Resource unmonitor
|
Monitor stop
|
Probe_command
Monitor_stop will only stop the probe if
Probe_command was set. If
Probe_command was not set but
PMF_managed=TRUE was set, then
Monitor_stop will stop the internal probe.
|
Resource monitor
|
Monitor start
|
Probe_command
Monitor_start will only execute
Probe_command if it is set. If
Probe_command is not set but
PMF_managed=TRUE is set, then
Monitor_start will start an internal probe.
|
Property update for an enabled
resource
|
Validate
|
Validate_command
If set, the
Validate_command is executed on
all nodes within the resource group's node
list.
|
|
Update
|
On the node where the resource is online,
the RGM Update method will kill
the fault monitor process tree and then use PMF to
restart the fault monitor.
|
Property update for a disabled
resource
|
Validate
|
Validate_command
If set, the
Validate_command is executed on
all nodes within the resource group's node
list.
|
Upon reboot for an enabled and monitored
resource
|
Boot
|
Boot_command
If set, Boot_command is
executed on all nodes identified by the
Init_nodes property.
|
|
Start
|
Start_command
Start_command is a
required property.
|
|
Monitor Start
|
Probe_command
Monitor_start will only execute
Probe_command if it is set. If
Probe_command is not set but
PMF_managed=TRUE is set, then
Monitor_start will start an internal probe.
|
Upon reboot for a disabled resource
|
Boot
|
Boot_command
If set, Boot_command is
executed on all nodes identified by the
Init_nodes property.
|
|
The ORCL.gds_proxy
method_command
Sequence
The table below lists the ORCL.gds_proxy
method_command
extension properties.
|
|
|
Resource creation
|
Validate
|
Validate_command
If set, the
Validate_command is executed on
all nodes within the resource group's node
list.
|
|
Init
|
Init_command
If set, the Init_command
is executed on all nodes identified by the
Init_nodes property.
|
Resource enable
|
Prenet start
|
Prenet_start_command
Prenet_start_command is a
required property.
|
Resource disable
|
Postnet stop
|
Postnet_stop_command
If set,
Postnet_stop_command is
executed on the node where the resource is being
disabled. If
Postnet_stop_command is not
set, then the Stop_signal
property is sent to the proxy PMF tag.
|
Resource delete
|
Fini
|
Fini_command
If set, Fini_command is
executed on all nodes within the resource group's
node list.
|
Upon reboot for an enabled resource
|
Boot
|
Boot_command
If set, Boot_command is
executed on all nodes identified by the
Init_nodes property.
|
|
Prenet start
|
Prenet_start_command
Prenet_start_command is a
required property.
|
Upon reboot for a disabled resource
|
Boot
|
Boot_command
If set, Boot_command is
executed on all nodes identified by the
Init_nodes property.
|
|
The Resource Group
method_command
Sequence
The table below lists the resource group
method_command
extension properties.
|
|
|
Resource group offline with an enabled
resource
|
Postnet stop
|
Postnet_stop_command
If set,
Postnet_stop_command is
executed on the node where the resource is being
disabled. If
Postnet_stop_command is not
set, then the Stop_signal
property is sent to the proxy PMF tag.
|
Resource group online with previously
enabled resource
|
Prenet start
|
Prenet_start_command
Prenet_start_command is a
required property.
|
Resource group switch from unmanaged to
managed
|
Init
|
Init_command
If set, the Init_command
is executed on all nodes identified by the
Init_nodes property.
|
Resource group switch from managed to
unmanaged
|
Fini
|
Fini_command
If set, Fini_command is
executed on all nodes within the resource group's
node list.
|
|