Bug 738701 - [RFE] expose autopick=random flag in reserve workflow
Summary: [RFE] expose autopick=random flag in reserve workflow
Keywords:
Status: NEW
Alias: None
Product: Beaker
Classification: Community
Component: web UI
Version: 0.7
Hardware: All
OS: Linux
medium
medium vote
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact:
URL:
Whiteboard: UX
: 221228 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-15 15:02 UTC by Frank Ch. Eigler
Modified: 2018-11-09 23:06 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 221228
Environment:
Last Closed:


Attachments (Terms of Use)

Description Frank Ch. Eigler 2011-09-15 15:02:52 UTC
+++ This bug was initially created as a clone of Bug #221228 +++

Description of problem:
Sometimes the reservesys installation EWD-timeouts.  I found out it is best to
schedule the same installation/reservation multiple times as one of the machines
may succeed.  If you wait till it Aborts you will get the same incompatible
combination scheduled during the retr

[...]

Bill reported:
    also, you can randomize your machine choice by changing the following in your xml:  
    <autopick random="true"/>

but there is no web UI for this in the reserve_workflow.  It'd be nice to get it
exposed there too, not just job-cloning.

Comment 1 Dan Callaghan 2012-10-03 06:15:54 UTC
*** Bug 221228 has been marked as a duplicate of this bug. ***

Comment 2 Jan Kratochvil 2012-10-03 06:36:32 UTC
I do not understand what random="false" can ever be good for.

Comment 3 Dan Callaghan 2012-10-03 22:49:21 UTC
(In reply to comment #2)

Ordinarily Beaker orders candidate systems by some heuristics that are theoretically good for overall scheduling performance -- selecting private systems before ones from the public pool. Setting <autopick random="true" /> defeats that, so it is not enabled by default.

The scheduler's behaviour in this regard is slated to be improved as part of the upcoming "groups model" enhancements anyway.


Note You need to log in before you can comment on or make changes to this bug.