EMI SA2 Weekly Meeting

→ Europe/Zurich
CERN

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)
 
Action List
Minutes
    • 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 thanks everybody for the work during Y1 and for the release of EMI 1. - Preparation of the EU review in Brussels first rehearsal today - All hands meeting in Lund: Review and get feedback for all tasks. Task leader could prepare a first list of what want to review and then we discuss with specifi meeting maybe. Do we make a meeting and then a wiki page (this week) EGI: - Discussed in Vilnius about how they will verify the software. No news since. + Next steps EU review and AHM in Lund. + Conferences - EMI All Hands Meeting. Lund University from 30 May-1 June 2011. https://indico.cern.ch/conferenceDisplay.py?confId=124206
        SA2 Internal Wiki
        Sa2 Meetings
      • TSA2.2 – Quality Assurance Process Definition and Monitoring 5m
        + Status and Progress - Working in the QA report deliverable. - Double checking the EMI-1 release pages in terms of acceptance criteria and release information. - Collecting feedback for the metrics report from developers. + Issues to Discuss - None + Steps Next Week - Work on the feedback for the metrics report.
      • TSA2.3 – Metrics and KPIs Definition and Reporting 5m
        + Status and Progress - Finished documenting lack of category to product team mappings for BMI - finished documenting why CheckStyle and PMD fail. - Preparing feedback for SA2 metrics survey.
      • TSA2.4 – Tools and Repositories Selection, Maintenance and Integration 5m
        + Status and Progress - ETICS * Hide HIDDEN properties in the submission tab: ready to be released * "Any date" filter problem in the submission tab: ready to be released * Missed "\" when cloning: ready to be released * New ETICS Repository feature: keep reports for a longer time (under testing) - Separate cleaning of packages and jobs - Reports are not cleaned after 5 newer jobs - Volatile reports kept for 2 months (or more) * etics-dev problem building: spent some time investigating the problem but it is not solved yet. - Support * 7 externals registered * 1 EMI external * 1 GGUS ticket closed * Joni Hakala problem building * Oliver problem with --frombinary option * Fabrizio issue with dependencies and externals * Support to Oliver about DPM producing multiple src.rpms - Infrastructure * Created and deployed the SLC464 template * Deployed an etics-repository test instance for new report feature * Solving a bug in the ETICS-Monitor * Problems in CVI after their intervention: some permissions were missed * Fix revertToSnapshot script issue because the new user (replacing Alberto Resco user& pass). Manual monitoring of the pool during that time * CVI web service memory problem - Plugins * CppCheck, RpmLint, Findbugs and JCcn are ready for relase and PyLint is almost ready - Plugin documentation: https://tomtools.cern.ch/confluence/display/EMITOOLS/Plugins (three sub-categories) * Working on on a bug in the old PycCoverage plugin - QA Reports * Automatic backup of EMI QA Reports - eticsbld credential used to write to AFS - Archives created with tar.gz - reports cleaned from useless data * Started work on trend graphs for SLOC, Findbugs etc. * Contacted product teams two change build configuration in order to get findbugs to work. Some components have new configurations that are working. * Removed "new features" from bug lists, can create separate lists. * UNICORE bug tracker categories mapping, removed categories not relevant for EMI, added some that were not already mapped. * Several fixes to the chart titles * Improved the bug lifecycle chart (now average bug lifecycle). * Imporved backlog management index trend chart, scales correctly above and below the threshold after a log2() adjustment. - Other * Nightly builds of EMI updated to the new version * Lars documentation about plugins reviewed and feedback sent * Requested HTTPD logs from eticssoft and emisoft to compute download statistics + Issues to Discuss + Steps Next Week
      • TSA2.5 – QA Implementation Review and Support 5m
        + Status and Progress -participation on Nordugrid conference NG2011, -presentation regarding testing activities, -discussion about large scale testbed, performance tests, release procedure -proposal to extend period of RC testing (Balazs will initiate discussion in EMI) SA2.5 MS25 sent to Florida + Issues to Discuss during NG11 I initiated discussion about basic performance parameters for chain client-server for ARC middleware (job submission rate, concurrent requests on server and a reliability of job submission) These basic technical parameters are important if we want to analyze performance tests. The result of discussion is a common proposal that SA2 should be a body in EMI which should define these parameters. Shall we active to define these parameters or at least minimal set of parameters? + Steps Next Week finish open tasks
      • TSA2.6 – Testbeds Setup, Maintenance and Coordination 5m
        + Status and Progress * ALL sites where involved in the deployment and testing of EMI-1 products on the Intercomponent testing testbed.HERE (https://twiki.cern.ch/twiki/bin/view/EMI/Emi1CoverageSavannahTrackerConvention) find an up-to-date coverage status with remarks on services documentation/installation/configuration/functionality. also documented in tkt https://gus.fzk.de/ws/ticket_info.php?ticket=70375 * "EMI Preview Activity is also starting. Here find https://twiki.cern.ch/twiki/bin/view/EMI/EMIReleasePreview the description of activity involving outer volunteer sites + Issues to Discuss * Data management deliverable reviewer. + Steps Next Week * finish deployment/testing of mpi, glexec and argus on cream... * EMI Preview activity
    • 11:10 → 11:30
      Issue and Topics to Discuss 20m
      • AOB