ETICS Technical Commitee

Name: ETICS Technical Commitee
Start: 2009-05-28T16:00:00+02:00
End: 2009-05-28T17:00:00+02:00
Location: CERN

Thursday 28 May 2009, 16:00 → 17:00 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

- 16:00 → 16:05
  
  Welcome and headcount 5m
- 16:05 → 16:30
  Status reports 25m
  
  Highlights of the week, 5 minutes for each WP (NA2, SA1, SA2, JRA1, JRA2)
  - NA2 5m
    
    Dissemination and Exploitation • Working on the questions for the ETICS customer satisfaction survey. Having a last exchange of feedback. • Yesterday a feature on ETICS was published on iSGTW newsletter. The original contribution sent in February was updated according to new outcomes of the project • Updated the website added two news one on the Hannover Messe and one on the QA&TEST conference • Contacted by the editor team of ICT Results interested in publishing a feature on ETICS. We forwarded documents giving information on ETICS 2 impact and exploitation possibilities. They will further evaluate the possibility of publishing an article. • Working on a session proposal for EGEE 09 together with OGF Europe • Discussed internally in ENG the integration of A-QCM in Spago4Q and got the internal approval for extra investments in integrating with Spago4Q • Exploring other grant opportunities in areas different from Research Infrastructure (e.g QUalipso and its follow-up) • Internal meetings with ENG marketing experts to discuss ETICS services position in the market in reply to EC recommendations Training • Decided to send a proposal for a training session on ETICS at the next GridKA school will do it by tomorrow A-QCM • Finished document on ISO standardization and sent to the PMB for feedback NA2 QR sent
  - SA1 5m
    
    ++ Releases - Testing 2.4.3, we had to remove the latest client because some plug-ins need to be modified. - Release 2.4.4 will follow quite soon with what was left out of 2.4.3 - Release descriptions are available here: https://twiki.cern.ch/twiki/bin/view/ETICS/SA1ReleasesContents ++ Development - The couple of bugs holding the release of 2.4.3 were solved. We will need RC3 because of a fix added yesterday. - Progress with the integration of the disseminator with the last version of the portal and is nightly installed in the development installation (etics-dev). We are reviewing it. - AQCM Report: We start having examples of the report for comments and generation of very incomplete reports. - Project dashboard: newcomers needs to learn ETICS, GWT, etc still in training phase - Plug-ins integration is progressing but few stil missing to have all the AQCM metrics (next few weeks). - Submitters integration progressing: now is built on the development environment (thanks SA2) and we will do some testing soon. - Writing a "diff" among cofnigurations or same configuration on different platforms. - Working on multi-node testing but is not progressing fast with all other activities ongloing. ++ Infrastructure - Debugging with Uwe installation at VEGA,progress. Visit of Marian last week, successfully set up ETICS. Adding WNs and Solaris support on the WN. - Debugging with UoW the X-site migration. Bug in Condor to be fixed? - Removed virtualised nodes of SL5 x86_64 from pool installing physical node for SL5 x86_64 - Investigating Deb v4 x86_64 problems with builds, contacting UoW/Becky for Condor on Deb4 x86_64 - Had problems with the repository and we reviewed our alarm systems (emails, sms, etc). - SL v5.2 becoming SL5.3 - New platform names proposed https://twiki.cern.ch/twiki/bin/view/ETICS/PlatformNames ++ Planning - Started planning meetings and will involve other activities - General SA1 planning is next (mostly in DSA1.4 already)
  - SA2 5m
    
    Support ------- - Andras, Claudio, Jozsef in shift. 6 tickets, 3 solved (2.5h), 3 escalated (6h). 2 externals processed Requirements ------------ - Aerospace community applications ready to be phased in in the system installed at VEGA Infrastructure Integration Job Submission ------------------------------------------ - Installed the required software on EGEE worked nodes, now some problems installing the client with the python headers - Testing the integration of the gLite and Metronome submitters with Andres from SA1 (gLite submitters work on CNAF resources while sorting out the problmes installing the nodes) - Farm managers at CNAF are installing our production worker nodes - Design for an EC2 externsions on hold due to other commitments Deliverables ------------- - DSA2.5 due PM15. Sent to TC for review, with recommendation to the internal reviewers not to work on section 11, as we are still working on it
  - JRA1 5m
  - JRA2 5m
    
    This week was a bit slow for JRA2, because we were contributing to SA2 (support shift and new contributions to DSA2.5 deliverable was sent following the received comments). Quarterly Report 5 has been completed and already sent. JRA2 development work included integration of the new plugin registration process into the existing one - proposals for seemless integration will be provided as soon as possible. Started to work on multinode process document. The focus now is on the technical details. New version of the output xml will be proposed soon. Also we were doing some maintenance work on plugins.
- 16:30 → 16:35
  
  Review recommendations, user satisfaction survey, next all-hands, AOBs 5m
  
  Discussion on recommendations List of questions (almost) defined Start discussion on AH agenda
- 16:35 → 16:50
  
  Deliverables, milestones and planning check 15m
  
  Formal check of agreed milestones and planning
- 16:50 → 16:55
  
  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:55 → 17:00
  
  AOB 5m

Choose timezone

ETICS Technical Commitee

TBD

CERN