ETICS Technical Commitee

→ Europe/Zurich
TBD (CERN)

TBD

CERN

Alberto Di Meglio (CERN)
Description
Conference Name: ETICS Technical Committee meeting Recurrence: Every Thursday at 15:30 CET Dial-in numbers: +41227676000 (Main) Access code: 0126137 (Participant) Participant site: https://audioconf.cern.ch/call/0126137
    • 15:30 → 15:35
      Welcome and headcount 5m
    • 15:35 → 16:00
      Status reports 25m
      Highlights of the week, 5 minutes for each WP (NA2, SA1, SA2, JRA1, JRA2)
      • NA2 5m
        DNA2.8 Dissemination and Use of Knowledge Plan (Third Update) ready for internal reviewers • DNA2.6 resubmission (long-term sustainability strategy) still working on little adjustments according to comments coming from ENG internal reviewers and waiting for small contributions from CERN (exploitation plan and a business scenario). • Preparing the new version of the brochure which will be ready to be handed out at the EGEE09 conference • QR6 for NA2 was sent at the beginning of this week. • Sent the MoU to D4Science project. They have started the procedures for its signature.
      • SA1 5m
      • SA2 5m
        Support ------- - SZTAKI in shift. 5 tickets, 3 solved (2h), 2 escalated (1h). QR6 metrics for the first level support shows we are very fast in tackling problems (average around 3h to solve or escalate) but still too many are escalated to second level support (50%). We are trying to understand whether it's possible to improve that. Were any of the tickets assigned to ETICS Experts something that should have been solved at first level support? Infrastructure Integration Job Submission ------------------------------------------ - Received yesterday instructions from Marian on how to get the submitter service automatically deployed with the ETICS scripts. We are changing things accordingly. Any progress on the availability of the gLite UI on etics-dev? - Started working on moving to using the gLite API instead of the command line. - EC2 submitter development slowly going on. At this point an account to test things is needed. Deliverables ------------ - DSA2.5 PM15 Completed . What shall we do with the testing guidelines for DSA2.5? Do we have news so to consider delivering an addendum as agreed at DSA2.5 delivery? - DSA2.6 PM20 Not started yet.
      • JRA1 5m
      • JRA2 5m
        Implementation TestSystem GUI was updated following the conversations with Lorenzo. The plugin registration doing in step-by-step approach has been implemented. Today will be integrated into etics-dev and hopefully it will be in tommorow’s morning build. Now just the GUI is added to the etics-dev. The web services will be added in the coming days. Probably some issues with the rights will appear. This issue will be tested. Selenium tests for the GUI are in progress. Plugin development The reguired old plugins have been updated according to the discussions and are uploaded to the CVS. Andras has finished the implementation of the Vera++ and Cppcheck following the ’template’ discussed for other plugins. Some final tests needed and he will upload to the CVS soon. DesktopGrid scenario in Sztaki They continued to work on the desktopgrid scenario. They managed to do builds for all tree connected applications (BOINC, DC-API, uppercase) just on one platform. Deliverable, reports Main parts of DJRA2.5 is ready, but we are waiting for Sztaki’s contribution. They started to work this week after holidays and can contribute with their part just on next Monday. On Monday I will send the internal review version. Quaterly report will be sent this week On-line journals list for Isabel will be sent next week
    • 16:00 → 16:05
      User satisfaction survey, AOBs 5m
      First version of the online survey at: http://etics.web.cern.ch/etics/survey.htm
    • 16:05 → 16:20
      Deliverables, milestones and planning check 15m
      Formal check of agreed milestones and planning
    • 16:20 → 16:25
      ETICS USIS (User Satisfaction Improvement Strategy) 5m
      Improving user satisfaction about usage of the ETICS services is critical. ETICS is often perceived as slow and difficult to use. This is due to a number of factors: 1) Need for technical improvements in speed and usability 2) Disinformation or third-party rumours 3) General resistance to adopt 'procedures' We need to understand what to focus on and have a plan to address this issue as a combination of technical enhancements, training and dissemination. Where to start?
    • 16:25 → 16:30
      AOB 5m