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
        - Answers to recommendations will be ready by today EOB … sorry again for the delay! - Performed dissemination activities to ENG R&D and R&I PMs through internal meetings. - Putting together all the info and feedback coming from the exploitation and sustainability session. Next week will start working on the DNA2.6 (resubmission). - QA&TEST the slot for ETICS tutorial was shortened to 45 minutes. - Lorenzo and Marian are giving the BalticGrid training today and tomorrow
      • SA1 5m
        SA1 Weekly Progress Report - 2009.07.02 ++ Releases - The client 1.4.7 RELEASED - Release descriptions are available here: https://twiki.cern.ch/twiki/bin/view/ETICS/SA1ReleasesContents ++ Development - Working on multi-node testing on all aspects involved (WS, repository, clients, etc) - Adapting the Web Applications to support the configuration and launch of multi-node tests. - Checking Firefox 3.5 support. - Integrating new submitter, diff and disseminator in the Web Services. - Dashboard for a User Project is being defined. - Plug-ins integration is progressing but few stil missing to have all the AQCM metrics (next few weeks). - Plugins for Findbugs and JUnit fixed - CKJMPlugin completed and tested - lcov (asked by gLite) started plugin - AQCM plugin wiki page and AQCM report created for a testSubsystem - Submitters integration progressing on the development environment. - Working on bootstrapper on KVM (hope KVM will be available in Bologna). ++ Infrastructure - Stable operations, no relevant news. ++ Planning and Documentation Continuing after the AHM: . Plugins, AQCM reports . Disseminator, Metrics . Submitters . Multi-node-Testing . Dashboard Planning after the AHM is here: https://twiki.cern.ch/twiki/bin/view/ETICS/PlansAHMBudapest - All SA1 info is available (mostly up to date) from here: https://twiki.cern.ch/twiki/bin/view/ETICS/SA1_internal
      • SA2 5m
      • JRA1 5m
      • JRA2 5m
        RA2 - activity report 1. Working on plugins - according to the plan agreed on all-hands meeting 2. Analysing two tools for replacing CodeWizard. The conclusion is that these two tools just provide two required metrics. The other ones relevance should be verified by the consultant. As plugin implementation, it is quite hard and time consuming, requires at least one month or more. See the detailed analysis below. András will participate on today's meeting, he can provide more technical details. Eva will update the current metrics-plugins mapping document and will circulate soon. Cppcheck http://cppcheck.wiki.sourceforge.net/ A tool for static C++ analysis. It is a new tool appeared recently in sourceforge. This program tries to detect bugs that your C/C++ compiler don't see. The goal is no false positives. No xml, html reports. It is easy to use, but the reports should be implemented. It provides just one metric: “No null pointers”. The others are just similar ones and there relevance should be verified by the consultant. Vera++ http://www.inspirel.com/vera/ Vera++ is a programmable tool for verification, analysis and transformation of C++ source code. It is just a framework, not really a tool. Provides quite few default rules. It parses the C++ code and present it in the form of collections of various objects to user provideds scripts that will define the concrete actions to be executed. Practically, the user has to write the rules checks. It is hard to compile and build. It depends on the Boost libraries. Requires tcl scripting language. Additionally, it is quite hard to run. It does not produce reports: xml or html. It is just possible to redirect the output in a text file. It provides just one metric: “Curly Brackets positioning”. The others are just similar ones and there relevance should be verified by the consultant. *Metrics* Filename in lowercase File names should be well-formed (Vera++) No C instruction (in C++ programming) à language dependent C-style pointer cast in cpp file (Cppcheck) Curly Brackets positioning Curly brackets from the same pair should be either in the same line or in the same column (Vera++) Control structures should have complete curly-braced block of code (Vera++) *First character in variables names * No never used variables Check for functions that are never called (Cppcheck) Unused struct member (Cppcheck) Are all variables initialized by the constructors? (Cppcheck) Are there unused private functions (Cppcheck) Too frequent “breaks” use – rule to be defined *No not variables de-allocation* *No null pointers* dereferencing a null pointer (Cppcheck) *Management of one instruction long “if” or one instruction long “cycle” (parenthesis..)*
    • 16:00 → 16:05
      Review recommendations, user satisfaction survey, AOBs 5m
      Discussion on recommendations status 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