JRA1 all-ears status meeting (note: new date)

Friday 19 Oct 2012, 10:00 → 12:00 Europe/Zurich

http://evo.caltech.edu/evoNext/koala.jnlp?meeting=MMMeMn2928D9Du9l9iD29M (EVO)

Postponed to Friday 19.10.2012.

JRA1 all-ears 19.10.12 Present: Balazs (chair), Jon (minutes), Christina, Zsombor, Bernd, Patrick, Will, Henri, Andrea G., Florido, Aleksandr, PhoneBridge1, PhoneBridge2 Minutes: The meeting format is adjusted to the capabilities of EVO. No discussions, just going through the tasks to get a very quick overview. Balazs will go through the tasks, Jon takes minutes. Went through all Compute and Data tasks one by one. Question: Will this task be finished by the code freeze. Answer: Yes - No - No clear understanding of the task Compute: Task 31464: Yes Task 26210: no-one present 22426: EMI accounting record implementation for UNICORE CE - No (problematic because dependency on CAR agreement) 22424: EMI accounting record implementation for CREAM CE - No (problematic, depends on CAR agreement) 22410: Glue 2.0 support in ARC Compute Clients - Yes 22408: Glue 2.0 support in WMS - no-one present 22400: Client-side implementation of EMI-ES in ARC - Yes 22399: Client-side implementation of EMI-ES JAVA API - Yes 22398: Server-side implementation of EMI-ES in CREAM - Yes 22397: Server-side implementation of EMI-ES in A-REX - Yes (only to 90% level due to internal ARC structure) 22396: Server-side implementation of EMI-ES in UNICORE - Yes 31516: Exclusive node and/or multiple core allocation: Use cases - no-one present (no response but will most likely go to problematic) 31482: EMI parallel execution framework: UNICORE/X deployment - no clear understanding of the task 31474: EMI parallel execution framework: ARC CE deployment - no-one present 31533: Accounting of parallel jobs in CAR - done 31521: Evolve EMI products: ARC CE LRMS framework cleanup - no-one present 31519: Tagged jobs design - no-one present 31466: Adapt MPI_start to EMI-ES - no-one present 22425: EMI accounting record implementation for ARC CE - No (problematic, depends on CAR agreement) 30808: Evolve EMI products: SLURM support for CREAM - No (waiting for APEL, no info from APEL, APEL got no response from SLURM team to get a SLURM test environment) Can conclude that getting CAR 1.1 agreement in place is now getting critical. Data: 22150: Cat sync plug-in for StoRM SE - no-one present 22149: Cat sync plug-in for dCache - yes 32115: Migration to EMI_datalib: lcg_utils - yes 22370: StoRM SE test and deploy EMI accounting record sensors - no-one present 22369: DPM test and deploy EMI accounting record sensors - no-one present (but probably almost done) 22368: dCache test and deploy EMI accounting record sensors - yes 22367: StoRM SE implement sensors to populate the EMI accounting record - no-one present 22365: DPM implement sensors to populate the EMI accounting record - yes 22363: dCache implement sensors to populate the EMI accounting record - yes 32133: Federation frontend for the transparent distributed storage - yes 32132: Authentication mechanism agreement for the federated storage - sufficiently ready for code freeze 22225: Add webdav protocol to StoRM SE - no-one present 22153: Extend cat sync functionality for StoRM SE - no 22176: Pilot FTS service - done Stopped after one hour after going through all Compute and Data development tasks. Next meeting next week will cover the remaining development tasks from the Security, Infrastructure and Cross areas. Next meeting: Friday 26.10.12 - going through Security, Infra, Cross (guaranteed to last at least 2 hours).