Hi Andrea,
Actually, that's a feature of the upcoming 8.3.5 release (which was supposed to happen yesterday - but I assume got bumped to today?).
Since the release isn't out yet, I can't point to the documentation in the manual. Here's the original ticket:
https://htcondor-wiki.cs.wisc.edu/index.cgi/tktview?tn=2640
With this, you could add:
SUBMIT_REQUIREMENT_NAMES = block_cms
SUBMIT_REQUIREMENT_block_cms = x509UserProxyVOName =!= "cms"
SUBMIT_REQUIREMENT_block_cms_REASON = "This schedd is temporarily blocking submission from the CMS VO."
A different-but-related feature of 8.3.5 is CURB_MATCHMAKING. You can set:
CURB_MATCHMAKING = true
to temporarily block matchmaking for all jobs from the schedd. See: https://htcondor-wiki.cs.wisc.edu/index.cgi/tktview?tn=4905 . I suppose a natural extension we could add is to evaluate this with respect to the job and/or submitter. That would allow the schedd to queue submissions but not run them.
Brian
On Apr 21, 2015, at 8:28 AM, Andrea Sartirana <sartiran@xxxxxxxxxxxx> wrote:
Hi,
I've a newbie question.
I'd like to configure our condor Pool so to temporary refuse submission from a particular group (x509UserProxyVOName or Accounting group).
I seem not to be able to figure out how this can be done.
May someone give me some hints.
Thanks in Advance,
Andrea
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/