J. Jensen Deliverable Review Form

Jens Jensens initial review was delivered via e-mail. The orginal mail can be found here. An agreement with Jens, his e-mail has been shoehorned into the EMI review form below.

Identification of the deliverable or milestone
Project: EMI Deliverable or milestone identifier: DJRA1.2.1
Title: DJRA1.2.1 - Data Area Work Plan and Status Report Doc. identifier: EMI_DJRA1.2.1-draft-6.docx
Author(s): Patrick Fuhrmann Due date: __

Identification of the reviewer
Name: J. Jensen Affiliation: STFC EMI Activity/External project or Institute: External

Review date 10/10/2010
Author(s) revision date mm/dd/yyyy
Reviewer acceptance date mm/dd/yyyy

Attach the reviewed document to the deliverable page, put here a link

General comments

First of all, I am happy that EMI has a data storage and management area. As head of the GridPP storage and data management group I welcome this, and I am glad to see it in good hands, and I look forward to collaborating with EMI.

As another general comment, I welcome the strong emphasis on interoperability and open standards and working with standards bodies. I also welcome the migration plan to GLUE 2.0. Note that this also depends on components outside EMI, so should be coordinated (and interoperation tested) with those components.

Additional recommendations (not affecting the document content, e.g. recommendation for future work)

Detailed comments on the content

Note 1: The reviewers must list here any observation they want to track explicitly and that require interaction with the authors
Alternatively all changes must be listed in the document itself using Word change tracking features (if you use Word)
Note 2: These comments have to be explicitly addressed by the authors and the action taken must be clearly described

N Page Section Observations Is Addressed?
1 16 4.1.1 Reviewer : Missing 'catalogue Synchronization' was intended and is not a design flaw. Fixed (Rephrased)  
2 0 0 How is feedback obtained from sysadmins and users, and how is work prioritised and triaged See below  
3 8 2 Explain the phrasing "global parallel filesystem" Fixed(now cluster file systems)  
4 0 0 How is portability addressed. This is a good point, which I can't answer. What happens with all the software when SL6 is coming  
5 0 0 Is there a release plan, quality control, and pre-release testing, or is this part of a wider EMI plan? Different deliverable, see below  
6 10 3 Restrict the title "State of the Art" to EMI components Fixed  
7 15 3.4 Is there a wider role for CDMI, and if so, what? Fixed in "State of the Art"  
8 0 0 Is any work foreseen on WAN transfer protocols? Is there a roadmap for GridFTP v2? Fixed in 4.3.2  
9 0 0 Are the following protocols resp. access protocols forseen in EMI-Data : iRODS, Apache, Hadoop, xootd Revoked by reviewer  
10 0 4.1.8 For example, should ARGUS be a single PDP for all middleware? Should they share libraries? Should the code be refactored and shared between the three stacks? Fixed : 4.1.8 last sentence  
11a 22 4.3.11 Which deployment frameworks will be supported? Not relevant : EMI is not about deployment (PEB/PTB decision)  
11b 22 4.3.11 Which monitoring frameworks will be supported? Monitoring framwork is not part of the DATA Area, maybe not even of EMI  
12 16 4.1.1 The reviewer doesn't believe that the catalogue synchronization effort is required. Misunderstanding, he does  
13 17 4.1.3 SRMs are actually interoperating, so it would be interesting to see more details about the proposed work. 4.1.3 Improved  
14 18 4.2.2 4.2.2 is a bit thin for two very complex topics (maintainability and usability). This is true, but to keep the deliverable within reasonable limits, I concentrated on common efforts and not on individual (PT) activities, as they are only funded by EMI to a very small extend  

The reviewer raised the question of user feedback mechanisms, software quality control and software portability. These issues are handled by different sections of the EMI project and in the opinion of the author of DJRA1.2.1 those issues shouldn't be repeated in the Data Area deliverable. As information for the reviewer :

Quality control

  • DJRA1.7.1 Software Development Quality Control Report (undergoing review)
  • DSA2.1 Software Quality Assurance Plan (finalised)
  • DSA1.3.1 - Software Maintenance Quality Control Report (undergoing review)

User/community feedback

There is a proposal by the EMI directory on how to manage user/community feedback which still needs to be formalized. This should be seen as a first draft :
  • EMI take requirements from EGI, PRACE, WLCG, etc using channels provided and managed by those projects
  • In general direct submission of requirements and feature requests to EMI is discouraged to avoid "double counting" or having to merge requirements from too many places
  • For EGI the main channel is the User Communities Forum, for PRACE it is under discussion, for WLCG is a yet-to-be-finalized WLCG-wide technical coordination body
  • The actual mechanism can be based on GGUS ticket submission, but EMI will set up a requirement tracker for internal consumption that will have to be synchronized in some way with external requirement trackers (e.g. EGI uses RT)
  • This works for all users working with one of the above mentioned infrastructures. Not clear yet to me how we can deal with other types of users. Will there be enough of those to justify an EMI-managed requirement collection process?

Any other modification, spelling or grammatical corrections, etc must be done directly in the document using tracked changes or similar mechanisms that allows the authors to identify which correction is suggested.

Topic attachments
I Attachment History Action Size Date Who Comment
PDFpdf EMI_DJRA1.2.1-draft-8.pdf r1 manage 2718.5 K 2010-11-18 - 16:03 PatrickFuhrmann Draft 7 plus fixes for Jens
Edit | Attach | Watch | Print version | History: r9 < r8 < r7 < r6 < r5 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r9 - 2010-11-25 - PatrickFuhrmann
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback