Bug 738701

Summary:	[RFE] expose autopick=random flag in reserve workflow
Product:	[Retired] Beaker	Reporter:	Frank Ch. Eigler <fche>
Component:	web UI	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	0.7	CC:	bpeck, dkl, fche, jan.kratochvil, mastyk, mcsontos, stl, tools-bugs
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	UX
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	221228	Environment:
Last Closed:	2020-06-02 11:50:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.

Comment 6 Martin Styk 2020-06-02 11:50:19 UTC

Hello,

thank you for opening issue in Beaker project.
This issue was marked with component "web ui".
As we are not planning to address any further issues in current UI, due to technical stack and not being able to work with Python 3 codebase, I'm closing this issue as WONTFIX.
New UI will be reimplemented within new versions of Beaker.

If you have any questions feel free to reach out to me.

Best regards,
Martin <martin.styk>