Bug 659171

Summary: expose scheduler's URL in a job xml (for e.g. reservesys)
Product: [Retired] Beaker Reporter: Raymond Mancy <rmancy>
Component: schedulerAssignee: Bill Peck <bpeck>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 0.5CC: bpeck, dcallagh, ebaak, mcsontos, rmancy
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-09 05:45:20 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:
Bug Depends On: 661761    
Bug Blocks:    

Description Raymond Mancy 2010-12-02 03:04:32 UTC
I've made a small change on my dev for the reservesys task to task a param for the inventory server so it's not harcoded. Need to change the server code so it can automatically populate this param in the XML.

Comment 1 Marian Csontos 2010-12-02 09:12:24 UTC
IMO this looks more like a job property, not a task's param - i.e. "this job runs on such-and-such scheduler", and not "this task should know the scheduler is so-and-so" ?

BTW, is this assigned to test-harness (and thus me) correctly?

Comment 2 Raymond Mancy 2010-12-02 22:53:21 UTC
Well if I set it as a task param I know that it is easily accessible by the task (which is exactly what I need). Perhaps it was short sighted, but I've got no idea how to get it in any other way.
I guess the correct place to have it is as a Job level entry, but I have no idea to do this. 

I didn't mean to assign this to you actually. I think you have more important things to do.

Comment 3 Marian Csontos 2011-01-25 10:13:17 UTC
I suggest implementing this as a global param for the job element: see Bug 658455.

On harness side that would be a really simple change.

Comment 4 Dan Callaghan 2012-07-09 05:29:38 UTC
Could we just dupe this to bug 646773?

Comment 5 Raymond Mancy 2012-07-09 05:45:20 UTC
Yes.

*** This bug has been marked as a duplicate of bug 646773 ***