 |
 |
Passing the ClassAds structures to the local batch interface would provide a standard syntax for the parameters. We would then need a library which could - Remove the 'site' based parameters (since these are already resolved as the job was sent to the CE) - Provide a standard expression tree which could be translated into the local batch system by the submission engine. This would be the job parameters only. As long as we agree on an objective that this first level parsing should be batch system independent, we can avoid a lot of complexity for the batch system interface. Jeff Templon took the same approach on the ERT by defining an intermediate interface between the batch specific and the batch independent parts. This allows one side to follow the close evolution of the grid standards while avoiding 'n' complex implementations for the different batch systems. I'd vote for ClassAds with this library as an implementation... I'd be happy to do the LSF backend rather than spend the time manually tuning job priorities... Tim Bell Mail: [log in to unmask]