[gin-jobs] Worker Node Environment

[Laurence Field]

Hi Aleksandr,

Thanks for the feedback, I have appended this to the end of the document.

Here are some answer to your questions.

I completely agree that some variables will be MUST and some will be SHALL.

The meaning of "site" is something that the reference model group should 
define. For me this the administrative domain where the services are 
physically located. A site therefore represents the policies of an 
organization, a physical local and "wetware".

The definition of Global Job ID is something that certainly needs to be 
discussed.

In general I don't know of any "Grid Users", that do not submit jobs on 
behalf of a VO or where sites do not do add users depending on which VOs 
they support. If there are instances where a user does not belong to a 
VO, then they themselves become the VO.  They are a VO with only one 
member.

If jobs are not assigned any home-like environment then the variable 
will not be available, the same goes for all the other similar variables. 

Most of these files system present a POSIX like interface via some 
client. The client which is required can be figured out from the TYPE. 
The enumerated list will of course be open ended.

Laurence


Aleksandr Konstantinov wrote:
>   Dear Laurence,
>
>
>  Many statements in a draft are clearly non-applicable to some execution
> environements - some of them are not even grid-related. Hence it would be 
> nice to have some tags like MUST, SHALL, etc. assigned to every item and 
> action to be taken in case of absence of those items.
>  Purpose/usage of defined items would be also nice to have. That would help
> to understand what is expected that item to represent.
>
>  Here are some items with meaning not clear to me:
>
>  GRID_SITE_ID - what is "site"?
>  GRID_GLOBAL_JOB_ID - at Grid level job may have multiple IDs. Should it 
> be one known to initial client or last one known during job's submission 
> to batch system? Or list of them?
>  GRID_VO_ID - there may be job's (and users) unrelated to any VO. Should 
> there be some generic VO name? Or some ad-hoc name? Or VO per user?
>  GRID_APPLICATION_ROOT - what is "application software"?
>  HOME - what if jobs are not assigned any home-like environement?
>  GRID_CLUSTER_HOME - what if there is no "home" shared among cluster's nodes?
> Same goes for GRID_GLOBAL_HOME, GRID_CLUSTER_SCRATCH and GRID_GLOBAL_SCRATCH.
> Since those locations are shared, their access protocol is most probably 
> nor POSIX. What is format of associated value, URL?
>  GRID_HOME_TYPE - why enumerated? What about exotic file systems?
>
>  Why bootstraping scripts location includes VO name at all? How about software
> shared among VOs? Used by non-VO users? Is there any namespace planned to 
> distinguish between different softwares with same name?
>
>
> A.K.
>
>
>
>
>
>
> On Mon, 25 Jun 2007 14:09:36 +0200
> Laurence Field <Laurence.Field at cern.ch> wrote:
>
>   
>> Dear All,
>>
>> I have finally got round to writing up an initial draft recommendation 
>> for the Worker Node Environment based on what was discussed at OGF 20.
>>
>> http://forge.ogf.org/sf/wiki/do/viewPage/projects.gin/wiki/WorkerNodeEnvironment
>>
>> I hope that I have captured and interpreted everything accurately. 
>> Please send me any comments or suggestions, especially if they 
>> strengthen any of the semantics.
>>
>> I am not sure on how we should proceed but I guess that will depend on 
>> the feedback.
>>
>> Thanks
>>
>> Laurence
>>
>>
>> --
>>   gin-jobs mailing list
>>   gin-jobs at ogf.org
>>   http://www.ogf.org/mailman/listinfo/gin-jobs
>>     
>
>
>