Go to the Indico Home Page Oldest event Older event Up to category Newer event Newest event Printable version
  • Compact style
  • Indico style
  • Indico style - inline minutes
  • Indico style - numbered
  • Indico style - numbered + minutes
  • Indico Weeks View
    • Switch to the management area of this event
    Login

    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: preparation of the AHM meetings. - SA1 says that some of their KPIs are from our metrics (discuss with Mathilde and Giuseppe). - Release mgmt will be discussed. Do some guidelines need to be updated? - REGISTER HERE: http://indico.cern.ch/conferenceDisplay.py?confId=108375 - No SA2 Side meetings we will try to fit in the slot we have: - Preparation of the AHM, will have during the SA2 session: Presentations at AHM - overview (A. Aimar) Discussions (prepare a couple of slides?) - tools (L. Dini) - guidelines (M. Alandes) - metrics (E. Kenny) - testbeds (D. Dongiovanni cannot participate, A. Aimar but difficult to answer difficult questions, Jozef?) - Preparing the SA2 Quarterly Report for the EU. - GGUS for Testbeds and tools: "EMI Testbeds" and "EMI QA Tools". Available and is it working? Oliver is trying one for testbeds this morning. - PEB asked for when on the Testbeds there will be installed the Production and RCs version of all products. For general usage by the PTs. - Asked for review of Testbeds deliverable (ended up to Gianni?) and of Quarterly Report
          SA2 Internal Wiki
          Sa2 Meetings
        • TSA2.2 – Quality Assurance Process Definition and Monitoring 5m
          + Status and Progress - Reviewed Software Maintenance and Support Plan. - Phone conference with Massimo and Alberto to go through the SA2 review of the Compute Area work plan. - More feedback from Cristina for EMI 0 delay. - On going discussions with Alberto di Meglio and Francesco to understand who is responsible for the information providers existing in gLite. + Issues to Discuss - The following documents are part of the SQAP and haven't been finished yet: - DSA1.1 Software Maintenance and Support Plan -> SA2 Review is done but twiki is not updated. Should we contact Florida? - DSA1.2 - Software Release Plan -> No news. Is this ready for review? - DSA2.4 Continuous Integration and Certification Testbeds -> Is the review process finished? This seems to be never ending. - DJRA1.1.1 - Compute Area Work Plan and Status Report -> Author working after review. - DJRA1.2.1 - Data Area Work Plan and Status Report -> Author working after review. - DJRA1.3.1 - Security Area Work Plan and Status Report -> Author working after review. - DJRA1.4.1 - Infrastructure Area Work Plan and Status Report -> Seems to rejected by JRA1? Is this status presented to PEB? What's their opinion on these delays? Do we need to prepare any presentations for AHM? + Steps Next Week - Prepare recomendations for EMI 1. - Still finish the new version of the SQAP!
        • TSA2.3 – Metrics and KPIs Definition and Reporting 5m
          + Status and Progress - Latest version of document includes pseudo code and visualisation examples for PriorityBugs requested by Lars/Andres. - Working on defining best way to visualise the PriorityBugs and other metrics. This also serves as a secondary check on anything that is produced by SA2.4. - Working on the pseudo code for the BackLog and other metrics. - Attempting to obtain 3rd level incident GGUS ticket information based on direct GGUS queries. - Collecting/collating information on products per product teams. + Issues to Discuss + Steps Next Week - Awaiting prototype visualisation. - catching up ARC and dCache bug-listings.
        • TSA2.4 – Tools and Repositories Selection, Maintenance and Integration 5m
          + Status and Progress - EMI Integration work - EMI EMT - Dcache configuration synchronizer - Script to add externals with package.prefix to all EMI externals - Installed new externals into EPEL - Pedro bulk update for EMI DM - Validated EMI configurations against guidelines (errors reported) - Fixing of some wrong DB entries in the EMI project - Investigation of "[" error in the EMI build - Client bugfix for EL5.SL5 working - DM support - Attend daily meeting on infrastructure issues - Build/deployment/test cycle with ETICS - Investigation/Migration to CERN CVI to improve infrastructure - New plugins to be released as part of ETICS 3.2 - Other plugins under development - ETICS 3.2 release preparation and testing + Issues to Discuss - Packaging and release guidelines The packaging guidelines are pretty much the Fedora and Debian ones. When EMI-0 or EMI-1 will arrive to the point of packaging, something may be added... but right now the Fedora and Debian ones are more than enough. About the release guidelines, the only thing I have heard is that Owen is not 100% satisfied by the change-management guidelines regarding how to release software and he has some cases he would like to clarify about externals, repositories and timing of releases. + Steps Next Week - Deliverable? - New iteration start - Last bit of the ETICS client takeover - ETICS DB separation - ETICS infrastructure monitoring and quattor - Metrics related tools prototypes - ETICS 3.2 Release - Bugfixes (Chrome support, webservice) - New software versions in servers (SL5, HTTPD, Mysql) - New plugins - New ETICS client 1.5.0 released after the server release
        • TSA2.5 – QA Implementation Review and Support 5m
          + Status and Progress SA2.6 testbed infrastructure recovery -two rooms are allocated 1th room central computer hall (only rack servers are allowed in this hall) status -rack is in this hall -we are waiting on realization of electric power connection to the rack -servers for production grid and part of functional tests are prepared for new installation 2th room at department (older machines PC desktops) status -we allocated new space -we need to check el. grid in this room -we ordered additional cooling equipment -many of EMI services are running on servers in this room -servers for revision testing are located here. Expected deadline for total recovery: the end of the next week (20th November). Our goal is to have all infrastructure ready before all hands meeting in Prague. 5.4 Discussion with Balazs about increase testing activities of UPJS team in JRA1. Conclusion is not yet clear. Analysis of new infrastructure for functional tests. The ifrastructure should be more flexible as previous one. Marek and Eva started coding. Test plan for ARC PTs postphoned (all hands meeting) + Issues to Discuss + Steps Next Week to finish testbed recovery
        • TSA2.6 – Testbeds Setup, Maintenance and Coordination 5m
          + Status and Progress - documenting monitoring solutions in the twiki (CERN, UNICORE,ARC) - documenting resource publishing solutions in the twiki (CERN, UNICORE,ARC) - testing emi VO: - UIs, data management services, creamce works fine - ran on issues with WMS job submission using new VO - added use cases description in the twiki + Issues to Discuss - PEB comments on large scale testbed milestone proposed approach? + Steps Next Week - CESNET Missing on twiki info update - DSA2.4 review from SA1 - deployment of testers VO, going on.
      • 11:10 → 11:30
        Issue and Topics to Discuss 20m
        • AOB