3.9. Adding a Cluster Service to the Cluster

To add a cluster service to the cluster, follow the steps in this section. The starting point of the procedure is at the cluster-specific page that you navigate to from Choose a cluster to administer displayed on the cluster tab.
  1. At the detailed menu for the cluster (below the clusters menu), click Services. Clicking Services causes the display of services in the center of the page and causes the display of menu items for services configuration: Add a Service, Add a Virtual Machine Service, and Configure a Service.
  2. To configure any service other than a virtual machine service, Click Add a Service. Clicking Add a Service causes the Add a Service page to be displayed.
  3. On the Add a Service page, at the Service name text box, type the name of the service.

    Note

    Use a descriptive name that clearly distinguishes the service from other services in the cluster.
  4. Below the Service name text box, enter the following parameters for this service.
    • Automatically start this service — When the checkbox is checked, the service is started automatically when a cluster is started and running. If the checkbox is not checked, the service must be started manually any time the cluster comes up from the stopped state.
    • Enable NFS lock workarounds — Setting this option will release NFS locks on a file system in a soft attempt to unmount a file system, which may be necessary if your filesystem is exported via NFS and occasionally fails to unmount (either during shutdown or service relocation). You can also enable NFS daemon and lock workarounds for individual file system resources, which will result in a hard attempt to unmount a file system, as described in the table of file system resource parameters, Table C.3, “File System”, and the table of GFS resource parameters, Table C.4, “GFS”.
    • Run exclusive — If enabled, this service (resource group) can only be relocated to run on another node exclusively; that is, to run on a node that has no other services running on it. If no nodes are available for a service to run exclusively, the service is not restarted after a failure. Additionally, other services do not automatically relocate to a node running this service as Run exclusive. You can override this option by manual start or relocate operations.
    • Failover Domain — List of cluster members to try in the event that a service fails. For information on configuring a failover domain with Conga, refer to Section 3.7, “Configuring a Failover Domain”.
    • Recovery policy Provides the following options:
      Disable — Disables the resource group if any component fails.
      Relocate — Tries to restart service in another node; that is, it does not try to restart in the current node.
      Restart — Tries to restart failed parts of this service locally (in the current node) before trying to relocate (default) to service to another node.
      Restart-Disable — (Red Hat Enterprise Linux release 5.6 and later) The service will be restarted in place if it fails. However, if restarting the service fails the service will be disabled instead of being moved to another host in the cluster.
    • In addition, you can specify the Maximum number of restart failures before relocating and the Length of time in seconds after which to forget a restart.
  5. Add a resource to the service; click Add a resource to this service. Clicking Add a resource to this service causes the display of two drop-down boxes: Add a new local resource and Use an existing global resource. Adding a new local resource adds a resource that is available only to this service. The process of adding a local resource is the same as adding a global resource described in Section 3.8, “Adding Cluster Resources”. Adding a global resource adds a resource that has been previously added as a global resource (refer to Section 3.8, “Adding Cluster Resources”).
  6. At the drop-down box of either Add a new local resource or Use an existing global resource, select the resource to add and configure it according to the options presented. (The options are the same as described in Section 3.8, “Adding Cluster Resources”.)

    Note

    If you are adding a Samba-service resource, connect a Samba-service resource directly to the service, not to a resource within a service.
  7. If you want to add resources to that resource, click Add a child. Clicking Add a child causes the display of additional options to local and global resources. You can continue adding children resources to the resource to suit your requirements. To view children resources, click the triangle icon to the left of Show Children.
  8. When you have completed adding resources to the service, and have completed adding children resources to resources, click Submit. Clicking Submit causes a progress page to be displayed followed by a page displaying the added service (and other services).

Note

To verify the existence of the IP service resource used in a cluster service, you must use the /sbin/ip addr list command on a cluster node. The following output shows the /sbin/ip addr list command executed on a node running a cluster service:
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1356 qdisc pfifo_fast qlen 1000
    link/ether 00:05:5d:9a:d8:91 brd ff:ff:ff:ff:ff:ff
    inet 10.11.4.31/22 brd 10.11.7.255 scope global eth0
    inet6 fe80::205:5dff:fe9a:d891/64 scope link
    inet 10.11.4.240/22 scope global secondary eth0
       valid_lft forever preferred_lft forever

Note

To configure a virtual machine service, after clicking Services you can click Add a Virtual Machine Service. Enter the virtual machine resource parameters. For a description of the virtual machine parameters, refer to Table C.23, “Virtual Machine”. When you have completed adding the virtual machine resource parameters, click Create Virtual Machine Service.