Description of problem:
Currently when scheduling tests hosts selection is not random. Speaking with Bill the order of selection is Owner, Group, Other. I would like the ability to make this selection process truly random.
I will have to push this to 0.5.60 since I realize we need the following implemented:
# Order systems by owner, then Group, finally shared for everyone.
# FIXME Make this configurable, so that a user can specify their scheduling
# preference from the job.
# <recipe><scheduler method='random|fair|owner|group'/></recipe>
Right now we have fair implemented and thats all.
This change would allow jobs to be submitted with "random" and get a truly random selection.
I've reworked this a little..
<pool>owner</pool> <!-- add systems that you are the owner of -->
<pool>groups</pool> <!-- add systems that you have access via group membership -->
<pool>Public</pool> <!-- add systems that are shared to everyone -->
<!-- Pick me any system randomly from any of the pools -->
<!-- First try to find a system I'm the owner of, then a system that is a memeber of my groups -->
<!-- Pick me a system I own randomly -->
Could it be made to work with particular group as a parameter?
It would be useful for people who are members of multiple groups as I am, e.g. I do not want to run some tests on rare machines dedicated to storage testing. (IIUC I could use "Public" in this case, but that makes the pool smaller.)
Yes, But I feel that belongs in the <hostRequires/> section.
(In reply to comment #2)
> <!-- First try to find a system I'm the owner of, then a system that is a
> memeber of my groups -->
This one does not work. `autopick' element without `random' attribute fails with following message:
<Fault 1: "exceptions.AttributeError:'bool' object has no attribute 'lower'">
IMHO it should work: autopick is used for randomization as well as for picking pools and without the attribute I do not care about randomization and system should provide a reasonable default according to its settings/preference.
Shall I open a new BZ or will we name it a feature?
It does not work as advertised...
I have tried:
> <autopick random="1">
- still uses machines owned by a group
- it's not included in job-results and is not clone-able
Only the random part was implemented. The pools of systems was never done, I just wanted to make sure what ever we did implement made sense for that as well.
Bulk reassignment of issues as Bill has moved to another team.
This is on hold until we evaluate the possibility of switching to a more capable scheduling engine.