EMI SA2 Weekly Meeting

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

Wednesday 6 Oct 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 - GGUS for Testbeds and tools - "EMI Testbeds" and "EMI QA Tools". Mailing list available, SU request sent with FAQ. https://savannah.cern.ch/support/index.php?117108 RECEIVED MESSAGE: SUs will appear as "Testbeds" and "QA Tools" under the label of EMI - 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. Balasz input only. Sent also milestones. - Asked to review: DJRA1.2.1 Data Area Work Plan and Status Report DJRA1.3.1 Security Area Work Plan and Status Report - Reviewing of PT documentation? Check updates of documentation? - Metrics and Guidelines should be completed and used. We had a first meeting on ETICS metrics reports. - SA2 Deliverables and Milestones DONE MSA2.2 - Continuous integration and certification testbeds in place TODO DSA2.2 - QA Tools Documentation MSA2.3 - Large-scale acceptance certification testbeds are in plac
    
    SA2 Internal Wiki
    
    Sa2 Meetings
  - TSA2.2 – Quality Assurance Process Definition and Monitoring 5m
    
    + Status and Progress - Working on new version of SQAP. + Issues to Discuss - Status of guidelines? + Steps Next Week - Finish SQAP
  - TSA2.3 – Metrics and KPIs Definition and Reporting 5m
    
    + Status and Progress - A mapping schema for priority, severity and detection area mapping (BugMapping.xsd), a second schema (SQAPDefinitions.xsd) describing the inputs as defined in the change management guidelines and a small number of metrics XSD's are now finished and verified using xmllint. - Defining a prototype to read each middleware specific bug-tracking mapping values into a python routine for later use in ETICS. The input will be defined by each middleware in BugMapping.xml conforming to BugMapping.xsd. The prototype Python script is producing the mapping from the Savannah bug-tracking format to the SQAP Request for Change (RfC) format. - A prototype metric calculation tool will use python, xml.dom.minidom and mysql-python to provide metric results. - Issues to iron out relate to multiple mappings for one SQAP required value. E.g: 'defect' value for the change management guidelines relating to "feature vs. defect" has many values, not just one unique value. + Issues to Discuss + Steps Next Week - Finish prototype for PriorityBugs metric first and gLite bug mapping XML example. - Pass XSD's around to other metric collection partners. - Pass first bug-tracking metric calculation prototype example to SA2.4 for introduction into ETICS.
  - TSA2.4 – Tools and Repositories Selection, Maintenance and Integration 5m
    
    + Status and Progress - Collaboration with SA1 about the RPM list definition for external dependencies - sl5_x86_64_gcc412EPEL has been produced and put in production - All RPMs installed - Maven treated as special case and installed from tar.gz - ETICS migration script has been produced and it will be used to migrate many gLite configuration to the new EMI project - ETICS 3.1 Release under testing - RPMLint plugin ready will be part of 3.1.0 - JDepend plugin ready will be part of 3.1.0 - Integration guidelines updated according to latest process changes - Build configuration guidelines completed (only templates missing) - EMI EMT participation and troubleshooting - Working on the Metric storage and QA reporting - GGUS application for EMI QA Tools - ETICS Documentation improvement plan + Issues to Discuss + Steps Next Week - ETICS templates in configuration guidelines - Migration of gLite configuration to EMI via script - Migraton to the new platform - Integration builds start - ETICS infrastructure reliability improvement plan - Remove locking proposal
  - TSA2.5 – QA Implementation Review and Support 5m
    
    + Status and Progress commit build tests (Marek) http://arc-emi.grid.upjs.sk/revisionTests.php To track influences of developer commits on integrity of final the build, we developed new version of commit build test suite mainly available for release manager and developers. We can identify problems in Autogen Configure Make Make Check Make Dist Build phases. Learning GGUS procedures (EVA) 2.6 At present only instant CA and commit build tests are running. Many local meetings to solve critical situation with testbed in Kosice (Jozef) 2.2 Test and certification guidelines in progress (expected date to finish 7.10.) review of tools to visualise data in XML format + Issues to Discuss + Steps Next Week 2.6 solve recover of all testbed in Kosice 2.2 discussion about a new functional test suite for ARC PTs and proposal how to design it (Marek, Jozef, Eva)
  - TSA2.6 – Testbeds Setup, Maintenance and Coordination 5m
    
    + Status and Progress - Testbed meeting: https://twiki.cern.ch/twiki/bin/view/EMI/Minutes10012010 - GGUS EMI_Testbed Support Unit FAQ compiled - Unicore HW for testbed arrived: Started installing it - DS24 revision: ongoing discussion with Technical Director Balazs. - Fake VO support: VOMS developers use case, they will test the ARC instant CA tool. + Issues to Discuss + Steps Next Week - Bjorn: Unicore HW for testbed setup and documentation in the twiki. Milestone changing accordingly - Actions deriving from Testbed Meeting: - ALL SA2.6 population of GGUS SU mailing list - DANILO: PREPARE A TABLE with SERVICES * PLATFORMS * SITES, putting together info in the https://twiki.cern.ch/twiki/bin/view/EMI/DeliverableDNA131 deliverable with info about the possibility to deploy on same server. - Testbed central monitoring dashboard: Tomasz gets info from NAGIOS people. - Tomasz, Bjorn, Marek: BDII with just prod or RC versions for all middlewares. - DS24 integrating Balasz feedback.
- 11:10 → 11:30
  Issue and Topics to Discuss 20m
  - AOB