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
    • 1
      Welcome and headcount
    • 2
      Status reports
      Highlights of the week, 5 minutes for each WP (NA2, SA1, SA2, JRA1, JRA2)
      • a) NA2
        Dissemination and Exploitation - Sent an abstract for the QA&TEST conference for a 4 hour tutorial on ETICS testing and quality verification features - Proposed ETICS as build and test tool to a software development team in Neta part of Engineering (http://www.netanet.it/). Exchanged e-mails and phone calls on general information on ETICS. Hoping to organize a demo for them. - Bad news from CBT. They are interested in ETICS but haven’t got personnel to dedicate to the “ETICS experiment”. - Uwe is at the Hannover Messe representing ETICS: brochures are being handed out, a video was prepared and a presentation was given on 22nd. - Working on improving ETICS website page ranking on search engines A-QCM - workshop with CTI took place on the 13th and 14th April, will send a report on it soon. - Preparing a document on the planning and strategy to follow for ISO standardization to discuss at the PMB Training - D-Grid interested in the organization of a workshop on ETICS. Need to chose location, and period. Working on planning of activities mostly of the A-QCM and the Long-term sustainability strategies task taking into consideration the feedback received from reviewers.
      • b) SA1
        Several absences after the Review, restarting at full speed now. ++ Releases Testing 2.4.2 (bug fixes to the web services and webapp) Preparing 2.4.3 (repository and client 1.4.7) Release descriptions are available here: https://twiki.cern.ch/twiki/bin/view/ETICS/SA1ReleasesContents ++ Development and Infrastructure Bug fixes on web services Started to integrate disseminator with the last version portal's version. VM Bootstrapper progressing, one month for the demo. Debugging with UoW the X-site migration Debugging with Uwe installation at VEGA ++ Planning Started planning meetings and will involve other activities. - Current activities/bugs - Plugins - AQCM report - privacy, authorization, etc - import/export from other systems - JRA2 test design plugins - SA2 job submitters - bootstrapper - client - etc
      • c) SA2
        Support ------- - Michele, Marco in shift. 4 tickets, 2 solved (average 2h42m), 2 escalated (average 11h15m) - Evaluated commenting extensions for the support portal - 4 externals added New applications ---------------- - Working with ARC peolpe to fix their build problems - Installed externals for the infngrid release project Infrastructure Integration Job Submission ------------------------------------------ - Basic security implemented on the glite-submitter, authz granted after the dns contained in a file - Preparing the documentation on how to write a plugin for the submission service (will be used for UNICORE) - We have bought the machines for the ETICS VO. - Ping NA4 person for the seed machines. He said they enabled the VO on one site, but I haven't had time to submit a test job yet.
      • d) JRA1
      • e) JRA2
        * Build&Deployment of JRA2 services In the last period the focus has been on to automatise the build and deployment of the new ETICS Test system. The work is in a good shape, all the processes are modelled in ETICS and the necessary build and deployment scripts are ready. Until know it has been checked just as local build. Now the source code is in ETICS CVS so we will try it as remote build as well. There are still some more work to do to fully automatise the process and to think about extending it for multinode. Additionally to ease the technical work, our aim with this process is to have a live example on the whole functionalities of ETICS usage for marketing purposes. Therefore, it would be good to have a separate project for all this stuff. Now it is done in quite a messy way in org.etics.testsuites/pluginstests subsystem. * Mapping between metrics and the warnings Assisting Eng in the mapping between metrics and the warnings generated by test plugins.
    • 3
      Review post-mortem
      Brief discussion of review results
    • 4
      Deliverables, milestones and planning check
      Formal check of agreed milestones and planning
    • 5
      ETICS USIS (User Satisfaction Improvement Strategy)
      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?
    • 6
      AOB