On a cluster member, become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.
Register the SMF proxy multi-master resource type.
# clresourcetype register -f\ /opt/SUNWscsmf/etc/SUNW.Proxy_SMF_multimaster SUNW.Proxy_SMF_multimaster |
Create the SMF multi-master resource group.
# clresourcegroup create\-p Maximum_primaries=m\-p Desired_primaries=n\ [-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.
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 configured on the global-cluster voting nodes.
Specifies your choice of the name of the scalable resource group to add. This name must begin with an ASCII character.
Verify that the SMF proxy multi-master resource group has been created.
# clresourcegroup show resource-group |
Add an SMF proxy multi-master resource to the resource group.
# clresource create -g resource-group -t SUNW.Proxy_SMF_multimaster\ [-p "extension-property[{node-specifier}]"=value, …] [-p standard-property=value, …] resource |
Specifies the name of a scalable service resource group that you previously created.
Specifies a comma-separated list of extension properties that you are setting for the resource. The extension properties that you can set depend on the resource type. To determine which extension properties to set, see the documentation for the resource type.
node-specifier is an optional qualifier to the -p and -x options. This qualifier indicates that the extension property or properties on only the specified node or nodes are to be set when the resource is created. The specified extension properties on other nodes in the cluster are not set. If you do not include node-specifier, the specified extension properties on all nodes in the cluster are set. You can specify a node name or a node identifier for node-specifier. Examples of the syntax of node-specifier include the following:
-p "myprop{phys-schost-1}" |
The braces ({}) indicate that you want to set the specified extension property on only node phys-schost-1. For most shells, the double quotation marks (“) are required.
You can also use the following syntax to set an extension property in two different global-cluster non-voting nodes on two different nodes:
-x "myprop{phys-schost-1:zoneA,phys-schost-2:zoneB}" |
Specifies a comma-separated list of standard properties that you are setting for the resource. The standard properties that you can set depend on the resource type. For scalable services, you typically set the Port_list, Load_balancing_weights, and Load_balancing_policy properties. To determine which standard properties to set, see the documentation for the resource type and Appendix B, Standard Properties.
Specifies your choice of the name of the resource to add.
The resource is created in the enabled state.
Verify that the SMF proxy multi-master application resource has been added and validated.
# clresource show resource |
Bring the multi-master resource group online.
# clresourcegroup online -M + |
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.
The following example registers the SUNW.Proxy_SMF_multimaster resource type.
# clresourcetype register SUNW.Proxy_SMF_multimaster # clresourcetype show SUNW.Proxy_SMF_multimaster Resource Type: SUNW.Proxy_SMF_multimaster RT_description: Resource type for proxying multimastered SMF services RT_version: 3.2 API_version: 6 RT_basedir: /opt/SUNWscsmf/bin Single_instance: False Proxy: False Init_nodes: All potential masters Installed_nodes: <All> Failover: True Pkglist: SUNWscsmf RT_system: False Global_zone: False |
This example shows the creation and addition of a multi-master proxy resource type SUN.Proxy_SMF_multimaster to a resource group resource-group-1.
# clresourcegroup create\ -p Maximum_primaries=2\ -p Desired_primaries=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: multimastered 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 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_multimaster -x proxied_service_instances=/var/tmp/svslist.txt resource-1 # clresource show resource-1 === Resources === Resource: resource-1 Type: SUNW.Proxy_SMF_multimaster Type_version: 3.2 Group: resource-group-1 R_description: Resource_project_name: default Enabled{phats1}: True Monitored{phats1}: True |