Friday April 28, 2006

SLAMD 2.0.0-alpha1 is now available

• SLAMD now uses an embedded database (using the Berkeley DB Java Edition) for storing all configuration and job information, so it no longer needs and external configuration directory for this purpose. This makes it much simpler to set up and manage a SLAMD server instance.
  
  
• SLAMD now provides a new job groups feature, which makes it possible to define a set of jobs that form a common workload and schedule them as a single entity. I have previously discussed job groups, but a lot of additional work has gone into it since then.
  
  
• The SLAMD server and clients have been updated so that they are now simpler to use. Where possible, the commands will attempt to automatically determine the location of the Java installation, and the command line client and resource monitor client have been updated so that the process of configuring them is now the same on Windows as it is on UNIX-based systems.
  
  
• Lots of bugs have been fixed, and lots of minor improvements and tweaks have been added to generally improve the overall user experience.
  
  
• The SLAMD source code base has been moved from a CVS repository into a Subversion repository, and therefore the project on java.net has been moved from https://SLAMD.dev.java.net/ to https://SLAMD2.dev.java.net. Instructions for checking out the source are available at http://www.SLAMD.com/subversion.shtml.
  
  
• The source code build process is now based on Ant rather than shell scripts. Although this is not a tremendous benefit for UNIX-based systems, it does make the code much easier to build on Windows. Further, there is now a single build that works on both Windows and UNIX systems, as opposed to a .zip build for Windows and a .tar.gz. build for UNIX.