| Summary: | [RFE] Grid QMF job identification incongruity in GetJobAd() | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Martin Kudlej <mkudlej> |
| Component: | condor-qmf | Assignee: | Pete MacKinnon <pmackinn> |
| Status: | CLOSED WONTFIX | QA Contact: | MRG Quality Engineering <mrgqe-bugs> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 1.3 | CC: | matt |
| Target Milestone: | 2.0 | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-02-03 16:59:34 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Martin Kudlej
2011-02-01 10:25:29 UTC
Note that GetJobAd is a method on the JobServer object associated with a Scheduler object, which is always a 1:1 association. Naming a schedd in the GetJobAd argument is superfluous - a JobServer only knows about a specified set of clusters.procs. I know, that if you want run GetJobAd(), you need know name of the scheduler. But why there have to be any difference in job identification? I think it's confusing now. If there should be any difference in calling functions with JobId, please add it to documentation somewhere(API specification). I think it will be fine that if job doesn't belong to scheduler, it will return False, None or raise exception as in situation when ClusterId doesn't belong to scheduler. Martin feel free to raise a doc bug if you like. |