How to Create a Scalable Resource Group

Language:

A scalable resource group is used with scalable services. The shared address feature is the Oracle Solaris 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. Each instance of the scalable service must run on a different cluster node.

Note - Perform this procedure from any cluster node.

On a cluster member assume the root 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 -S [-p Maximum_primaries=m] [-p Desired_primaries=n] \
[-n nodelist] resource-group
```
–S

Specifies that the resource group is to be multi-mastered. If the –p Maximum_primaries and –p Desired_primaries options are omitted, both properties are set to the number of nodes in the resource group's node list.

–p Maximum_primaries=m

Specifies the maximum number of active primaries for this resource group.

–p Desired_primaries=n

Specifies the number of active primaries on which the resource group should attempt to start.

–n nodelist

Specifies a comma-separated, ordered list of nodes in which this resource group is to be available.

This list is optional. If you omit this list, the resource group is created on all nodes in the cluster.

resource-group

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
```

Example 2-5 Creating a Scalable 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 -S \
-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

Next Steps

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.

See also

The clresourcegroup(1CL) man page.