- ur-wg - lists.ogf.org

Agendas for next UR phone meeting today 15.06.2012 at 15:00 CEST and for Sunday's session at OGF35
by Andrea Cristofori 15 Jun '12

15 Jun '12

Dear all, here are the agendas for today phone conference and for our OGF session on Sunday Today's agenda: - Comments on the naming in GLUE 2.0 - Comments on the updated Draft attached to thie email - Should LocalUserId and LocalGroupId be moved in each block (e.g.: a user with a GlobalUserId could request computing resurces from a site and be assigned to a local user that is different from the user to which is assigned if for examples he/she requests storage resources in another site)? - Discuss the Attribute Origins Matrix (the table that shows the correspondences between the different definitions) - Should we included GLUE 2.0 (is it OK?) - A column for each definition? - Any topics that needs to be added to Sunday's agenda? - AOB Sunday's agenda: - Close the still open use cases and requirements - Discussion on the common fields - Further discuss the Attribute Origins Matrix - AOB Cheers, Andrea

1 1

how to publish services information
by Andrea Cristofori 15 Jun '12

15 Jun '12

Dear all, In reference to the discussion during our last phone meeting I found that GLUE seems not to inforce any standar name. But I also found a rather document (from 2009. You can find it attached to this email) that describe the name usage in WLCG. In particular, concerning the storage: * ImplementationName MUST be published. The format is defined by the implementations, but the names MUST NOT clash. In particular, for WLCG storage services the names to be used are: CASTOR, DPM, StoRM, dCache, BeStMan, xrootd. * ImplementationVersion MUST be published. The format is defined by the implementations. For OS names there are others directives here (I don not think we need it but while I was looking around for info I found it): https://wiki.egi.eu/wiki/Operations/HOWTO05 For site names: https://wiki.egi.eu/wiki/Operations/HOWTO05 Furthermore my understanding is that, at least in EMI, the decision is just to set the EMI release version. Based on that it should be then possible to identify the version of the specific middleware. Cheers, Andrea

4 4

Next UR phone meeting
by Andrea Cristofori 11 Jun '12

11 Jun '12

Dear all, Here you can enter the pool for next UR phone conference. http://www.doodle.com/yrrbr5v532s95izw#table Please cast you preference. Cheers, Andrea -- Andrea Cristofori INFN-CNAF Viale Berti Pichat 6/2 40127 Bologna Italy Tel. : +39-051-6092920 Skype: andrea-cnaf

1 1

Meeting in Delft Sunday 17th June
by john.gordon＠stfc.ac.uk 11 Jun '12

11 Jun '12

Can I just confirm that we will be quorate in Delft before I book my tickets. Thanks, John -- Scanned by iCritical.

5 7

Next phone meeting 29.05.2012 at 15:00 CET
by Andrea Cristofori 31 May '12

31 May '12

Dear all, Today no one was able to join the phone meeting. Next week some of us will be in New York and can not attend so I suggest we meet again in two weeks, the 29th of May. Jon will not be able to join because he is travelling. If other people can not make it I suggest to further postpone the phone meeting of 1 or 2 days but not later than the 1st of June. This way we will also have time for another phone meeting before next OGF. In the meanwhile I ask you to have a look to the document that I sent yesterday and give some comment and suggestion. In the next days we will anyway provide updates but the feedback is very important because in this way we know if we are moving in the right direction. Cheers. Andrea

4 6

Actions for next phone meeting 15.05.2012 at 15:00 CET
by Andrea Cristofori 15 May '12

15 May '12

Dear all, next phone meeting is posponed to the 15th of May because several people will be busy the 8th of May. The action list for next phone meeting is the following: - JAK check the use case for aggregation over different sites. - JKN and AC continue the work on the document. Cheers, Andrea

2 2

Phone meeting 24.04.2012 at 15:00 CET
by Andrea Cristofori 24 Apr '12

24 Apr '12

Dear all, Just a reminder for today phone meeting at 15:00 CET. I would also like to add two things: - 2 slots for UR session (90 minutes in total) have been requested ( I have also asked to avoid clashes with Standards-Data and Standards-Security) - attached to this email you can find the beginning of the document that will became the UR reccomendation. Basically, for the moment, it contains the old template with a revised "Table of Contents" Cheers, Andrea

1 0

Agenda for today's phone meeting 10.04.2012 at 15:00 CET
by Andrea Cristofori 12 Apr '12

12 Apr '12

Dear all, following is the agenda for today's phone meeting: - If John agrees, he could give a short report from Munich. - Jon comment on the StAR comment. - Discussion on the wiki pages starting from the use cases. Cheers, Andrea P.S.: the charter has been updated with the information discussed during last OGF in Oxford.

3 2

Regular meeting postponed for a week
by Jon Kerr Nilsen 03 Apr '12

03 Apr '12

Hi all, Since I'm out with a cold (since Munich) and it's so close to easter I suggest we postpone this Today's meeting to next Tuesday. Hope it's ok for all and sorry about the short notice. cheers, Jon

2 1

Fwd: Re: Fwd: EMI StAR – Definition of a Storage Accounting Record - ready for public comments
by john alan kennedy 26 Mar '12

26 Mar '12

Hi all, I asked Jean Yves Nief who's very active in the iRODS scene and works at IN2P3 where they have a large iRODS based data store to comment on the StAR doc. Here's his feedback. cheers johnk -------- Original Message -------- Subject: Re: Fwd: [UR-WG] EMI StAR – Definition of a Storage Accounting Record - ready for public comments Date: Tue, 20 Mar 2012 18:03:16 +0100 From: Jean-Yves Nief <nief(a)cc.in2p3.fr> To: john alan kennedy <jkennedy(a)rzg.mpg.de> dear John, I finally had time to take a look at your document. I do not have much comments at this point as I don't know the exact context of the discussion. In 5.18 (ResourceCapacityUsed), it is said that this information should contain the space used for redundancy in RAID setups for example. At the middleware level, I am not sure if this information is totally relevant. The important thing at the middleware level is the amount of disk space available for the grid users. The real amount of disks installed for example is some kind of internal cooking. On the other hand, it might be interesting to have some metadata information wrt the level of data security of a given storage resource (RAID level etc...). A storage resource could be less capacitive than an other one but provide more data security on the other hand: it could be an element used in the assessment of the level of service performed by a given storage resource (and not only the amount of space provided). Also the latency to retrieve the data should be documented (is it online, "nearline", offline ?), that's important when you are dealing with hybrid system with both storage resources and tapes for example. In section 6 (Intentionally Left Out Properties): if the site id can be found somewhere else, that's fine. However, having infos spread over several information systems might be a bit dangerous. And one way or an other, you need to link what is available in a storage system (or part of it) with a given site. The transfer information is said to be related to network resources, hence not in the scope of this document. However, it is an important feature. For example, serving 30 TBs of data for thousands of users is not going to be the same as having 30 TBs for archival purposes which is going to be accessed once in a while. Ie, the amount of transfer is going to have some consequences on your storage system design solutions (both hardware and software) and not only on the network resource, again the investment and the cost are not going to be the same. If you take the case of Amazon S3, they are charging also for the network usage: this is not separated from storage usage as it is defined in this document. Also, if you have an hybrid system, the amount of data transfer is directly connected to the number of cache disk that you have, the number of tape drives etc... cheers, JY

1 0