cluster:Maui/326p19/server

From Dgiref

Please open a NGI-DE ticket if you experience any Installation or Configuration problem.

Maui/326p19/server

Prepare

It is required to install the Torque server (version 2.1.6 or version 2.3.6) before the maui scheduler packages.

administrator's script: prepare.sh

```
 
```
```
#!/bin/bash
```
```
# prepare maui
```
```
#-> start routine
```

REPO_URL="http://dgiref.d-grid.de/svn/dgiref/PROD/cf3/repl/repos/external/"

wget -O /etc/yum.repos.d/sl-dgiref.repo ${REPO_URL}/sl-dgiref.repo

```
#<- end routine
```

Install

To install Maui, the following RPMs are needed :

maui
maui-server

Install rpms from dgiref binary repository.

administrator's script: install.sh

```
 
```
```
#!/bin/bash
```
```
# install maui server
```
```
#-> start routine
```
```
# Choose the OS architecture: 
```
```
OS_arch="x86_64"   # x86_64 for 64 bit
```
```
# OS_arch="i686"   # i686 for 32 bit
```

yum -y install maui-3.2.6p19-snap1171482917_1dgrid_sl4.${OS_arch} maui-server-3.2.6p19-snap1171482917_1dgrid_sl4.${OS_arch}

```
#<- end routine
```

Configure

By default, batch systems like OpenPBS or Torque have their own job scheduler. Normally, this is much more simple-minded than Maui; for example, in the case of OpenPBS and Torque, the default is a simple fifo scheduler. Therefore, before Maui can be used, the batch system must be told to use it.

With OpenPBS or Torque, this is accomplished setting the scheduling state of the server to False:

qmgr -c "set server scheduling = False"
qmgr -c "list server"
  ...
  server_state = Idle
  scheduling = False
  ...

The scheduling policies are defined in Maui’s configuration file : /var/spool/maui/maui.cfg

administrator's script: configure.sh

```
 
```
```
#!/bin/bash
```
```
# configure maui server
```
```
 
```

# Declare the variables section ------------

# Please insert your actual configuration

EDGINFO_UID=user id for edginfo on GLITE server

RGMA_UID=user id for rgma on GLITE server

# from here ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

```
EDGINFO_UID=101
```
```
RGMA_UID=102
```
```
HOST=`hostname -f`  
```

# till here ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

```
 
```
```
#-> start routine
```

# In some cases the alias host name command HOST=`hostname -a` should be run. But the previous should work.

sed -e "s/localhost/$HOST/" -i /var/spool/maui/maui.cfg

```
 
```
```
cat << EOF >> /var/spool/maui/maui.cfg
```

# The users edginfo and rgma query Maui from the glite-CE to provide data to the InfoSystem

```
ADMIN3            edginfo rgma 
```

# Set the delay to 1 minute before Maui tries to run a job again,

# in case it failed to run the first time.

```
# The default value is 1 hour. 
```
```
DEFERTIME       00:01:00 
```
```
# Necessary for MPI grid jobs 
```
```
ENABLEMULTIREQJOBS TRUE 
```
```
EOF 
```
```
 
```
```
# Create users for gLite 
```
```
useradd -u $EDGINFO_UID edginfo 
```
```
useradd -u $RGMA_UID rgma
```
```
 
```
```
#<- end routine
```

Proceed

Start service maui

administrator's script: proceed.sh

```
 
```
```
#!/bin/bash
```
```
# proceed
```
```
#-> start routine
```
```
## start maui
```
```
chkconfig maui on 
```
```
/etc/init.d/maui start
```
```
#<- end routine
```

cluster:Maui/326p19/server

Contents

Maui/326p19/server

Prepare

Install

Configure

Proceed

Views

Personal tools

general

guidelines

reference installation

Search

internal

Toolbox