60 likes | 194 Views
Legacy Phase-Out Overall Motivation and Plans . Vito Baggiolini. Background. Over the last years, we have added a lot of new stuff in a rush LS1 is a good occasion to phase-out old stuff Phase-out must be planned early
E N D
Legacy Phase-OutOverall Motivation and Plans Vito Baggiolini
Background • Over the last years, we have added a lot of new stuff in a rush • LS1 is a good occasion to phase-out old stuff • Phase-out must be planned early • Things are connected, phasing out one thing requires phasing out of others • Many responsibles (in and outside of CO) must be involved • Users/clients may have other priorities than CO
How to get it done… • “Obvious” Motivation • HW: no spare parts left • Knowledge is vanishing (experts retiring) • Less diversity = less work • “CO-induced” motivation for clients / users • More functionality, better performance for new solutions • No upgrades for old platforms (e.g. for LynxOS) • Much better user support for new things than for old ones • Examine difficult cases with perseverance • Go into details of each problem with the clients • Follow them up regularly • “Un travail de fourmis”
List of HW legacy to phase out • HP/UX machines (some still for years!) • PC + cPCI CPUs which are not 64-bit capable • CES CPUs (~300 RIO3, ~230 RIO2) • VXI Oasis crates • CAMAC crates • Other non-Wiener VME crates • TG8 cards, … • Remote reset equipment for legacy crates • Terminal servers in IT/CS start points (Thanks Nicolas & Alastair) A C C O R
List of SW legacy to Phase-out • LynxOS, OS9 => rest of this TC • Nodal: a few some users left in BI, BT, and EL • SL-Equip: a few users in BI, EL, PO, RF • Old RPC code (PS/SPS Access systems; RF, …) • GM equipment classes • X/Motif GUIs in many places (AD, Linac, CPS, SPS,…) • Old versions of FESA, IEPLC • Old device classes, devices • Old versions of Java jars • Old data in the DB (Thanks Nicolas, Alastair, Niall, Zory) A C C O R Usage info
Summary • LS1 is an excellent occasion for legacy phase-out • But legacy phase-out is difficult and needs to be prepared • We (CO) all need to send the same message to the clients/users