[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [geclipse-dev] GRIA questions
|
Hi Ariel, Mariusz, Ken, all,
Mariusz already answered almost all of Ariel's questions, but here are
some comments from me:
On Mon, 28 Apr 2008 16:01:53 +0200, Ariel Garcia <garcia@xxxxxxxxxx> wrote:
(...)
Another question:
i see some exceptions regarding jobs submitted with invalid parameters,
(...)
The question is, doesn't the GRIA client libs check for those things
beforesubmitting? I think it would make sense that this error is catched
by theclient libs.
(...)
These ones... how can they happen, if we query for the list of available
applications in the gria infoservice?
Those happened when we weren't able to query GRIA info service (because of
problems with GRIA JobService on Cyprus).
Jie submitted "hand-made" JSDL - and that's why we got those errors.
That bring us to the point of validating the JSDL for GRIA. We cannot
prevent user from editing JSDL - we have a general editor for those files,
and at the point of editing a JSDL file is only a JSDL file. It's in
submission wizard when user informs g-Eclipse it's GRIA job... Anyhow
validating those files here is also not always posible. There are 2 ways
to check if parameters from JSDL are ok with GRIA:
a) check it against application's metadata (taken from infoservice)
b) submit JSDL to GRIA and wait for response
The a) solution is not always possible (e.g. like yesterday, when we
couldn't access necessary information from JobService). Of course we can
always try a) and if that's not accessible just go for b), but it will
take some extra time of processing on user's machine. Imagine you have 2
GRIA projects (each for different version of GRIA, with different apps
installed). In submission wizard we're not able to say if job is submitted
to "proper" GRIA server, so each time you have to connect to chosen one,
download app's metadata and parse it... And still it may not guarantee
successful job submission (because of some server's related stuff). So I'm
not sure if that's of much use for users, if GRIA is doing validation
anyway - and gives us quite clear messages (if they should be logged on
server - that's sth different).
And one more thing about apps' metadata files. It seems that they aren't
always available on GRIA server - they weren't on the Cyprus one. I'm not
sure which GRIA version is installed there, but there's a question to Ken
- will those apps' metadata be supported in future GRIA versions (please
take a look at this bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=228196)? Is there some other
- maybe more reliable way - to get information how should JSDL for each
app look like?
Thanks,
Kasia
