Go to main content

Planning and Administering Data Services for Oracle® Solaris Cluster 4.4

Exit Print View

Updated: November 2019
 
 

Encapsulating an SMF Service Into a Scalable Proxy Resource Configuration

For information about scalable configuration, see How to Create a Scalable Resource Group.


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. Register the SMF proxy scalable resource type.
    # clresourcetype register -f \
    /opt/SUNWscsmf/etc/SUNW.Proxy_SMF_scalable SUNW.Proxy_SMF_scalable
  3. Create the SMF failover resource group that holds the shared address that the scalable resource group is to use. See How to Create a Failover Resource Group to create the failover resource group.
  4. Add the shared address resource to the failover resource group.

    See How to Add a Shared Address Resource to a Resource Group (CLI).

  5. Create the SMF proxy scalable resource group.
    # clresourcegroup create -S [-p Maximum_primaries=m] [-p Desired_primaries=n] \
    [-n node-zone-list] 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.

  6. Verify that the scalable resource group has been created.
    # clresourcegroup show resource-group
  7. Add an SMF proxy scalable resource to the scalable resource group you created in Step 5.
    # clresource create-g resource-group -t SUNW.Proxy_SMF_scalable \
    -p Resource_dependencies=network-resource[,network-resource...] \
    -p Scalable=True \
    -p Port_list=portnumber/protocol \
    -x Proxied_service_instances=/tmp/dns_svcs.txt
    –p Resource_dependencies=network-resource[,network-resource…]

    Specifies the name of the scalable network resource you created in Step 3 on which this resource depends.

    –g resource-group

    Specifies the name of the SMF proxy scalable resource group that you previously created.

    –p Scalable=True

    Specifies that this resource uses the network load balancing features of Oracle Solaris Cluster software. For more information, see How to Add a Scalable Application Resource to a Resource Group.

    The resource is created in the enabled state.

  8. Verify that the SMF proxy scalable application resource has been added and validated.
    # clresource show resource
  9. Bring the SMF proxy scalable resource group online.
    # clresourcegroup online -M resource-group

    Note -  If you use the clresource status command to view the state of the SMF proxy resource type, the status is displayed as online but not monitored. This is not an error message. The SMF proxy resource is enabled and running and this status message is displayed because there is no monitoring support provided for the resources of SMF proxy resource type.
Example 40  Registering an SMF Proxy Scalable Resource Type

The following example registers the SUNW.Proxy_SMF_scalable resource type.

# clresourcetype register SUNW.Proxy_SMF_scalable
# clresourcetype show SUNW.Proxy_SMF_scalable

Resource Type:           SUNW.Proxy_SMF_scalable
RT_description:          Resource type for proxying scalable SMF services
RT_version:              2.0
API_version:             7
RT_basedir:              /opt/SUNWscsmf/bin
Single_instance:         False
Proxy:                   False
Init_nodes:              All potential masters
Installed_nodes:         <All>
Failover:                True
Pkglist:                 <NULL>
RT_system:               False
Global _zone:            False
Example 41  Creating and Adding an SMF Proxy Scalable Application Resource to a Resource Group

This example shows the creation and addition of a scalable proxy resource type SUN.Proxy_SMF_scalalble to a resource group resource-group-1.

# 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
# clresource create -g resource-group-1 -t SUNW.Proxy_SMF_scalable \
-p resource_dependencies=net-res -p port_list=1080/tcp \
-x proxied_service_instances=/var/tmp/svslist.txt resource-1
# clresource show resource-1

=== Resources ===

Resource:                            resource-1
Type:                                SUNW.Proxy_SMF_scalable
Type_version:                        2.0
Group:                               resource-group-1
R_description:
Resource_project_name:               default
Enabled{phys-schost-1}:              True
Monitored{phys-schost-1}:            True

You can choose the resource_dependencies and port number to use.