EMI SA2 Weekly Meeting

Name: EMI SA2 Weekly Meeting
Start: 2011-03-16T10:30:00+01:00
End: 2011-03-16T12:00:00+01:00
Location: CERN

Wednesday 16 Mar 2011, 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 - PEB approved packaging guidelines. See bit.ly/emisa2 for the status of the others. - Open question: Can the testbed be used at the EGI TF for training purposes? Is becoming urgent.... - Reviewed the QC report from SA1 QC. - Documentation Team: PEB wants to have a team to quickly read the material produced and provide feedback. I will be in the team for SA2 if someone else wants to participate he/she is welcome. - Presentations in Vilnius. Presenters should prepare them in advance and circulate them. - The links to the videos of the SA2 training are on the EMI SA2 page http://bit.ly/emisa2 EGI: - Sent feedback to the EGI on their guidelines https://documents.egi.eu/public/ShowDocument?docid=240 Conferences - EGI UF and EMI TF joint conference. https://www.egi.eu/indico/sessionDisplay.py?sessionId=13&confId=207#20110412 - Participation from the task leaders - EMI All Hands Meeting. Lund University from 30 May-1 June 2011. http://indico.cern.ch/conferenceDisplay.py?confId=124206 + Next Step - Check the reports from the product teams
    
    SA2 Internal Wiki
    
    Sa2 Meetings
  - TSA2.2 – Quality Assurance Process Definition and Monitoring 5m
    
    + Status and Progress - Reviewing the Metrics Generation Twiki: https://twiki.cern.ch/twiki/bin/view/EMI/EmiSa2MetricsGuidelines - Working on SQAP. - Working on the next QA report. + Issues to Discuss - Policies pending PEB approval. Reminder sent on Friday: - https://twiki.cern.ch/twiki/bin/view/EMI/EmiSa2ChangePolicy - https://twiki.cern.ch/twiki/bin/view/EMI/EmiSa2ConfigurationIntegrationPolicy - https://twiki.cern.ch/twiki/bin/view/EMI/EMISa2DocumentationPolicy - Other documents waiting for PEB feedback: - https://twiki.cern.ch/twiki/bin/view/EMI/ProductionReleaseCriteria - Open issues: - Inter-component testing. https://twiki.cern.ch/twiki/bin/view/EMI/EmiIntegrationTests - Who is going to populate the EMI production repository? Who is going to create the web pages for the release? Is this all done by SA1? + Steps Next Week - SQAP and QA report.
  - TSA2.3 – Metrics and KPIs Definition and Reporting 5m
    
    + Status and Progress - investigating which is better CCCC or cppcheck. cppcheck seems to be more detailed. - installed ETICS client 1.5.2-1 in TCD, with automatically tabulated reports for EMI. - Testing cppcheck on emi.wms.* local builds. Seems to be relatively easy to run at the component level, however, at the workspace level its far to slow. Trade-off may be obtainable on its usage. - Looking at CLOC as a possibly for "Commented Lines of Code" metric, however it may need to be slightly modified for our purposes in that it is "Count Lines of Code" not lines of comment. - Putting together a "Delay in Release Schedule" metric template - Attended SA2.4 metric report generator meeting on Friday. Plots are well developed by SA2.4. + Issues to Discuss - CCCC not running on emi.wms. is there certain conditions under which it doesn't run? - is there a timescale for when pylint will be ready? + Steps Next Week - finish cppcheck investigations. Liaise with Fabio on this to try to get some outcome. - finish "Delay on Release Schedule" metric. - awaiting feedback on file naming conventions and repository location for "Up-to-date Documentation" metric.
  - TSA2.4 – Tools and Repositories Selection, Maintenance and Integration 5m
    
    + Status and Progress Support: - 3 new externals - 5 GGUS tickets closed (work done on many others) - 2 new external components Infrastructure: - Several CVI problems again this week. Service downtime and SOAP failures. - RevertToCheckpoint script changed: - Added logs - SOAPPy retry investigated - 64bit minimal Image with swap file ready - EPEL VM infrastructure updated with the swap file - There are some issues in the 32bit minimal image (missing packages) - Monitoring scripts (ongoing) - Nightly builds changed to EMI 1 RC2 QA Tools: - Report Generator status meeting 11.3 - Changes to the report generator: - Set maximum bar width in barcharts. - Added page header, added build date to header - Created front page with EMI logo - Possibility to have two charts per page - X-axis label rotated to save space - Added product and product team prefix to headlines - Backlog management: moved bars closer, fixed calculation error. - Generated two lists for missing components, components not correctly configured and components that failed to build. - Fixed titles in EMI report. - New chart fixed bugs - Chart titles are now generate from a template file. - Started working on a schema for a release schedule delays xml with SA2.3 - Plugins: pylintplugin and rpmlintplugin under testing - rpmlintplugin output should now be more readable by Internet Explorer - Redirected the output from pylint directly to a file so that there is no html in the build report - Added some warning messages to pylintplugin - Testing against a whole EMI build Docs: - DSA2.2.2 deliverable in progress - Configuration guidelines change after Oscar feedback + Issues to Discuss + Steps Next Week - Complete DSA2.2.2 - Deploy 32bit EPEL WN - Deploy 64bit minimal EPEL run as root ---------------- Latest detailed report from the report generator https://twiki.cern.ch/twiki/pub/EMI/EmiSa2MetricsReports/NightlyReport.pdf
  - TSA2.5 – QA Implementation Review and Support 5m
    
    + Status and Progress SA 2.5 no progress SA2.6 Marek will report to Danilo all team members are involved in EMI-1 RC testing I wanted to enter in discussion about post-certification testing-no time to do this + Issues to Discuss + Steps Next Week Continue in testing
  - TSA2.6 – Testbeds Setup, Maintenance and Coordination 5m
    
    + Status and Progress • CERN o - testbed updates - virtualization infrastructure • CESNET • CNAF: o Meetings attendance: SA2, EMT, INFN-Security (testbed related) o GGUS tkting o HW: security updates, openjdk vulnerability issue. o Large Scale:  more discussion on templates  Use case definition with Argus team. SA2.6 will receive a request shortly • DESY o Worked on (support and tkts handling, documentation, HW/SW administration...): * BDII problem, galway publishing wrong information • JUELICH + Issues to Discuss + Steps Next Week • CERN • CESNET • CNAF o EMI deployment? • DESY o * Getting IPs opened to outside CERN, DESY testbed users • JUELICH
- 11:10 → 11:30
  Issue and Topics to Discuss 20m
  - AOB