Oracle® Solaris Cluster Concepts Guide

Exit Print View

Updated: July 2014, E39575-01

Data Service Project Configuration

This section provides a conceptual description of configuring data services to launch processes on a specified Oracle Solaris OS UNIX project. This section also describes several failover scenarios and suggestions for using the management functionality provided by the Oracle Solaris Operating System. See the project(4) man page for more information.

Data services can be configured to launch under an Oracle Solaris project name when brought online using the RGM. The configuration associates a resource or resource group managed by the RGM with an Oracle Solaris project ID. The mapping from your resource or resource group to a project ID gives you the ability to use sophisticated controls that are available in the Oracle Solaris OS to manage workloads and consumption within your cluster.

Using the Oracle Solaris management functionality in an Oracle Solaris Cluster environment ensures that your most important applications are given priority when sharing a node with other applications. Applications might share a node if you have consolidated services or because applications have failed over. Use of the management functionality described here might improve availability of a critical application by preventing lower-priority applications from overconsuming system supplies such as CPU time.

Note - The Oracle Solaris documentation for this feature describes CPU time, processes, tasks and similar components as “resources”. Meanwhile, Oracle Solaris Cluster documentation uses the term “resources” to describe entities that are under the control of the RGM. The following section uses the term “resource” to refer to Oracle Solaris Cluster entities that are under the control of the RGM. The section uses the term “supplies” to refer to CPU time, processes, and tasks.

For detailed conceptual and procedural documentation about the management feature, refer to Planning for Network Deployment in Oracle Solaris 11.2 .

    When configuring resources and resource groups to use Oracle Solaris management functionality in a cluster, use the following high-level process:

  1. Configuring applications as part of the resource.

  2. Configuring resources as part of a resource group.

  3. Enabling resources in the resource group.

  4. Making the resource group managed.

  5. Creating an Oracle Solaris project for your resource group.

  6. Configuring standard properties to associate the resource group name with the project you created in step 5.

  7. Bringing the resource group online.

To configure the standard Resource_project_name or RG_project_name properties to associate the Oracle Solaris project ID with the resource or resource group, use the –p option with the clresource set and the clresourcegroup set command. Set the property values to the resource or to the resource group. See the r_properties(5) and rg_properties(5) man pages for descriptions of properties.

The specified project name must exist in the projects database (/etc/project) and the root user must be configured as a member of the named project. Refer to Introduction to Oracle Solaris Zones for conceptual information about the project name database. Refer to project (4) for a description of project file syntax.

When the RGM brings resources or resource groups online, it launches the related processes under the project name.

Note - Users can associate the resource or resource group with a project at any time. However, the new project name is not effective until the resource or resource group is taken offline and brought back online by using the RGM.

Launching resources and resource groups under the project name enables you to configure the following features to manage system supplies across your cluster.

  • Extended Accounting – Provides a flexible way to record consumption on a task or process basis. Extended accounting enables you to examine historical usage and make assessments of capacity requirements for future workloads.

  • Controls – Provide a mechanism for constraint on system supplies. Processes, tasks, and projects can be prevented from consuming large amounts of specified system supplies.

  • Fair Share Scheduling (FSS) – Provides the ability to control the allocation of available CPU time among workloads, based on their importance. Workload importance is expressed by the number of shares of CPU time that you assign to each workload. Refer to the following man pages for more information.

  • Pools – Provide the ability to use partitions for interactive applications according to the application's requirements. Pools can be used to partition a host that supports a number of different software applications. The use of pools results in a more predictable response for each application.