On Tue, 22 Feb 2011, Dave Love wrote:
...
Perhaps Mark Dixon will chime in with his scripts for processing the
schedule file to show the reservations in effect.
...
For those who don't know:
I've written a user command that prints what the resource reservation
scheduler is thinking. It looks a lot like qstat, except that all the
times are in the future.
It has two main aims:
1) Give users have a greater understanding of when their job may execute.
2) Allow admins and developers to identify times when the scheduler
clearly isn't working, submit a bug report, and hopefully get it fixed.
I've already noticed a lot of instances of (2), which I really should
submit to Dave's issuezilla.
Files:
There are two Perl programs - "qsched" (user callable) and
"process-scheduler-log" (a daemon) - and there'll be a file giving
instructions on how to integrate it into GE. That's it.
What needs to be done:
I've got approval to send this upstream under an open source license, but
I'm now wondering how to go about it in terms of which license and any
notices that need to go with it or into each file. I'm a tech, not a
lawyer, so obviously I'm imagining this is more complicated than it
actually is ;)
Does anyone have advice on how to do this? This'll be the first time I've
submitted code.
I guess the main points that are important to me are:
* It will remain copyright of University of Leeds.
* I'd like it to make it into the source repository if possible, so that
people can find it.
* I want the license to be compatible with the rest of the stuff in the
source repository. A lot of people say SISSL is a bit odd. Is there
another license in common use in the source tree?
Cheers,
Mark
--
-----------------------------------------------------------------
Mark Dixon Email : [email protected]
HPC/Grid Systems Support Tel (int): 35429
Information Systems Services Tel (ext): +44(0)113 343 5429
University of Leeds, LS2 9JT, UK
-----------------------------------------------------------------
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
