Sun/Oracle Grid Engine 6.2 installation on Windows

Sun Grid Engine 6.2 Update 2 introduced the support for Windows Operating systems to run as worker nodes. Sun or Oracle Grid Engine as it’s being relabeled now is a distributed resource manager primarily used in HPC environment, but there’s more widespread use now with all the new features introduced as part of Update 5.

Here I’m going to detail a quick how-to of getting Grid Engine installed and running on Windows hosts. This is more applicable for Windows XP and Windows Server 2003, some of additional prerequisites required on the Windows hosts are now standard in Windows Server 2008 and Windows 7.

Prerequisites

Installation of SFU

Additional but not required

  • Install the bootstrap installer from Interop. Follow the directions here. http://www.interopsystems.com/tools/pkg_install.htm
  • If your system doesn’t have access to the Internet download the packages from ftp://ftp.interopsystems.com/pkgs/3.5/ to your local machine
  • For adding new packages, set PKG_PATH to the packages directory on your local machine.
  • Mostly it can be used for adding Bash, because SFU comes with default ksh and csh.
  • The binaries are installed in /usr/local/bin

Post Installation of SFU / GE installation prep work

  • The instructions here can be followed http://wikis.sun.com/display/GridEngine/Microsoft+Services+for+UNIX#MicrosoftServicesforUNIX-PostSFUInstallationTasks , but the instructions provided below will also be useful.
  • Open the Control Panel -> Administrative Tools -> Services and check that Telnet and Remote Shell Service is disabled. We will need to run telnet and RSH from Interix.
  • Uncomment the lines containing telnet and shell from /etc/inetd.conf through one of the Interix shells.
  • Restart inetd from /etc/init.d/inet start/stop
  • Check the Windows Firewall, if its off there’s nothing to do, if its off and group enabled or if enabled do the following:
    • Add Exceptions for TCP port 23 and 514 for telnet and remote shell access required for GE.
    • Also add an exception for the Grid Engine Execution daemon port, in this case 6444.
    • Do a nmap to check that ports 23 and 514 are accessible.
  • User name mapping is an important step. This instructions may vary if there’s a domain controller.
  • Map the user names from the passwd file we used earlier and Windows users
    • Refer http://wikis.sun.com/display/GridEngine/User+Management+for+Sun+Grid+Engine+on+Windows+Hosts for a detailed understanding of User management on Windows for Grid Engine.
    • Start -> All Programs -> Windows Services for UNIX -> Service for UNIX Administration -> User Name Mapping
    • Depending on your configuration you may have choose NIS or Password and Group Files. Either of those options are fine.
    • Click on the Maps tab, check Simple Maps and choose the appropriate Windows domain name.
    • Under Advanced Maps click on Show User Maps. Click on List Windows Users and List UNIX Users
    • Now just map the Windows user to the appropriate UNIX user name.
    • Make sure the following mapping is present (Windows User) Administrator -> (UNIX User) root
    • Map any other required users.
  • Check the users home directories and map them accordingly and create a profile for users if needed.
    • Control Panel -> Administrative Tools -> Computer Management -> Users -> Properties -> Profile

Pre Grid Engine Installation

Following on Windows Host

  • Create a directory for Grid Engine installs, typically /opt/gridengine
  • Export the following environment variables, add it to /etc/profile.lcl for system wide settings.
    export SGE_ROOT=/opt/gridengine
    export SGE_QMASTER_PORT=6445
    export SGE_EXECD_PORT=6444
  • If you are going to be running multiple instances of the execution daemon, then don’t set these environment wide, rather set it for each instance, as each instance needs to use a different port.
  • Add the Master node and the current node in /etc/hosts

Following on Master Node

  • Run sgepasswd on the Master node and set the passwords for the Windows users. This is used by G! E for shell logins.
    • When you do "sgepasswd user", it sets the password for user on the default domain.
    • Use "sgepasswd -D domain user" to set the password for a user of a specific domain.
  • Make sure the Windows host is added as an administrative host.
    • Run "qconf -sh" to check if the Windows host is already an administrative node
    • Run "qconf -ah hostname" to add the Windows host.
  • Type "qconf -mconf" and set the execd_params to enable_windomacc=true.
  • Add the Windows Admin name
    • qconf -am Administrator
  • Generate certificates for the Windows users and also the certificates and keys used for encryption needs to be copied over to the Windows machine

NFS Setup


Grid Engine Installation

, , , , ,

3 Responses to Sun/Oracle Grid Engine 6.2 installation on Windows

    Error thrown

    Call to undefined function ereg()