Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Data Services Planning and Administration Guide Oracle Solaris Cluster 4.1

Search Scope:

- This Document
- Entire Library

## Creating a Resource Group

A resource group contains a set of resources, all of which are brought online or offline together on a given node or set of nodes. You must create an empty resource group before you place resources into it.

The two resource group types are failover and scalable. A failover resource group can be online on only one node at any time, while a scalable resource group can be online on multiple nodes simultaneously.

The following procedures explain how to use the `clresourcegroup` command to create a resource group. See the `clresourcegroup`(1CL) man page for more information.

For conceptual information about resource groups, see Chapter 1, Planning for Oracle Solaris Cluster Data Services and Oracle Solaris Cluster Concepts Guide.

## How to Create a Failover Resource Group

A failover resource group contains the following types of resources:

- Network address resources, which are instances of the built-in resource types `LogicalHostname` and `SharedAddress`

- Failover resources, which are the data service application resources for a failover data service

The network address resources and their dependent data service resources move between cluster nodes when data services fail over or are switched over.

Note - Perform this procedure from any cluster node.

1. On a cluster member, assume the `root` role that provides `solaris.cluster.modify` RBAC authorization.
2. Create the failover resource group.

       # clresourcegroup create [-n nodelist] resource-group

   `-n` nodelist

     Specifies a comma-separated, ordered list of nodes that can master this resource group.

     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 failover resource group to add. This name must begin with an ASCII character.

3. Verify that the resource group has been created.

       # clresourcegroup show resource-group

Example 2-4 Creating a Failover Resource Group

This example shows the creation of the failover resource group `resource-group-1`. The cluster nodes `phys-schost-1` and `phys-schost-2` can master this resource group.

    # clresourcegroup create -n phys-schost1,phys-schost-2 resource-group-1
    # clresourcegroup show -v resource-group-1

    === Resource Groups and Resources ===

    Resource Group:                                 resource-group1
    RG_description:                                 <NULL>
    RG_mode:                                        Failover
    RG_state:                                       Unmanaged
    RG_project_name:                                default
    RG_affinities:                                  <NULL>
    RG_SLM_type:                                    manual
    Auto_start_on_new_cluster:                      True
    Failback:                                       False
    Nodelist:                                       phys-schost-1 phys-schost-2
    Maximum_primaries:                              1
    Desired_primaries:                              1
    RG_dependencies:                                <NULL>
    Implicit_network_dependencies:                  True
    Global_resources_used:                          <All>
    Pingpong_interval:                              3600
    Pathprefix:                                     <NULL>
    RG_System:                                      False
    Suspend_automatic_recovery:                     False

Next Steps

After you create a failover resource group, you can add application resources to this resource group. See Tools for Adding Resources to Resource Groups for the procedure.

See Also

The `clresourcegroup`(1CL) man page.

## How to Create a Scalable Resource Group

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.

1. On a cluster member assume the `root` role that provides `solaris.cluster.modify` RBAC authorization.
2. Create the failover resource group that holds the shared addresses that the scalable resource is to use.
3. 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.

4. 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.

Copyright © 2000, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |