Print

Print


Hi Thomas,

Thomas Hartmann wrote:
> Hi Jeff,
>
> I started sketched our experiences with jdl vs. SGE on a twiki page in
> AtlasComputing
>
> https://twiki.cern.ch/twiki/bin/view/AtlasComputing/JobRequirementsSGE
>
> btw: since the page got automatically behind an ACL wall: is there a
> wiki, that is usable without CERN/LHC VO affiliations in case site
> admins without affiliations need access?
>
>   
the LCG twiki at CERN is publicly readable, e.g.
  https://twiki.cern.ch/twiki/bin/view/LCG/WMTEGEnvironmentVariables

so perhaps it's easier to move stuff to the LCG twiki?

If need be I can set up a wiki/twiki at Nikhef.

HTH,

JJK / Jan Just Keijser
Nikhef
Amsterdam


> On 27.02.2014 09:22, Jeff Templon wrote:
>   
>> Yo,
>>
>>    Dennis van Dok's results for torque / maui are here:
>>
>>               http://wiki.nikhef.nl/grid/Passing_job_requirements_through_the_WMS
>>
>> AFAICT there is a degree of arbitrariness in which (and how) requirements are translated from the JDL to the batch system.  My opinion is that some small team should sit down and decide what the desired behavior is, and then work on implementing this behavior on each of the batch systems.  It would be really great if this same behavior is reproduced when passing requirements to an ARC CE or a GRAM 5 CE.
>>
>> The coordination sounds like a job for EGI, however I think the input to this coordination has to come from a discussion between sites and the users; sites should drive the discussion, as the sites are the parties that understand the use cases from multiple user communities.  Since the WLCG multicore TF is already working on related issues, we can probably find at least a subset of the right group of people there. Thomas is one of them!
>>
>> 			JT
>>  
>> On Feb 26, 2014, at 19:18 , Thomas Hartmann <[log in to unmask]> wrote:
>>
>>     
>>> Hi Goncalo and Maarten,
>>>
>>> after some more testing (and debugging of my script...) we were able to
>>> get CERequirements getting piped to SGE, e.g.
>>>
>>> CERequirements = "other.GlueHostMainMemoryVirtualSize > 2000";
>>> or other.GlueCEPolicyMaxWallClockTime > 30
>>>
>>> So far, we tested successfully the CPUTime, WallTime, Mem and VMem
>>> parameters passing from the jdl to the finally submitted SGE wrapper/job.
>>>
>>> Do you know, if there are further experiences for SGE and other batch
>>> systems how the implementation/support is for the various parameters?
>>>
>>> Cheers and many thanks for your help,
>>>  Thomas
>>>
>>>