[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] Perform condor_q, condor_status selections on Requirements
- Date: Tue, 11 Aug 2015 15:31:13 +0000
- From: "Fischer, Max (SCC)" <max.fischer@xxxxxxx>
- Subject: Re: [HTCondor-users] Perform condor_q, condor_status selections on Requirements
Hi Greg, Brian,
yes, we are looking for such a symmetric matching. condor_status -target is close, but weâd need it for condor_q instead.
Point is that we have lots of virtual machines, but they are all exact replicas of a few basic images. Jobs on the other hand come from a wide range. Weâd like to monitor the excess/lack of specific flavors given usersâ jobs.
Ideally without inspecting every job individually. ;)
> Am 31.07.2015 um 21:13 schrieb Greg Thain <gthain@xxxxxxxxxxx>:
> On 07/31/2015 09:49 AM, Fischer, Max (SCC) wrote:
>> Hi all,
>> Is there a way to apply condor_q/condor_status -constraint to ClassAd attributes requiring a TARGET? Can we perhaps actually supply a TARGET ClassAd for the evaluation? Is this possible with the python bindings perhaps?
> condor_status (but not condor_q) takes an optional -target <filename> option, which specifies the filename containing a job classed (in condor_q -l format) that can serve as a TARGET reference for -format and -af, but not for -constraint. Perhaps that helps?
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> The archives can be found at: