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 Dial-in numbers: +41227676000 (Main) Access code: 0126137 (Participant) Participant site: https://audioconf.cern.ch/call/0126137
Minutes
    • 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
        • Preparing ETICS 2 description for EGI database. I will circulate it next week for comments • Done some thinking on USSIS, what about a questionnaire to understand the level of satisfaction and what users and developers feel is not working or is working in ETICS system? • Gave a three day training to Maria. What about second week in July for training at CERN?
      • SA1 5m
        +++ Infrastructure The setup for the Release Candidate is in place (etics1 + etics2-repository). The setup complete based on configuration: etics_R_2_1_0_0_RC1 Some problems of time synchronization with SLC4 running in virtualized machines that we will solve by accessing directly NTP servers from the virtual node. Added rights in repository/externals to Valerio and Elisabetta if more are needed please ask. Prepared page describing the Virtual Images management (updates, modification). Available under: https://twiki.cern.ch/twiki/bin/view/ETICS/SA1VirtualizationVMManagement +++ Software The work on moving the ETICS client to use sqlite and improving the speed is the main focus of the next client release. The ETICS web-application will be released (2.0.7) to add support for FF3. Added recursive package content browsing to the repository portlet Now it is possible to expand and see descriptors of any package and recursively in any internal package of the repository. Both from the REST and the repository web-portlet. NMI Job Results. Refactoring and cleaning of the NMI scripts done. Different email sent if the job is timeout from NMI. Added registration flag and "To" field on the notification email Added a property in the client to specify the type of job (build/test) and the registration will succeed even in case the reports marks the type as checkout. Build on etics of etics-dissemination-trend-analysis_R_0_1_0 succeded. Rpm and War not yet tested +++ Software Release RC candidate configuration created and now installed on etics1 Run and verified a few gLite tests on etics1 (the Release Candidate). +++ Presentations and Dissemination Presentation of ETICS at the IT Physics group leaders on the 3 July. Built ROOT, the most popular and large Physics Analysis application, with ETICS. In preparation for the presentation mentioned above. Revamped work on the CASTOR2 system, project seems fine, but there are build problems to be discussed with the developers +++ Deliverables Deliverable DSA1.1 completed and released officially in EDMS. QR Report completed and sent to A.Di Meglio for integration. +++ Useful links SA1 Tasks: https://savannah.cern.ch/task/?group=etics2-sa1 ETICS Support list: https://savannah.cern.ch/support/?group=etics
      • SA2 5m
        Support --------------- - No nonsense version for the guidelines on using GGUS for ETICS support ready within today. - Valerio in shift. 5 tickets assigned to Infrastructure, 2 solved, 3 escalated to Experts. Experts solved 1, 2 are pending. Other 6 pending for ETICS Experts. Experts invited to complain when Infrastructure escalates without analysis. - Support portal ready with initial FAQ and articles. Now just a matter of opening the http port on the machine. Elisabetta meeting with Isabel next week to complete the FAQ. Infrastructure Integration Job Submission ------------------------------------------- - Metronome installed at CNAF for implementing the submitter service. New Applications ----------------- - Continued integrating UNICORE, and started thinking about other HPC applications. Evaluation and requirements --------------------------- - Started analyzing first use cases and requirements collected among gLite developers. - Started planning some evaluation of the services. Need to agree on metrics. Various -------- - Beta client testing and feedback collection. Good impressions so far, no bugs, only minor suggestions.
      • JRA1 5m
        Nothing to report
      • JRA2 5m
        The focus was on deliverable DJRA2.1. Now is ready, I have to profread it, write the introduction, conclusion. It required more time than expected. Multinode job submission document read and studied both in 4DSoft and Sztaki. It seems to be in accordance to the agreement on the last meeting. Metrics-GridQCM document upgraded. On Friday Zsolt will send a more finegrained version, based on his recent work. In order to run in ETICS context an etics client installed to lxplus - /tmp/etics4codewizard codewizard rule filtering is under test tested on lxplus using the doc (http://engineering-software.web.cern.ch/engineering-software/Products/Codewizard/attachments/manuals/) A short term solution for GridQCM will be provided. Then a more generic solution as a use case for added commercial test tools in ETICS. Learn, design phase the work with new JRA2 services. Regarding workflow tool investigation of differences between technologies: GridSphere and Google Web Toolkit and installation of neccessary components for experiments (virtual machine, portal, etc.). NA2 task - adding a new project to ETICS Jarta project build and test through ETICS - util4d package upload requested - no response yet - JARTA project build, ant scripts under test , some modification is needed to include in ETICS
    • 16:00 → 16:05
      Deliverables status 5m
      Update on deliverables status for PM3
    • 16:05 → 16:15
      ETICS presentation at PSM 10m
      Discussion of any preparatory work to be done for this presentation
    • 16:15 → 16:25
      ETICS USIS (User Satisfaction Improvement Strategy) 10m
      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