The Maui Scheduler interfaces directly to a relational database using the Java DataBase Connectivity (JDBC) API. Currently only the MySQL database is supported through the mm.mysql driver. Other databases (Oracle, Postgres, ...) may be supported in the future.
The Maui Scheduler database provides:
Configure and setup MySQL as you would normally. Make sure to give your MySQL "root" user a good password!
For first-time installations of the Maui Scheduler, run the supplied
maui_create_db script after installation. You will need to
know the MySQL "root" user password. For upgrades, run the
Database Schema Documentation is here.
Certain tables in the database are automatically populated by the Maui Scheduler. For instance, the first time user steviek issues a command to the scheduler, his login account information is stored in the uusers and ugroups database tables. Each time steviek reconnects with changed information, (like a different UNIX group), this information is also recorded in the tables. User and group information is not purged from the database automatically. So if you remove users/groups from your system you must do so by hand from the database (although this shouldn't be necessary and may be undesireable from a bean-counting perspective).
The Maui Scheduler does not automatically store information for accounts, because accounts are not an underlying system feature and there is no way to pre-authenticate this. Thus, if you plan to use accounts for users, you need to populate account information yourself. The best way to think of accounts is as an alternate way to group users on your system (independent of UNIX groups), potentially for billing purposes. If you have no need of this functionality, just ignore it!
Job and reservation tables are automatically populated when a job or reservation finishes or is cancelled, recording the correct run times. The checkpoint table is automatically updated every so often when the scheduler checkpoints its data.
The database password for the Maui Scheduler user is stored in the
maui_db.pass alongside the
secret communication key on the Maui Scheduler server machine.
Keep this file safe too!
Remember to update the
maui_db.pass file if you change the
password for the Maui Scheduler user within MySQL.