EMI SA2 Weekly Meeting

Name: EMI SA2 Weekly Meeting
Start: 2010-09-29T10:30:00+02:00
End: 2010-09-29T12:00:00+02:00
Location: CERN

Wednesday 29 Sept 2010, 10:30 → 12:00 Europe/Zurich

CERN

Description

Meeting Access Information:
- Meeting URL
http://evo.caltech.edu/evoGate/koala.jnlp?meeting=e8eteDvBvDataDa9I8
- Phone Bridge
ID: 62440
- Phone Bridges Numbers
http://evo.caltech.edu/evoGate/telephone.jsp

NOTE: THE MEETING IS RECORDED (for minutes-taking only purposes, then the files are deleted)

- 10:30 → 10:40
  
  Action List Review 10m
  
  Emi Sa2 Action List
- 10:40 → 11:10
  Task Reports and Progress 30m
  
  In this first meeting we will discuss on who is working on which task(s).
  - TSA2.1 – Work Package coordination 5m
    
    + Status and Progress - Alberto DM distributes the offical news from now on. - Use the EMI templates for presentation of work done in EMI or by people paid by EMI - Asked for review of Testbeds deliverable and of Quarterly Report - Review started 22/9 - Reviewing of PT documentation? - Check updates of documentation - Metrics and Guidelines should be completed and used. - GGUS for Testbeds and tools - "EMI Testbeds" and "EMI QA Tools". Waiting for the mailing list to be created - Deliverables and Milestones TODO DSA2.2 - QA Tools Documentation TO REVIEW MSA2.2 - Continuous integration and certification testbeds in place MSA2.3 - Large-scale acceptance certification testbeds are in place
    
    SA2 Internal Wiki
    
    Sa2 Meetings
  - TSA2.2 – Quality Assurance Process Definition and Monitoring 5m
    
    + Status and Progress - DSA2.3.1 is now ready for the official review: https://twiki.cern.ch/twiki/bin/view/EMI/DeliverableDSA231 - Contacted Giuseppe for upcoming reviews to see how we are going to organise the work. https://twiki.cern.ch/twiki/bin/view/EMI/SQAP#SQAP_Review_Schedule - Contacted Giuseppe and Andrea for new version of SQAP https://twiki.cern.ch/twiki/bin/view/EMI/SQAP#Forseen_changes + Issues to Discuss None + Steps Next Week - Prepare new version of SQAP
  - TSA2.3 – Metrics and KPIs Definition and Reporting 5m
    
    + Status and Progress * In the process of generating an XML exchange format for: - metrics-<name>.xml (SA2.3 input/output for a named metric) - sqapDefinitions.xml (SA2.2/PEB information: release, docs, etc) - bugMapping.xml (uniform mapping: states, priority, etc) - bugListing.xml (bugs conforming to the exchange format) * Splitting static code analysers into separate metric definitions. * Defined a flowchart from bug-trackers to metric generation. + Issues to Discuss * none + Steps Next Week * Complete all metrics-<name>.xml definitions. * Include separate static analyser definitions. * Change the above XML files to conform to the SA2.4 schema. * Define prototype scripts that use one or more of the XML files mentioned above. * Pass prototype scripts to each middleware SA2 partner.
  - TSA2.4 – Tools and Repositories Selection, Maintenance and Integration 5m
    
    + Status and Progress - Last bugfixes done for multi-node. - Testing of multi-node feature completed in 1.4.15 - ETICS documentation proposal: plan circulated internally to do a new and up to date ETICS documentation - ETICS web service logging system reviewed. Some logging levels have been modified and the log rotation has been improved - ETICS support - New plugins to be introduced in the next release:RPMlint and JDepend - Preparation of EMI image with RPM list given by EMT - Problem with LCG-DM with the etics-client corrupting the build-status.xml fixed. - working with StoRM PT to setup ETICS worker nodes in Bologna because of license problems in some dependencies + Issues to Discuss + Steps Next Week - Finish all open issues - Code freezing and deep testing of the next ETICS release - Structure the contents of the new ETICS documentation and classification of the different external resources to be included.
  - TSA2.5 – QA Implementation Review and Support 5m
    
    + Status and Progress 5.4 I sent a short survey to know status of functional test in PTs (I did not analyse feedback) 5.6 An unexpected local reconstruction affected operation of our servers. I had to find local solution to bring up all servers. I found a different place for all servers which is more safe as the first. I expect that structure will run again in the next week 4.10.2010 (At present only 2 servers are connects -ARC commits build testing) + Issues to Discuss + Steps Next Week Finalise ARC PTs test plan
  - TSA2.6 – Testbeds Setup, Maintenance and Coordination 5m
    
    + Status and Progress * ongoing activity on the review process for DSA24 deliverable. Feedbacks from Balasz. * Tomasz will setup a new bdii at cern to have just production versions and Release Candidate versions in the official bdii * administrations of current testbeds: o new versions on Cnaf UI o working on kernel updates for security bugs on SL5 servers o etics WN installation. * GGUS support unit requested: Alberto A. is following the thing + Issues to Discuss Among Balasz comments: - testbed usage: how the testbed is used (who can use it, how is it planned to be used, how those the testbed fits into the general testing procedures? - the description of the procedure and average time to deploy a certain version of EMI service. A scenario: the ARC CE PT wants to test its data staging module against particular Dcache versions Do we need to add a part in https://twiki.cern.ch/twiki/bin/view/EMI/EmiSa2CertTestGuidelines mentioning the need for a "Release Candidate state process tracking and notification to testbed?" * I received a request for supporting fake CA in the EMI testbed: do you see any problems at doing that? + Steps Next Week * expected Unicore testbed setup * integration of review for DS2.4
- 11:10 → 11:30
  Issue and Topics to Discuss 20m
  - AOB