If you plan to install the QCG-Computing service on a separate machine (for performance or security reasons) you must assure that:

• the machine is a submit host of the Torque Local Resource Manager, what further implies that:
  • the machine share account information with the whole cluster (e.g. using LDAP or NIS),
  • the torque-client and torque-devel packages are installed,
  • the contents of the <code>/var/spool/pbs/server_name</code> points to the machine where the Torque <code>pbs_server</code> is running.
  • the Smoa Computing host is added as <code>submit_host</code> in the Torque server configuration:

      > qmgr
      Max open servers: 4
      Qmgr:
      set server submit_hosts += qcg.your.domain
      set server submit_hosts += qcg
    

Note: You may need to add the QCG-Computing host in the <code>/etc/hosts.equiv</code> file.

• the machine mounts <code>/home</code> filesystem of the cluster. Alternatively you can mount any other file system that can be used by any user (e.g. the scratch filesystem).
• the <code>/var/spool/pbs/server_logs</code> directory is exported in read-only mode (e.g. using NFS or Lustre) from Torque server to this machine (this share must be mounted locally as <code>/var/spool/pbs/server_logs</code>). The Torque DRMAA library for scalability reason can be configured to use batch system logs to get notified about jobs state changes.
• the machine is administrative host of the Maui Scheduler, what further denotes that:
  • The maui-client package is installed.
  • On the QCG-Computing machine modify the <code>SERVERHOST</code> section of the <code>/var/spool/maui/maui.cfg</code> file. It must points to the machine where the maui daemon is running.
  • On the Maui server machine modify the <code>ADMINHOSTS</code> section of the <code>/var/spool/maui/maui.cfg</code> file and add the QCG-Computing host to the list of admin hosts.