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
        NA2 weekly report 19th December to 8th January - Dissemination o Website  "download and install" page is now available still working on it for enhancements.  Still working on the testimonials page. o Poster  second version of ETICS 2 poster is available on EDMS (https://edms.cern.ch/document/982022/1) o Maintaining contacts with a new potential ETICS users (Cosmic Blue Team S.p.A.). A meeting with demo will probably be organized for the beginning of February - Deliverables and quartely report o DNA2.3 - Integrated reviews by Eva and received reviewed version from Alberto Aimar. Still integrating Alberto’s reviews. The final document will be ready on the 12th. o QR3 contribution sent on 19th December - Training o Still working on the on-line training modules delayed as other project activities had higher priority. - ETICS mapping on ISO 12207 o Still working on it. Preparing a document to share with project team.
      • SA1 5m
        Releases - Released Client 1.4.0 before holidays: the really fast client. - Preparing for the 2.3.0 release with improvements in the repository - Preparing Client 1.4.1 with bug fixes Infrastructure - Before Xmas major problems with AFS, the service was impacted for 48 hours. Mostly due to problems with the underlying infrastructure but we should have some backup solution maybe. - Investigation of ETICS server/repository performance (AFS client reinstallations, discussions/test with Netops - Cross-site submission is progressing. Deliverables - Reviewed the NA2 GRID-QCM document - Send for review the DSA1.3 ETICS Services SLA document. - Sent quarterly report for Q3. Resources - Oevynd Valen-Sendtad joins SA1 for six months as technical student. Will work on management of the VM images and dinamyc instantiation of VM on the WN. Dissemination - ETICS Presentation at UMM/Cyfronet Krakow - Participation, with Valerio, to the EGI/UMD initiative in Rome
      • SA2 5m
        Support -------- - Uwe in shift. New Applications ------------------ - Unicore had been ported as shown into the ETICS repository - StoRM backend has been ported. It does not use the ETICS package for producing rpms. One of its external packages is gpfs that has not been included yet into the ETICS external project for LICENSE reason. The porting of StoRM frontend is in progress and it will be completed within next week. A meeting with Storm developers is planned for next week on Monday in order to suggest and agree with further changes into Storm components. - VDT no progress Milestones ----------- - Nov 30th List of requirements to SA1 Further delayed. Foreseen Jan 9th. - Nov 30th StoRM Further delayed. Foreseen Jan 14th. - Nov 30th VDT Furter delayed, Foreseen Jan 14th. - Nov 30th ETICS VO created Completed. - Jan 16th Deployment of NMI submitter for testing On track.
      • JRA1 5m
      • JRA2 5m
    • 16:00 → 16:05
      Next All-Hands meeting 5m
      The meeting will take place on Feb 18-20 with the usual format (afternoon, full day, morning). I will prepare a preliminary agenda to be discussed as soon as we come back from holidays. Please send me any ideas and proposals for disscussion, taking into account that we will dedicate most of the time to the review organization
    • 16:05 → 16:20
      Milestones and planning check 15m
      Formal check of agreed milestones and planning
      more information
    • 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