2.9. Adding a Cluster Service to the Cluster

2.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 and Configure a Service.

  2. 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. Below the Service name text box is an checkbox labeled Automatically start this service. The checkbox is checked by default. 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.


    Use a descriptive name that clearly distinguishes the service from other services in the cluster.

  4. 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 2.8, “Adding Cluster Resources”. Adding a global resource adds a resource that has been previously added as a global resource (refer to Section 2.8, “Adding Cluster Resources”).

  5. 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 2.8, “Adding Cluster Resources”.)


    If you are adding a Samba-service resource, connect a Samba-service resource directly to the service, not to a resource within a service.

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

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


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 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 brd scope global eth0
    inet6 fe80::205:5dff:fe9a:d891/64 scope link
    inet scope global secondary eth0
       valid_lft forever preferred_lft forever

Note: This documentation is provided {and copyrighted} by Red Hat®, Inc. and is released via the Open Publication License. The copyright holder has added the further requirement that Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder. The CentOS project redistributes these original works (in their unmodified form) as a reference for CentOS-4 because CentOS-4 is built from publicly available, open source SRPMS. The documentation is unmodified to be compliant with upstream distribution policy. Neither CentOS-4 nor the CentOS Project are in any way affiliated with or sponsored by Red Hat®, Inc.