<< PreviousNext >>

Installing ClusterWare 5.3.0 on a Non-ClusterWare System

When installing ClusterWare 5.3.0 on a system that does not yet contain ClusterWare, you should perform the following steps:

  1. Clean the yum cache to a known state: yum clean all

  2. Update the RHEL5/CentOS5 base distribution: 

        yum --disablerepo=cw* update
    taking care to not update or install ClusterWare, then remove base distribution packages that conflict with ClusterWare:

        yum remove openmpi* mvapich*

  3. Download a custom Yum repo file:

    1. Login to MasterLink at http://www.penguincomputing.com/support/masterlink.

    2. Click on Download your ClusterWare 5 YUM repo file to download the new clusterware.repo file and place it in the /etc/yum.repos.d/ directory.

    3. Set the permissions:

          chmod 644 /etc/yum.repos.d/clusterware.repo

    4. The new clusterware.repo contains a baseurl entry that uses https by default. If your local site is configured to not support such encrypted accesses, then you must edit the repo file to instead use http.

  4. If your cluster includes Infiniband hardware, then you can ensure that all the necessary Infiniband-related rpms from the base distribution are installed: 

        yum groupinstall Infiniband
    where the Infiniband group is defined through the ClusterWare repo configuration file and refers to rpms that reside in the base distribution repository.

  5. Install ClusterWare: 

        yum groupinstall Scyld-ClusterWare
    If yum fails with a Transaction Check Error that complains that a base distribution rpm is newer than the Scyld ClusterWare rpm that is attempting to replace it, then you must manually install the downlevel Scyld ClusterWare rpm(s). For example, if the complaint is about the kernel rpms, then do: 
        cd /var/cache/yum/cw-core/packages
    rpm -Uvh kernel-headers-*
    rpm -i --oldpackage kernel-2* kernel-dev*
    and then repeat the groupinstall: 
        yum groupinstall Scyld-ClusterWare
    which should now complete! successfully.

  6. Configure the network for ClusterWare: run beonetconf to specify the cluster interface, the maximum number of compute nodes, and the beginning IP address of the first compute node. See the Installation Guide for more details.

  7. Examine /etc/grub.conf to confirm that the new CW5.3.0 kernel is the default, then reboot your master node.

  8. The first time Beowulf services start, e.g., when doing /sbin/service beowulf start or /etc/init.d/beowulf start, you will be prompted to accept a ClusterWare End User License Agreement (EULA). If you answer with an affirmative yes, then Beowulf services start and ClusterWare functionality is available, and you will not be prompted again regarding the EULA.

    However, if you do not answer with yes, then Beowulf services will not start, although the master node will continue to support all non-ClusterWare functionality available from the base distribution. Any subsequent attempt to start Beowulf services will again result in a prompt for you to accept the EULA.

    Note: if Beowulf is configured to automatically start when the master node boots (i.e., /sbin/chkconfig --list beowulf shows Beowulf on for levels 3, 4, and 5), then the first reboot after installing ClusterWare will fail to start Beowulf because /etc/init.d/beowulf is not executed interactively and no human sees the prompt for EULA acceptance. In this event, you may start Beowulf manually, e.g., using /sbin/service beowulf start, and respond to the EULA prompt.

<< PreviousHomeNext >>
Upgrading Earlier Release of ClusterWare to ClusterWare 5.3.0UpPost-Installation Configuration Issues