[Crunch2] c-d-slurm should avoid new --priority option
crunch-dispatch-slurm translates the container's priority into the sbatch
--priority option. According to the news, this option was added in 14.03.2, which is probably too new for us to require (it's not even included Ubuntu trusty, supported until 2019).
It's also not clear to me that we want it at all. The man page says, "Only Slurm operators and administrators can set the priority of a job." It's not clear to me that crunch-dispatch-slurm should need to count on having those privileges. Even if it happens to have them, I'm not sure it should use what is apparently such a blunt instrument.
9262: Stop setting sbatch --priority in crunch-dispatch-slurm.
There are a few reasons we want to back this out:
- `--priority` is a relatively new feature of SLURM, added in 14.03,
and it's not clear how many users are running that.
- Setting `--priority` requires extra privileges, per the sbatch man
page, and it's not clear crunch-dispatch-slurm should run with
- There are multiple ways to set the "priority" of a SLURM job.
There's also a niceness value. Which is correct to use is probably
ultimately going to depend on site rules or conventions. We need to
get more feedback on what people are doing before we implement
something. We might need configurations options along the lines of
"translate container priority into this option with this scaling
factor," or something like that.
Per discussion with Tom Clegg. Closes #9626.