alexander.papaspyrou at udo.edu
Fri Nov 23 09:41:31 CST 2007
2007/11/23, Philipp Wieder <philipp.wieder at udo.edu>:
> Ariel and I are currently meeting to progress with GSA and I had a quick
> look at the current OGSA-RSS document. The CandidateQualityProperties
> contain a number of attributes which are also of interest for us in a
> scheduling context, but for our needs there are a number of other things
> we would like to add. Is the current set of CandidateQualityProperties
> fixed and should we use the extension point to add our own stuff? Or do
> you plan to replace this sooner or later by a more generic QoS construct?
I would vote for splitting this out from RSS.
See, at least the timing constraints are something that is probably
needed by several different actors within the whole process: users
want to define start times, deadlines, and the like (probably using
JSDL), brokers need to know about the constraints for planning
(affecting GSA and RSS), and maybe LRMSs want the information for
being allowed to kill the job if it exceeds its runtime estimation
(think into the direction of BES/DRMAA).
Supposedly, this also goes for other properties described in the CQPs.
However, this is just my opinion and totally uncoordinated with the
So, what do you think, Donal?
Dipl.-Inform. Alexander Papaspyrou
Robotics Research Institute phone : +49(231)755-5058
Information Technology Section fax : +49(231)755-3251
Technische Universität Dortmund, Germany
More information about the gsa-rg