CUT-AND-PASTE glitches ( RQF3237689 - GoogleWS )

Wednesday 2 Jul 2025, 10:00 → 12:00 Europe/Zurich

test file

2025-06-25 
OR
 
Participants: Dirk, German, TimB. Aleksandra, Wayne,Ale, Massimo, Xavi, IgnacioR,IgnacioC, Jan, Arne, EricG, Kuba; PaoloTedesco
Jan asked contact for finalising (procedure: need description of scope (1 page) + collection of any existing documents, named contacts (SM+GL). Request & accept estimate, set up "project" structure)
IgnacioR Review of situation of SW and Licenses
Several cases: New request, Delta reqs (increase scope), Regularisation of status quo (got users w/o service)... Deltas are things like: “I need this additional feature”, “I prefer another project because it's simpler (trello)”, …
Unclear what to do (uniform approach)
Sentry.io probably stuck (they not accepting our proposal)
STEPS is the slowest ring in the chain
(not really a) conclusion. STEPS ? Fix a threshold?
For now, why is IT involved in these procurements? For now, it is that at least there is a coherent check on risks.
Trying to define an action: ask STEPS to define the threshold by which IT should consider an evaluation, even if there is low risk and low cost (there could be risks in “confusions”, in exiting, etc)
Who will decide what is above threshold after STEPS decision?
Service management
Check the note (no presentation)
3 post-mortem in the pipeline
Eligibility Framework
Getting momentum (Google Workspace in prod; OpenStack already there for about a month). AFS got a templated integration example
Ale, Karo and Paolo are the contacts (on top of docs)
TEAMS has been integrated (not in the initial (minimal) set of service for the end of the year). Useful also to *discover* possible limitations and fix them upfront
What to do if a service (not foreseen) wants to integrate now? Wait? Focus more on minimal set (rediscuss in September)
For retiree (RETR) the solution seems to use a ‘verified guest account’ (no computing account then required). Not everything finished but on track
Still unclear: still complex. Details on LMS (mandatory courses) and possible difficulties. ADAMS  (accesses) is next steps
Can this be improved via the IT-FHR or other official contacts to be sure they are on board (effort to do the necessary work needed by Elig)
It will be brought to the attention of FHR-IT. Do not forget ITC-RCS requirements in this area (Student of a non-CERN-related uni  contributing to ROOT, for example)
GPU monitoring
Splinter meeting probably needed (be sure Xavi gets what he needs)
Already being scheduled: action or (hopefully) not?
Minutes and Actions
1 action closed. OK all have “comment” access for TD coordination to edit
Reports from meeting
ATS: interest clarify legals for code assistants…
AI consolidation not channeled (multiple actors, disconcerting for mgmt)
New dept head in September: connected to succession planning
AccGPT 2 is ATS only? What is the plan for services in this area? New services should be blessed by ITSC… To be clarified ( Action on Dirk )
Alphabet news: ATS service being considered (useful also for CRMB)
4th of July meeting (deadline for input for risk analysis????) ← missed
Groups
Minutes based. Typically on yellow items only. Only points with discussions reported here
CD: difficult to hire people for projects (nearshoring). A 1-by-1 process was suggested but it is not successful. Try with a company out of the frame contract.
CD: problem (longhorn FS) solved in record time thanks to existing work/trust relations (although maybe the component was not really ripe for prod yet)
CD: Discussion on Harbor for CMS (exploratory). Do we have a general policy here?
EricG: Please recirculate the puppetDB hostgroup (for the GLs)
CS: TN switch preparation for Sept FC
CS: Issue on understanding on the firmware patch (Firewall boxes; problem detected by cernbox)
DA: opensearch cold storage to CephRDB
DA+PW: migrating from grafana openshit to monit
FA: cooling test announcement not 100% correct (some people did not get the message). Test performed, no major issues (but one chiller not restarting automatically found; fixed)
PW: decision not to have WordPress for *personal*. For “persona” Drupal they will be migrated anyway. No new personal WP site (Web Governance decision)
Followup (by WebGov) after PW does some inventory (other web platforms)
SD: follow up of OLA (ARB doc). Agreement to go for OLA within TD (ie not an OLD but actual OLA).
https://it-arb.web.cern.ch/review_table.html#IT-ARB-036
https://it-arb.web.cern.ch/review_table.html#IT-ARB-037