[Pgi-wg] Next teleconference: tomorrow, wednesday july 15th

[Laurence Field]

Hi Andrew,

The most important aspects of GLUE2 for this activity is the GLUE 
execution environment and GLUE application environment. It describes the 
hardware and software properties of the cluster respectively and the Job 
Description should mirror this information.

Currently, this information is propagated around the Grid infrastructure 
via a parallel mechanism.  Whether this needs to be part of BES or if 
there is an information service which must accompany BES is a matter for 
debate. Within the current EGEE/WLCG infrastructure there are no plans 
for the foreseeable future to move away from the current mechanism, the 
need to expose this information via BES is not a requirement for it to 
be deployed on the infrastructure.

One of the problems with getting the information from BES is that this 
is then a service specific mechanism and other services such as the SRM, 
etc. will have a different method. Information system interoperation is 
indeed problem which we must solve but we need to deal with things in 
manageable chunks. I would consider this problem to be a general Grid 
interoperability problem rather than something specific to BES so we 
should try not get too distracted from the good progress that has been 
made so far.  The definition of GLUE 2.0 has solved  more than half of 
the information system interoperability problem. As the information 
content is standardized, moving it around and translating from one data 
format to another is just a technical plumbing exercise. Having 
something standardized here would certainly help but it is probably out 
of scope for the BES discussion.

Anyway, my personal opinion on the information system standards is that 
a good one already exists,  X.500  :)

Laurence


Andrew Grimshaw wrote:
> Moreno,
> Once we figure out what we need I can start the process to get a new draft
> of BES out.
>
> Besides the state model - where we seem to have reached a consensus, and the
> "vector" operations, there is also the issue of moving towards GLUE2 as the
> attribute schema which has been discussed several times. We will need to be
> specific as to what part of GLUE2, and how to get the info from endpoints
> (we could keep the current mechanism). 
>
> Finally, there is JSDL. It would be good if we could synchronize the
> transition to GLUE2 with the JSDL group. I am cc'ing the JSDL group as they
> may be able to better answer the question of JSDL and GLUE2 congruence (if
> there are any such plans.)
>
> A
>
>   
>> -----Original Message-----
>> From: pgi-wg-bounces at ogf.org [mailto:pgi-wg-bounces at ogf.org] On Behalf Of
>> Moreno Marzolla
>> Sent: Tuesday, July 14, 2009 5:40 AM
>> To: pgi-wg at ogf.org
>> Subject: [Pgi-wg] Next teleconference: tomorrow, wednesday july 15th
>>
>> Dear all,
>>
>> the next PGI teleconference will be held tomorrow july 15th
>> at 16:00 CET (duration: 1 hour).
>>
>> Call-in details as follow:
>> via Skype call +9900827049931906 (free of charge) ordinary phone numbers
>> (local rates) with the 9931906 conference number:
>>
>> Austria 0820 401 15470
>> Belgium 0703 57 134
>> France 0826 109 071
>> Germany +49 (0) 180 500 9527
>> Switzerland 0848 560 397
>>
>> The agenda is similar to the last call (in particular, tomorrow I would
>> like that we spend a few minutes on a status update of the security
>> discussion)
>>
>> 1) State model
>>
>> 2) Status update on security
>>
>> 3) AOB
>>
>> Feel free to propose additional topics for discussion.
>>
>> Moreno.
>>
>> --
>> Moreno Marzolla
>> INFN Sezione di Padova,    via Marzolo 8,   35131 PADOVA,  Italy
>> EMail: moreno.marzolla at pd.infn.it         Phone: +39 049 8277103
>> WWW  : http://www.dsi.unive.it/~marzolla  Fax  : +39 049 8756233
>>
>> _______________________________________________
>> Pgi-wg mailing list
>> Pgi-wg at ogf.org
>> http://www.ogf.org/mailman/listinfo/pgi-wg
>>     
>
>
> _______________________________________________
> Pgi-wg mailing list
> Pgi-wg at ogf.org
> http://www.ogf.org/mailman/listinfo/pgi-wg
>