[ogsa-rss-wg] [GSA-RG] CandidateQualityProperties

[Alexander Papaspyrou]

Donal, Philipp, all,

2007/11/23, Donal K. Fellows <donal.k.fellows at manchester.ac.uk>:
> Alexander Papaspyrou wrote:
> > 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).
> >
> I also suspected that the bits I'd thought of weren't enough for more
> advanced cases, so I left as an extensibility point. (In general,
> candidates that are not related to execution planning would use totally
> different types of CQPs, of course. Data, for example, has many kinds of
> non-functional quality parameters.)
>
> If we spin out, I'd hope that whoever we spin out to would consider them
> to be a submission of things that are important. :-)

At least the timing issues are something that has been around in GSA
for quite a while. Probably, this would be at least the right place to
discuss and specify; as such, GSA could be some sort of "hub" for
things like that.

Maybe we could get to a kind of microspec handling the timing stuff
out of GSA, so it can be useful (and unified) for JSDL and RSS as
well. If this approach works, we could then extend it to other things
in the scheduling context that should be handled in a more holistic
way than within a single WG.

Regards,
Alexander
-- 
Dipl.-Inform. Alexander Papaspyrou
http://ds.e-technik.uni-dortmund.de/~alexp

  Robotics Research Institute                   phone : +49(231)755-5058
  Information Technology Section                fax   : +49(231)755-3251
  Technische Universität Dortmund, Germany