Next Previous Contents

1. Overview

The Maui Scheduler Molokini Edition is written primarily in the Java programming language. Maui has been developed from the ground up to be modular and extensible.

The primary features of the Maui Scheduler are:

1.1 Why Maui Scheduler?

So with other serial and parallel job schedulers out there, why should you use the Maui Scheduler Molokini Edition? We believe that the Maui Scheduler is the best solution in terms of price, features, and freedom.

The Maui Scheduler is "Free Software" (also termed Open Source software) licensed under the GNU Library General Public License. You can download the scheduler, install and run, and modify it as you see fit as long as you follow the liberal terms of the license.

We believe that the Maui Scheduler matches or exceeds the technical features of other parallel batch schedulers and resource managers. And if you know Java or Python, you should be able to write your own component plug-ins following the examples we've included.

1.2 Requirements

The Maui Scheduler is primarily written in the Java programming language. Thus, at the very least, you will need a Java virtual machine. This code has been tested and verified running on Linux and FreeBSD systems using the Java Development Kit (JDK)

1.3 Maui Scheduler Clients and Server

The main scheduling component is the Maui Server, which listens to a socket for client requests. For more information on the XML-based socket protocol, see the Maui Client Protocol documentation. See also the command line client documentation.

1.4 Socket Encryption and Authentication

Maui uses the Java Cryptix library for encrypting and authenticating communication between clients and server.

See the security section for more information.

1.5 Maui configuration

Except for tuning the database, the Maui Scheduler has two configuration files: and Use only if you want to override specific values of the file on a particular node, (which is primarily useful for heterogeneous clusters). NOTE: file is currently only read by the Node Daemon, but this may change in the future.

The file is a list of hierarchically-named properties for various components of the scheduling system. Each property is explained in the comments of that file. Make sure to propagate this file across all nodes in your cluster after making changes to it.

1.6 Logfiles

Scheduler logging is default written to the maui.out file in the /var/log/maui directory. The Node Daemon default logs to the wiki.out file in the /var/log/maui directory on its machine. These settings are configurable through properties in the file.

From a quick inspection of these files, you will see that most lines in the logfile have a class name and line number tags to allow you to go check the source code (if you so desire!)

Next Previous Contents