[HTCondor-users] Evaluation of GROUP_SORT_EXPR

["Sever, Krunoslav" <krunoslav.sever@xxxxxxx>]

Hi,

the GROUP_SORT_EXPR calculates the GroupSortKey which determines group order in the negotiation cycle.

The current values can be viewed using something like

# condor_userprio -con 'IsAccountingGroup && GroupSortKey' -af Name GroupSortKey

Right now a few selected attributes of (only) the group in question are available that determine the sort key at the start of the cycle, default being

ifThenElse(AccountingGroup=?="<none>",3.4e+38,ifThenElse(GroupQuota>0,GroupResourcesInUse/GroupQuota,3.3e+38))

I was wondering if it would be worthwhile to consider allowing additional attributes and possibly even attributes of other groups in that expression?

More specifically, we have a situation where it might make sense to force certain groups to always be considered after other groups and this would be a way to achieve that.

One way could be as follows:

* use GROUP_SORT_EXPR to calculate the base group attributes as it is done now
* use GROUP_SORT_EXPR.<GROUP> to post-process individual groups, allowing access to attributes of other groups here via <OTHERGROUP>.*

This would allow some logic of the kind

GROUP_SORT_EXPR.GRP1 = ifThenElse(GRP1.GroupSortKey<GRP2.GroupSortKey, GRP2.GroupSortKey+1.0, GRP1.GroupSortKey)

to make sure that GRP1 will be sorted after GRP2 at all times.

Does that make sense at all?

Best
  Kruno

-- 
------------------------------------------------------------------------
Krunoslav Sever            Deutsches Elektronen-Synchrotron (IT-Systems)
                        Ein Forschungszentrum der Helmholtz-Gemeinschaft
                                                            Notkestr. 85
phone:  +49-40-8998-1648                                   22607 Hamburg
e-mail: krunoslav.sever@xxxxxxx                                  Germany
------------------------------------------------------------------------