Project

General

Profile

Feature #5204

Support HTCondor-CE attributes

Added by Anthony Tiradani over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
Factory
Target version:
Start date:
01/15/2014
Due date:
% Done:

0%

Estimated time:
Stakeholders:
Duration:

Description

From Jeff Dost:

"We've been working with Brian to get glideins running on Nebraska HTCondor-CEs. Traditionally to specify special queues for GRAM sites, we would add things like maxWallTime, maxMemory, xcount, etc into the globus rsl.

If I understand Brian correctly, for a HTCondor-CE, now the correct place to put these types of settings are directly in the submit file as condor classad attributes.

I am wondering if this is supported yet and what the correct syntax is in the factory xml config file to properly get these values mapped into the entry submit file."

From Brian Bockelman:

"For OSG, this is high priority. Without it, we can't effectively do more than one entry point per HTCondor-CE."


Related issues

Has duplicate GlideinWMS - Feature #3537: We need to handle optional attributes at submit timeClosed02/26/2013

History

#1 Updated by Parag Mhashilkar over 5 years ago

  • Status changed from New to Resolved
  • Target version set to v3_2_3

Reviewed the code and merged it back from master to branch_v3_2

#2 Updated by Parag Mhashilkar over 5 years ago

  • Status changed from Resolved to Assigned
  • Target version changed from v3_2_3 to v3_2_4

Re opening the ticket. We need to work on an acceptable solution to specify HTCondor CE RSL.

#3 Updated by Igor Sfiligoi over 5 years ago

Also, we need to make sure that GF operators can upgrade from an existing v3_2_X in place.

#4 Updated by Igor Sfiligoi over 5 years ago

My proposal is to keep the overloading of the rsl attribute, but change the syntax to better match the RSL syntax.

BTW: While having full RSL language support would be nice, we probably can settle for a subset.

#5 Updated by Anthony Tiradani over 5 years ago

The accepted proposal is to slightly extend the <submit/> stanza for the entries. Example:

<entry ... >
<config>
<max_jobs>
<default_per_frontend glideins="50" held="5" idle="10"/>
<per_entry glideins="50" held="5" idle="10"/>
<per_frontends>
</per_frontends>
</max_jobs>
<release max_per_cycle="10" sleep="0.2"/>
<remove max_per_cycle="5" sleep="0.2"/>
<restrictions require_glidein_glexec_use="False" require_voms_proxy="False"/>
<submit cluster_size="10" max_per_cycle="100" sleep="0.2" slots_layout="fixed">
<submit_attrs>
<submit_attr name="RequestMemory" value="2000"/>
<submit_attr name="RequestCpus" value="1"/>
</submit_attrs>
<submit/>
</config>

...

</entry>

This has been coded and tested in branch v3/5204

#6 Updated by Anthony Tiradani over 5 years ago

  • Status changed from Assigned to Feedback

#7 Updated by Parag Mhashilkar over 5 years ago

  • Status changed from Feedback to Closed

Merged it to branch_v3_2

#8 Updated by Parag Mhashilkar almost 3 years ago

  • Has duplicate Feature #3537: We need to handle optional attributes at submit time added


Also available in: Atom PDF