Hi Manuel, On 15 May 2007 at 13:11, Manuel Prinz wrote: | Hi everyone, | | I've to administrate a small cluster and I'm intersted in your opinion | or experience with the resource managers/batch systems you use. | | ATM, there's Torque installed, and I'm not too happy with it, especially | with the documentation. I've found a thread on debian-science about | packaging SLURM [1] and had a look at it, and at a first glance it seems | that more people care about it then Torque. But that may be wrong. | | The cluster is new, so there would be no problem with switching to a | different resource manager. Our requirements are quite low, a default | FIFO scheduler will do. (The only thing really needed is support of | Prologue/Epiloque scripting, addressing single cores and two batch | queues.) | | I've the impression that SLURM will be maintained more actively and | during a longer time in the future. The better documentation probably | will ease up things when I run into trouble or the requirements change. | Torque's documentation is more like a tutorial without much explanation | of what's happening and I don't feel very comfortable with this. | | So, I'd be thankful if you would share you opinion with me! Thanks in | advance!
Following on a similar thread or two we had here, I have been sponsoring Gennaro Oliva who has been working on munge [ == authentication service used by slurm ] packages which we _almost_ got into Debian unstable. The ftpmaster noticed that another copyright line was missing for two files internal to munge. Gennaro has also packaged slurm as slurm-llnl [ Debian already has a slurm package ] but despite my prodding, has not released anything based on slurm 1.2.* as he is working on a configuration script -- and that's hard. I am trying to come to terms with slurm and lam myself at work, so I am doing some testing there too. Big summary: Yes, these should be forthcoming. Cheers, Dirk -- Hell, there are no rules here - we're trying to accomplish something. -- Thomas A. Edison -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]