Download

Release Date: 2007-08-08

nmi-2.2.8.tar.gz

MD5 checksum: 1e9060cb5b141e1ed228d6d5fe27dda3

Metronome-2.2.8-0.noarch.rpm

MD5 checksum: 71a59e60fd90fefe05e0aef96c9658f1

Release Notes

To support the web status pages’ ability to retain user preferences across multiple submit nodes, the web page database user must now be able to write to the ‘sessions’ table. The schema file, which now also describes the ‘sessions’ table, has been renamed from schema.sql to schema.mysql; please see it for details. We regret that sites with only one submit node can not at present readily disable this feature.

New Features

• The NMI_CONF enviroment variable is now respected.
• Added support for platform types, so that users who already have a platform naming scheme can retain it. See the PLATFORM_TYPE configuration variable, and the platform_type submit file variable.
• You can now advertise ‘nmi_condor_release_dir’ for machines which don’t have Condor (in particular, ‘chirp’) in their default PATH. This allows parallel jobs to invoke nmi_[get|put]attr on these platforms.

• If the configuration variable use_condor_job_leases is true, Metronome now sets a two-hour Condor job lease for all platform_jobs; this means if a submit host goes down or is disconnected from an execute host for less than two hours, running jobs will no longer be interrupted and have to restart. Note that this will not function with Condor version earlier than 6.9.3.

• The web status pages can now retain user preferences across multiple submit nodes in a Metronome pool.
• The web status pages now allow users to set their local timezone.
• Searching for a run in the web status pages based on runid or gid in the new top-right search box will now automatically jump to the task view for that run.
• The web status pages now display “condor submission failure” instead of “-1001” for that error code.

• The user may now suppress the pop-up window used to display standard output and error.

Bugs Fixed

• Metronome by default now correctly looks for nmi.conf under the Metronome install path specified at install time.
• Metronome no longer mangles submit files containing ‘queue’ when trying to insert the GID.
• Return to respecting the advertised attributed ‘nmi_gnutar’.
• nmi_condor_q now respects the PATH_NMI configuration variable.
• E-mail notification of run completion works again.
• The monitor job (which sends updates the Metronome DB) no longer keeps a persistent DB connection open; it also now retries after any failed DB updates. This should increase the maximum number of jobs in the system for a given database connection limit.

• The monitor now properly drains the event queue when it detects job completion. This should eliminate inconsistencies between the database and the on-disk state of the job.

Known Bugs

• nmi_condor_q fails to properly display jobs migrated to other Metronome sites

• View all Metronome bugs, as of the current release.

Requirements

• Metronome Submit/Archive Host
  • Condor >= 6.8.0 or Condor >= 6.9.0
  • Perl >= 5.005 (including DBI and DBD::mysql modules)
  • Apache >= 2.0

• PHP >= 4.2.3 (i.e, with Session & MySQL support)

• Metronome DB Host

• MySQL 4.1.20

• Condor Central Manager Host

• Condor >= 6.8.0 or Condor >= 6.9.0

• Build/Test Execution Hosts
  • Condor >= 6.8.0 or Condor >= 6.9.0

• Perl >= 5.005

Special Feature Requirements

• For Cross-Facility Job Migration: Condor >= 6.8.0
• For Parallel jobs: Condor >= 6.9.0 on central manager, submit and execute hosts.

• If use_condor_job_leases is enabled in nmi.conf: Condor >= 6.9.4