Login

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
        A-QCM - organized a workshop with CTI a company which works in the domain of software product quality evaluation and has substantial experience with the ISO/IEC 25000 standards. It will take place on the 13th and 14th April - performed an analysis of competitors for A-QCM it will be finalized in the following weeks. - writing an abstract on A-QCM to submit to QA&TEST. The call for papers and tutorial from the 6th of March was extended to 3rd April. It could be an interesting opportunity to participate to the call for tutorial (4 hours) with a presentation and demo of all ETICS but there is a need for support from SA1. DISSEMINATION - Presented ETICS to CBT on the 10th. The representative of CBT seemed very interested in ETICS features but showed doubts on the access to the system (privacy of code and users with reading access). We proposed an in-house installation as a solution while the ETICS team is working on the privacy, authentication and authorization requirements collected by SA2. The information collected at the workshop will now be reported by the representative of CBT to the production manager and other heads in CBT in order for them to decide towards the use of ETICS or not. - SA1, SA2 and JRA2 teams participated to OGF25/EGEE User Forum. - Tried to send an article on ETICS to Primeur but couldn’t find an active e-mail address. All e-mails send came back to me. - iSGWT received feedback on the article send at the end of February it will be published but no information was given on when it will be published. They will probably contact me next week with more information TRAINING - Preparing training demos SUSTAINABILITY - Performed an analysis of competitors for ETICS the results were added in the deliverable on sustainability. Needs a last check from Alberto DM. DELIVERABLES - DNA2.4, DNA2.5, DNA2.6 sent to reviewers. Received review from Eva for DNA2.4 (training) and Alberto A. for DNA2.6 (sustainability). - Reviewed DSA1.4. - News on DJRA1.3?
      • SA1 5m
        Most of the work is focusing on the review. +++ Deliverables - Deliverable DSA1.4 distributed - Reviewed SA2 and JRA2 deliverables - Deliverable from JRA1 missing +++ Infrastructure - Set-up automated nightly installation of etics-dev/etics-dev-repository for developers +++ Development - WS-I, CCCC and JFindbugs plugins added - Preparing for Release of 2.4.0, in RC installation next week - Studying the requirements from SA2 deliverables (privacy, authorization, etc) - Progressing with the metrics disseminator and the report generator
      • SA2 5m
        Support ------- - Michele/Andras/Andre' in shift. 6 GGUS tickets in, 4 solved, 2 waiting for reply, 2 escalated. New applications ---------------- - Discussed with Alain the possibility to advertise on the classads site the rpm and deb build by ETICS. That configuration is maintained by us and gLite. Shall it be a separate project, not in externals anymore? - Discussed at CNAF with the developer of wms monitor, a tool for monitorin and publising information about WMS's instances. Tehy're interested in using ETICS and we will create the project for them. - Started exploring the possibilities to have the infngrid release (gLite + some software specific to the italian grid infrastructure) build using ETICS. project will be created, and Cristina, that works on that on her other time will work on that. Infrastructure Integration Job Submission ------------------------------------------ - Final missing pieces in the gLite submitter. Persistence have been implemented using hibernate. Currently we are using MySQL, but that could be changed in the final version, as the few tables needed don't fit the bill for a full blown rdbms, and an embedded db as hsqldb could be used. - Some tweaking on the NMI submitter, now ready for the testing. - UNICORE deployment ready at FZJ. Anyway, development won't start before next thursday we need to talk to Andre' about the change made to the code in the meanwhile and we are busy up to Wednesady with the testing meeting we will have with Lorenzo and Andres next week. Deliverables ------------ - DSA2:4 Reviews received, integrating them. Will be ready for tomorrow.
      • JRA1 5m
      • JRA2 5m
        Mainly working on deliverable and documentation of the TestSystem deployment process. The deliverable will be completed today or tomorrow the latest. SZTAKI did fix the multinode deployment test. It is now possible to make difference between node and platforms at GUI level. <<Discussion of demo scenario>> Multinode scenario? Plugin demo connection with A-QCM?
    • 16:00 → 16:05
      Review organization and deliverables 5m
      Checks on the review organization schedule and deliverables status 3 April: Review 2 April: Dressed rehearsal 20 March: Second rehearsal (online) 18 March: All deliverables and project reports must be in the hands of the EC and reviewers 16 March: All deliverables and project reports must be sent out (CD-ROM) 13 March: Revised versions of the presentations to PMB/TC 10 March: All deliverables and reports must be ready for PMB approval 6 March: Deliverables reviewed, back to originators for modifications 2 March: activity quarterly report to project manager (Alberto); all (most) budget and effort data to project admin (Catherine) 27 February: deliverables ready for internal review sent to reviewers 19 February: First rehearsal 13 February: deliverables first draft
    • 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
Powered by Indico v3.3.7-pre