JRA1 monthly telcon

Monday 6 Feb 2012, 10:00 → 11:00 Europe/Stockholm

lund.room.1 (Skype)

Jon Kerr Nilsen (University of Oslo (NO))

EMI JRA1 meeting Required participants: PTs with late EMI 2 development tasks Expected participants: All PTs, area leaders, release coordinator, technical director Time: Monday 6/2/2012, 10:00-11:00 Call-in details: Skype contact: lund.room.1 Phone bridge: +46462884608 Agenda: - Welcome and head-count (5 min) - News (15 min) - JRA1 leader/TD - area leaders - release coordinator - Contractual obligations (10 min) - Deliverables, milestones - Quarterly report - Progress on late EMI 2 development (20 min) - PT reports - Questions (5 min) - AOB (5 min)

JRA1 meeting 6/2/2012 Present: AMGA - no APEL - John G. ARC CE - David ARC Clients - Martin ARC Classic SE - Aleksandr ARC Container - Aleksandr ARC Infosys - Weizhong ARGUS - Valery gLite infosys - Laurence gLite compute - Massimo, Marco glite MPI - no gLite sec - no dCache - Christian CERN Data - no StoRM - Michele Cesnet sec - yes l&b - yes VOMS - Morse SAGA - no Unicore - Björn, Bernt, Krzysztof EMIR - Shiraz Common - Cristina (sorry if I missed someone, sound quality was not exactly high-quality, neither on skype nor EVO) Minutes: News: PTB: - Started Year 3 preparations, objectives is being defined, main goal to reach stability, some more requirements, finishing ongoing development, cutting objectives/tasks - Important message to PTs: If you have any requirement you think is important for your product team, please send a message to Balazs/PTB within the next two weeks Areas: No news Release manager: Going through current release schedule. RC3 29 February last chance to finish development for EMI 2. Integration testing: PTs were requested to give info on integration tests TF will based on this define integration tests to come soon, PTs will need to write and execute tests 2 weeks to run integration tests after RC3 - comment: should give one-two weeks for writing tests - PTs should tell if the tests are too complex to write Contractional obligations Deliverables: DJRA1.{1-4}.3 - Area Work Plans and status reports - should be ready for internal review start of April. PTs are asked to post all received requirements now, input to status reports needed soon. Milestones: MJRA1.3 - Successful implementation of the common job submission and management methods - Due January - SE implementation - still need a couple of months to finish milestone - Already postponed several times MJRA1.11 - Easier end-user access capability to EMI components in place - Due February - STS - will not be finished until June MJRA1.19.2 - Integrated EMI Major Release Candidates - Due February - Can be said to be ready as of RC3 MJRA1.7 - First implementations of POSIX compliance and HTTP support - Due April - Christian will remind Patrick MJRA1.12 - Common Security Architecture Assessment - Due April Quarterly report: - Due Friday 10 - Jon's working on it, may ask for input from PTs during the week - Will use the dev tracker as basis, please all keep your tasks update - Three new KPI's for this quarterly report; Standard Compliance KPI, Product Integration KPI and Harmonization KPI - SLOC, and number of released products no longer tracked Development EMI-2 Absolute last code freeze: RC3 end of February Late development highest priority: EMI-ES, Glue2 Please all update status of your development tasks Currently 12 problematic, 9 non-responsive. If you have non-responsive tasks, please update! Questions: - What will happen with tasks that can't finish and released as part of RC3 If late for RC3, PTB will need to decide if development should continue for EMI2 update, dropped or moved to EMI 3 - Question about integration tests, is there a matrix? TF will come with requests - Question on platform support tasks Special task, we'll see what is available by end of February. More important to finish development tasks. - What is status of Debian support Impossible to say because no nightly build Next meeting will be in a month's time.