JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for LCG-ROLLOUT Archives


LCG-ROLLOUT Archives

LCG-ROLLOUT Archives


LCG-ROLLOUT@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

LCG-ROLLOUT Home

LCG-ROLLOUT Home

LCG-ROLLOUT  2005

LCG-ROLLOUT 2005

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Forward requirements to local batch system (fwd)

From:

pierre girard <[log in to unmask]>

Reply-To:

LHC Computer Grid - Rollout <[log in to unmask]>

Date:

Mon, 26 Sep 2005 14:35:28 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (66 lines)

Charles Loomis a écrit :

>> 2) Build a classad parser which does the best it can with the expression
>> it gets; that parser might be either in the WMS or in the CE.
>>
>> 2a) As 2, but insist that users restrict their requirement expressions
>> to things the parser can deal with.
>>
>> 3) Add new things in the JDL which match more directly with the kind of
>> thing you get in batch systems, e.g.:
>>
>> CPULimit = 3600;
>> MEMlimit = 511;
>> DiskLimit = 500;
>> Priority = 3;
>>
>> 3) is simpler on the batch system side, but you still have to adapt it
>> to specific systems, you still have to make it match the glue schema (or
>> vice versa), and you lose a lot of the potential richness of the classad
>> expressions.
>
>
> I would instead opt for a hybrid approach of 2) and 3).  Allow people 
> to define parameters like in 3) and have whatever processes the final 
> JDL combine those with any explicit requirements to arrive at the full 
> expression.  Only those limits given separately would be passed to the 
> local batch system.  This makes it easy to parse, loses none of the 
> functionality of the classad, and could be implemented in a finite 
> amount of time.  It is also closer to the spirit of the GGF job 
> description.


I would even opt for a XML implementation approach... It seems to me 
that the problem is basically to rewrite an expression (the JDL source) 
in another one (the LRMS command to be performed). The XML technology 
provides us with a very convenient and a very open way to do this. 
Moreover, there would be no need to implement (yet another) parser and  
we could possibly use an existing XML transformer (i.e. XSL Transformer) 
to finally transform the XML data into the expected LRMS-specific command.

How could it work ?
the RB could provide the CE with the jdl/classad data expressed as an 
XML document, and the CE could provide something like a XSL stylesheet 
to rewrite the XML data into a local LRMS command expression to be applied.

What would be the implementation effort ?
1- At the RB level, to express the classad/jdl (or whatever you want) in 
a XML format.
2- At the CE level, to provide an XSL stylesheet depending on the kinf 
of LRMS, which would transform the XML data into a LRMS command.

I don't know the expressivness of the famous classad (is there somewhere 
a classad specification document ?). Then I don't know whether a classad 
expression could or not be expressed as an XML tree...  ???

Pierre


-- 
______________________
Pierre GIRARD
Grid Computing Team Member
IN2P3/CNRS Computing Centre - Lyon (FRANCE)
http://cc.in2p3.fr
Tel. +33 4.78.93.08.80 | Fax. +33 4.72.69.41.70 | e-mail: [log in to unmask]

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
November 2023
June 2023
May 2023
April 2023
March 2023
February 2023
September 2022
June 2022
May 2022
April 2022
February 2022
December 2021
November 2021
October 2021
September 2021
July 2021
June 2021
May 2021
February 2021
January 2021
November 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
February 2018
January 2018
November 2017
October 2017
September 2017
July 2017
June 2017
May 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager