Re: [HTCondor-users] Accounting group queries

[John M Knoeller <johnkn@xxxxxxxxxxx>]

The accounting_group is the submit keyword, you need to use the Job attribute name which is AccountingGroup

 

like this

 

SUBMIT_REQUIREMENT_accountinggroup = AccountingGroup isnt undefined

SUBMIT_REQUIREMENT_accountinggroup_REASON = âuse of accounting_group is not permittedâ

 

or

 

SUBMIT_REQUIREMENT_accountinggroup = stringListMember(AccountingGroup, âgroup1, group2â)

SUBMIT_REQUIREMENT_accountinggroup_REASON = âaccounting_group must be one of:  group1, group2â

 

-tj

 

 

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> On Behalf Of Vikrant Aggarwal
Sent: Tuesday, July 30, 2019 7:02 AM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: Re: [HTCondor-users] Accounting group queries

 

Thanks for your reply. 

 

- Both the conditions doesn't allow me to submit the jobs with or without accounting group, it's expected in case when accountinggroup defined but not when it's undefined. 

 

SUBMIT_REQUIREMENT_NAMES = accountinggroup
SUBMIT_REQUIREMENT_accountinggroup = accounting_group isnt undefined

 

OR 

 

SUBMIT_REQUIREMENT_NAMES = accountinggroup
SUBMIT_REQUIREMENT_accountinggroup = !isundefined(accounting_group)

 

Also, can't we use the functions like to allow only certain accounting groups in submit file. 

 

SUBMIT_REQUIREMENT_NAMES = accountinggroup
#SUBMIT_REQUIREMENT_accountinggroup = accounting_group isnt undefined
SUBMIT_REQUIREMENT_accountinggroup = stringListIMember(accounting_group, "group1,group2"))

 

I am getting this error while submitting job, 

 

$ condor_submit sleep.sub                                                                                                                                                              
Submitting job(s)............................
ERROR: Failed to commit job submission into the queue.
ERROR: Submit requirement accountinggroup evaluated to non-boolean.

 

- it seems like that AssignAccountingGroup is not present in list of use features. 

 

$ condor_config_val use feature
use FEATURE accepts
  ContinuousCronHook
  GPUs
  OneShotCronHook
  PartitionableSlot
  PeriodicCronHook
  REMOTE_CONFIG
  REMOTE_RUNTIME_CONFIG
  ScheddCronContinuous
  ScheddCronOneShot
  ScheddCronPeriodic
  StartdCronContinuous
  StartdCronOneShot
  StartdCronPeriodic
  TESTINGMODE_POLICY_VALUES
  UWCS_DESKTOP_POLICY_VALUES
  VMWARE

 

 

Version of condor we are using:

 

$ condor_version
$CondorVersion: 8.5.8 Dec 13 2016 BuildID: 390781 $
$CondorPlatform: x86_64_RedHat6 $

Thanks & Regards,

Vikrant Aggarwal

 

 

On Tue, Jul 30, 2019 at 1:32 AM John M Knoeller <johnkn@xxxxxxxxxxx> wrote:

You can use a the SUBMIT_REQUIREMENT configuration to refuse jobs that have an accounting group,

or to verify that the accounting group is approved for that user.   We have a configuration template

for the second case.

 

use FEATURE : AssignAccountingGroup(<mapfile>)

 

where <mapfile> is the pathname to a file that declares the allowed accounting groups for each user.

 

-tj

 

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> On Behalf Of Vikrant Aggarwal
Sent: Monday, July 29, 2019 8:54 AM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: [HTCondor-users] Accounting group queries

 

Hello Experts,

I have some questions related to accounting groups in HTCondor. I read the official documentations also gone through some PPT.

No accounting groups are configured in our pool atm.

- Submitted one job without specifying accountingroup in submit file and another job using accountingroup "vikrant" in submit file. It created another entry with highest priority (lowest effective priority) that means user can cheat on priority by using different accounting group in their submit file which doesn't look good.

$ condor_userprio  | grep -i vaggarwal
vikrant.vaggarwal@xxxxxxxx            502.92   1000.00      1         0.20      <now>
vaggarwal@xxxxxxxx                   2542.40   1000.00      3       224.23      <now>

- Submitted job using "vikrant" accounting group with another user, it created another user again with lowest priority.

$ condor_userprio  | grep -i vikrant
vikrant.psingh@xxxxxxxx               500.00   1000.00      0         0.00    0+00:00
vikrant.vaggarwal@xxxxxxxx            504.56   1000.00      1         0.32      <now>

Checking the negotiator logs helped me to confirm that it's treating all as users only but still it's breach of trust. I don't think following statement applies in this case:

"Multiple users can all submit jobs into the same accounting group, and all jobs with the same accounting group will be treated with the same priority. Jobs that do specify an accounting group have all accounting and priority based on the specified accounting group. "

- On another hand, we want to give some users the freedom to use accounting group in submit file.

Questions:

- How can we limit the use of accounting group in submit file?
- I want some users to keep using the accounting groups, is adding list of allowed accounting group in GROUP_NAMES on master node should be sufficient to impose limit on the name of accounting groups which teams can use? if not then which approach we should follow? I don't want to set any limit on accounting groups atm.
- In future, if we tried to set the limit on accounting group and also have users without accounting groups; how negotiator decide on priority? Will it compare the effective priority of user using accountgroup with user without accounting group irrespective of accountinggroup quota.

Above use case is mainly for billing purpose and for understanding the working of accounting groups. 

Regards,
Vikrant 

_______________________________________________
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/