Minutes of June 25, 2010 EVO conf. of the PT leaders of the EMI Compute Area ============================================================================ Attending: Bj??rn Bernd Martin Massimo Shahbaz It is necessary to prepare the workplan for the EMI compute area This is needed for 2 deliverables: - DNA1.3.1 "high level technical plans", to be written by the EMI Tech. director (Balazs) - DJARA1.1.1 (deliverable specific for the compute area). Also the other areas have to provided such deliverables - DNA1.3.1 has to cover the whole duration of the project - DJRA1.1.1 has to cover only the first year - At the end of each year we will have to report (in another deliverable) what we have done wrt what we planned (e.g. we planned to do A and B; instead we did A and C because of ...). We will also have to provide an update of the workplan - For DJRA1.1.1 it is also needed a current state of the art of our services - DJRA1.1.1 should be finalized (i.e. ready for internal EMI review) by July 10. - Each PT leader was asked to provide a plan for its product team These workplans are not really homogeneous (e.g. different level of details, different areas covered, etc.) - We have now to provide a coherent workplan for our area, compatible with the DoW, agreed by the PTs, specifying among the items which ones are supposed to be done in the first year. - This must be submitted to the PTB by Tuesday 29. The PTB will then have to analyze such inputs (e.g. if we write that we rely on X supposed to be provided by some other areas, plans for X should be reported in the workplan for that area) - The new developments to be reported in the workplan must be classified in 2 categories: - harmonization: adoption of standards, simplification, drop of duplication - evolution: new developments targeted to the provision of new functionility required by users, etc. - The current draft (v. 0.3) of the workplan for the compute area is quickly analyzed: * Definition and adoption of job related standard interfaces Fine with everyone * Adoption of information service related standards Martin reports that the use of Glue2 is not implemented in all ARC components so it should be written that it will be finalized * Harmonization of the authorization mechanisms Massimo reports that according to Oxana, the integration with Argus within ARC is fine. Martin will double check. Unicore is willing to assess it. * Harmonization of the other security mechanisms Fine with everyone * Harmonization in the integration with the accounting systems Fine with everyone * Harmonization in the service monitoring and management tools Fine with everyone Massimo reports that he can't see plans for the provision of such tools (to be provided by the infrastructure area). He already raised the issue with the PTB * Removal of Dependency on Globus toolkit in the ARC CE ARC specific item * Harmonization in the use of the job bookkeeping services Fine with everyone * Harmonization in the parallel and MPI job support The harmonization for the paralell and MPI job description is something that is supposed to be done also in the context of "Definition and adoption of job related standard interfaces" No clear ideas at the moment if and how the backends (mpi-start, ARC RTEs, UNICORE execution environments) can be harmonized It is agreed to write that this will be assessed. - Evolution section Martin will provide an update for the ARC client by today (June 25). It will be clearly specified what can be done in the first year - Bernd will provide an update for UNICORE by Monday at latest Massimo will integrate these new inputs and will modify the current draft also according to the comments raised during the meeting. He will then circulate (likely Tuesday) the new version. He will allow half day of internal review before submitting to the PTB - Current status: Bernd provided the input for Unicore. Now we have all the contributions Massimo will integrate it in the current draft