1. JRA Execution Plan 13 January 2003 - 1 JRA1 Execution Plan Frédéric Hemmer EGEE Middleware Manager EGEE is proposed as a project funded by the European Union under contract IST-2003-508833

2. JRA Execution Plan 13 January 2003 - 2 Objectives Provide robust, supportable middleware components Select, re-engineer, integrate identified Grid Services Evolve towards Services Oriented Architecture Adopt emerging OGSI standards Multiple platforms Selection of Middleware based on requirements of The applications (Bio & HEP) In particular requirements are expected from LCG’s ARDA & HepCALII The Operations E.g. deployment, updates, packaging, etc.. Support and evolve of the middleware components Evolve towards OGSI Define a re-engineering process Address multiplatform, multiple implementations and interoperability issues Define defect handling processes and responsibilities ARDA has completed the RTAG. A new prototyping activity is starting, but not in a stage yet we can do planning. LCG has decided to take ownership of the LCG-2 code and to ensure their own support. This has impact on JRA1, at least for the CERN part

3. JRA Execution Plan 13 January 2003 - 3 Partners

4. JRA Execution Plan 13 January 2003 - 4 Milestones and Deliverables for the first year Month Deliverables & Milestones ItemLead Partner M03MJRA1.1Tools for middleware engineering and integration deployedCERN M03DJRA1.1(Document) Architecture and Planning (Release 1)CERN M03MJRA1.2Software cluster development and testing infrastructure available CERN M05MJRA1.3Integration and testing infrastructure in place including test plans (Release 1) CERN M05DJRA1.2(Document) Design of grid services (Release 1)CERN M09MJRA1.4Software for the Release Candidate 1CERN M10MJRA1.5Integrated Release Candidate 1 enters testing and validation period (Release 1) CERN M12DJRA1.3(Software) Software and associated documentation (Release 1) CERN

5. JRA Execution Plan 13 January 2003 - 5 Product Breakdown Structure (TA) Tools TestingIntegrationInformation Services Workload Management Services Data Management Security Resource Brokering Resource Access Accounting Logging Bookkeeping EGEE JRA1 Regression Test Testing Processes and Procedures

6. JRA Execution Plan 13 January 2003 - 6 Product Breakdown Structure (ARDA) ToolsTestingIntegrationGrid Access Services Workload Management Services Data Management EGEE JRA1 Authentication Authorization Information Services Auditing Services Accounting Services Site Gatekeeper Packaging Services This will further be detailed based on preparation of the prototype

7. JRA Execution Plan 13 January 2003 - 7 Task Breakdown

8. JRA Execution Plan 13 January 2003 - 8 Effort needed and responsibilities

9. JRA Execution Plan 13 January 2003 - 9 Training requirements

10. JRA Execution Plan 13 January 2003 - 10 Risk analysis

11. JRA Execution Plan 13 January 2003 - 11 Issues related to other activities

12. JRA Execution Plan 13 January 2003 - 12 Changes to Technical Annex Minor changes such as LCG-2 replaces LCG-1 ARDA and HEPCal II have completed Prototype work But does this pertain to the TA?

13. JRA Execution Plan 13 January 2003 - 13 Steps needed before project startup Finalize hiring and define training needs Complete table 4.5 Setup Engineering Management Team Define membership into Security group Define membership in QA Group Define membership in Architecture Team Set up development and implementation guides Complete the ARDA services document Check compatibility with non-Physics applications Validate security model Start the ARDA prototyping activity (with EGEE unfunded effort) Understand the support model as proposed by SA1 Define a process to obtain SA1 requirements Clusters to come with a task breakdown

14. JRA Execution Plan 13 January 2003 - 14 Other points to be addressed in the near future JRA1: Current Software - organise continued support for software currently deployed on LCG service by identifying the groups responsible for each module. Establish composition of engineering management board and architecture group Assess the suitability of the GT3 as a OGSI implementation taking into account the list of selection criteria previously established. Clarify plans for the suggested "pilot project" to investigate an OGSI based prototype grid Middleware suite Software Clusters (CERN, Italy, NEG, UK) to clarify plans for their development, integration and testing testbeds in terms of scale, sites and support. Deployment: understand what tools and mechanisms will be used for software packaging and distribution Clarify the relationship with fabric mgmt software and what is expected from it compared to grid Middleware. JRA2 (all points in discussion with JRA1, JRA3): Clarify which parts of LCG SPI can be reused in EGEE. Produce templates for all deliverables, and other important documents of the project. Produce schedule for review of deliverables in PM1-3 including identifying activities that should provide reviewers and moderators. Expand all steps of software development process to clarify what artifacts are to be produced, when and by which groups. Establish composition, management and organization of the Quality assessment group (QAG) Understand what training will be necessary for the software process and tools and establish a training schedule in conjunction with NA3.. JRA3: Need to clarify role of VOMS with INFN and who will support it (not clear in Technical Annex). Establish process and sources of input for requirements survey (MJRA3.1, PM3) Define role, scope organization composition and management of the European Grid Policy Management Authority (PMA) (MJRA3.2, PM3) Clarify the relationship between the PMA and the grid policy forum to be established by NA5. While it is not scheduled until PM4, the content of MJRA3.3 (OGSA SEC service initial recommendations for re-engineering) will probably affect JRA1, and SA1 and hence its implications needs to be clarified as early as possible. JRA4: Clarify if any software will produced and if so understand the relationship with JRA1 & JRA3. Note: currently this activity has n o milestone or deliverable before PM6 - this does not follow the recommendations of the project and EU who would like to see some output at PM3.