First round of reviews for DJRA 1.2.2 : Marias Review

Section: General

It would be very useful to have a summary of which objectives were achieved and which ones weren’t. It’s difficult to get a general idea

Good idea. GUNTT Chart added.

Section: Achievements and deviations in consolidating the usage of the storage resource manager protocol

What about SRM Integration into UNICORE? It’s mentioned in DJRA1.2.1.

Added paragraph:

The objective 1.4 in DJRA 1.2.1 is not affected as the integration into UNICORE is based on the existing OGF specification plus the document [R43], describing differences in different implementation. Moreover, it is very likely that the UNICORE team will decide to adapt an existing SRM client, which guarantees interoperability.

Section : Achievements and deviations in enabeling standard posix file access for emi storage elements especially nfs4.1/pnfs

This doesn’t mention anything about the performance and reliability testing of native POSIX and NFS 4.1 implementations. It doesn’t mention either whether results were reported at CHEP

The chapter actually does exactly this. See all the references. However, I added an additional remark for DPM.

It only talks about dCache, was it planned that only dCache did this?

For EMI-1 only dCache and StoRM were supposed to provide production level POSIX. StoRM does through GPFS. GPFS is a industry product. It doesn't make sense to measure this.

NFS41. is extremely well tested and there are 3 references to documents where this is described. Test have only been done by dCache not by DPM yet. Therefore no result. As it wasn't requested I don't need to mention this.

Not clear whether POSIX is available or not in StoRM. In DJRA1.2.1 is says this is available from day zero!

Find the following sentences in the text

• As the StoRM storage element is build on top of cluster file systems, POSIX access is naturally available.
• StoRM provides POSIX I/O through its file-system backend,

Nevertheless I addd a picture on how StoRM and DPM/dCache and Linux are handling POSIX

What does it mean a prototype implementation?

I changed it to functional prototype which is a technical term : See Wikipedia

What’s preventing them from providing production implementation?

The production implementation for DPM is due for EMI-2.

Section : Achievements and deviations in providing the WebDAV data access standard fo all emi storage elements

According to workplan they should have provided read access data via http in PM12. Maybe it’s worth explaining why this was not achieved.

I added : A prerequisite of the WebDAV implementation is read access to data via http(s). This is available for dCache and DPM in EMI-1. Due to some restructuring of the StoRM front-end, releasing this feature for StoRM is delayed by 2 months.

Section : Achievements and deviations in giving unicore access to grid resources by implementing SRM and LFC client functionality

Does this mean that the prototype that was supposed to be ready by PM12 is not finished?

No, it is finished. I added the sentence : A prototype of the UNICORE LFC client is available for M12

The 'not finished' refers to the SRM not the LFC : SRM client still needs to be integrated.

Section : Achievements and deviations in migrating from the GLUE 1.3 schema to GLUE 2.0

It would be good to mention what has been the common agreement of the interpretation of the specification and whether some work has been done together with OGF.

It actually already was by the reference to the OGF document but I added another sentence on OGF.

Section : Achievements in evaluating the benefits of utilizing a common messaging infrastructure within the EMI Data area

What are the requirements passed to the infrastructure group in the end?

No requirements were passed. Just the areas of interest.

Section : GENERAL

Sorry, for some reason two objectives were not in the deliverable I sent out. I found them and put them back into the document. It is about monitoring and improved maintainance.

-- PatrickFuhrmann - 24-May-2011