Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] time of day policy
- Date: Fri, 20 Jun 2025 18:05:04 +0200 (CEST)
- From: "Beyer, Christoph" <christoph.beyer@xxxxxxx>
- Subject: Re: [HTCondor-users] time of day policy
Hi,
I think anything request_.* triggers a condition:
In the examples below, assume Tag is the custom resource name.
so
request_tag = <expression>
causes
RequestTag = <expression>
to be added to the job ClassAd, and the Requirements expression will have
(TARGET.Tag >= RequestTag)
or
regexp(RequestTag, TARGET.TAG)
Anyway - I meant shutdowntime of course or remaining uptime :)
I am currently experimenting with something like this:
/* Job must start outside restricted hours (before 11:00 or after 14:00) */
( (CurrentHour < 11) || (CurrentHour >= 14) ) &&
/* If starting before 11:00, must finish before today's 11:00 */
( (CurrentHour < 11) ?
(CurrentHour + floor(request_runtime / 3600) < 11)
:
/* If starting after 14:00, must not wrap into any future 11:00â14:00 window */
(
/* Calculate total runtime in full days + remaining hours */
(floor((request_runtime / 3600) / 24) == 0) || /* If runtime < 24h, just check today */
(
/* For multi-day jobs, ensure no part of runtime overlaps 11:00â14:00 */
((CurrentHour + (request_runtime / 3600)) % 24 < 11) ||
((CurrentHour + (request_runtime / 3600)) % 24 >= 14)
)
)
)
)
Will try it line for line and see but would still be interested to know if the clocktime feature includes runtime aspects ...
best
christoph
--
Christoph Beyer
DESY Hamburg
IT-Department
Notkestr. 85
Building 02b, Room 009
22607 Hamburg
phone:+49-(0)40-8998-2317
mail: christoph.beyer@xxxxxxx
----- UrsprÃngliche Mail -----
Von: "Todd L Miller via HTCondor-users" <htcondor-users@xxxxxxxxxxx>
An: "HTCondor-Users Mail List" <htcondor-users@xxxxxxxxxxx>
CC: "Todd L Miller" <tlmiller@xxxxxxxxxxx>
Gesendet: Freitag, 20. Juni 2025 17:40:55
Betreff: Re: [HTCondor-users] time of day policy
> Does that automatically respect the request_runtime of the jobs because
> it may tinker with the uptime value of the host ?
I don't understand this question. AFAIK, "request_runtime" isn't
a thing -- at least, it doesn't appear to be in the manual. I'm also not
sure what the "uptime value" of the host is in the context -- the host's
uptime (time since boot) shouldn't change any as a result of running or
not-running jobs.
-- ToddM
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
Join us in June at Throughput Computing 25: https://osg-htc.org/htc25
The archives can be found at: https://www-auth.cs.wisc.edu/lists/htcondor-users/