A scalable resource group is used with scalable services. The shared address feature is the Sun Cluster networking facility that enables the multiple instances of a scalable service to appear as a single service. You must first create a failover resource group that contains the shared addresses on which the scalable resources depend. Next, create a scalable resource group, and add scalable resources to that group. The node list of a scalable resource group or of the shared address resource group must not contain more than one global-cluster non-voting node on the same node. Each instance of the scalable service must run on a different cluster node.
You can configure a scalable resource group to run in a global-cluster non-voting node as well. Do not configure a scalable resource to run in multiple global-cluster non-voting nodes on the same node.
Perform this procedure from any cluster node.
On a cluster member, become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.
Create the failover resource group that holds the shared addresses that the scalable resource is to use.
Create the scalable resource group.
# clresourcegroup create\-p Maximum_primaries=m\-p Desired_primaries=n\ -p RG_dependencies=depend-resource-group\ [-n node-zone-list] resource-group
Specifies the maximum number of active primaries for this resource group.
Specifies the number of active primaries on which the resource group should attempt to start.
Identifies the resource group that contains the shared address resource on which the resource group that is being created depends.
Specifies a comma-separated, ordered list of nodes in which this resource group is to be available. The format of each entry in the list is node:zone. In this format, node specifies the node name and zone specifies the name of a global-cluster non-voting node. To specify the global-cluster voting node, or to specify a node without global-cluster non-voting nodes, specify only node.
This list is optional. If you omit this list, the resource group is created on all nodes in the cluster.
The node list of the scalable resource can contain the same list or a subset of nodename:zonename pairs as the node list of the shared address resource
Specifies your choice of the name of the scalable resource group to add. This name must begin with an ASCII character.
Verify that the scalable resource group has been created.
# clresourcegroup show resource-group
This example shows the creation of the scalable resource group resource-group-1. This resource group is to be hosted in the global cluster of nodes phys-schost-1 and phys-schost-2. The scalable resource group depends on the failover resource group resource-group-2, which contains the shared address resources.
# clresourcegroup create\ -p Maximum_primaries=2\ -p Desired_primaries=2\ -p RG_dependencies=resource-group-2\ -n phys-schost-1, phys-schost-2\ resource-group-1 # clresourcegroup show resource-group-1 === Resource Groups and Resources === Resource Group: resource-group-1 RG_description: <NULL> RG_mode: Scalable RG_state: Unmanaged RG_project_name: default RG_affinities: <NULL> Auto_start_on_new_cluster: True Failback: False Nodelist: phys-schost-1 phys-schost-2 Maximum_primaries: 2 Desired_primaries: 2 RG_dependencies: resource-group2 Implicit_network_dependencies: True Global_resources_used: <All> Pingpong_interval: 3600 Pathprefix: <NULL> RG_System: False Suspend_automatic_recovery: False
After you have created a scalable resource group, you can add scalable application resources to the resource group. See How to Add a Scalable Application Resource to a Resource Group for details.
The clresourcegroup(1CL) man page.