All VOs expressed interest for an extension of the CE interface to be able to Keep N jobs queued at all times until a given date or a given condition arises eg no work to be done in case there is nothing to do the rate of submissions doesnt go to infinite ID: 243301
Download Presentation The PPT/PDF document "Commonalities in pilot frameworks" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Commonalities in pilot frameworks
All VOs expressed interest for an extension of the CE interface to be able to:
Keep N jobs queued at all times until a given
date or a given condition arises (e.g. no work to be done)
in case there is nothing to do the rate of submissions doesn’t go to infinite...
All jobs of the “
stram
” share the same
jdl
(i.e. the same requirements, I/O specification, etc...)
CREAM d
evelopers
considered this feasible
This was approvedSlide2
Commonalities in pilot frameworks
Currently the pilot framework security relies on the fact that the pilot wrapper calls
glexec
to execute the user payload
This requires reviews of all and each of the VO pilot
frameworks
This concerns also how credentials are managed
It was proposed to find commonalities in the frameworks to factor out this part and enforce
glexec
calling, making unnecessary the review
During the discussion it emerged that this part is buried deep in the pilot and is very difficult to factorize it without impacting the efficiency. Furthermore that part would become as critical as
glexec
itself but definitely more complex so it was considered potentially counterproductive.
This has to be further investigated before decisions are taken