BE/CO Changes in LS1 to the Software Development Infrastructure and Widely Used Libraries Chris Roderick, Greg Kruk, Katarina Sigerud, Luigi Gallerani, Niall Stapley, Vito Baggiolini, Wojtek Sliwinski, Zereyakob Makonnen on behalf of BE/CO 1

Agenda General BE/CO upgrade strategy for LS1 (Vito, 10') Changes to the development tools and infrastructure – Development tools (Niall, 15') – Development platforms (VPC, cs-ccr-devX) (Luigi 10’) – Ideas for Development outside the TN (Vito 5’) – Linux platforms (consoles, back-end and front-end) (Vito, 5’) Changes to widely used software libraries – Brief introduction (Katarina, 5') – CMW and JAPC (Wojtek, 20') – LSA/InCA (Greg, 10') – Controls Configuration DirService (Zere, 10') – SDDS (Chris, 10') 20-March-2013Vito Baggiolini2

Today Today’s focus is on changes to widely used software libraries where an action is required from the user community 20-March-2013Vito Baggiolini3

General BE/CO Upgrade Strategy for LS1 Vito Baggiolini (CO TEC) 4

LS1 – a time for radical changes LS1 is the time to make radical changes, and we will ;-) – During the last 4 years of Run, we focused on operations – During LS1, we’ll focus on development/renovation/upgrades – We’ll do our best to minimize nuisance to operations, but … We’ll switch from Run mode to LS1 mode at Easter Why do we need to upgrade? – No more commercial support for old HW or SW – Security updates – Follow evolution of hardware (e.g. drivers for new CCC consoles) – New versions with new features – To keep things stable until LS2 How to get our users & developers to upgrade as well? – New features only in new versions (e.g. FESA 3) – Very good support for new solutions, good enough for old ones – No support for obsolete products after official end-of-life dates 520-March-2013Vito Baggiolini

LS1 – a time to clean up LS1 is also a moment to clean up old/unused stuff – Obsolete versions of software (source and binary) – Unused FESA classes, devices, properties – Unused settings, sequences, configurations, data – Unused NFS mounts, symbolic links, environment variables How do we know what can be cleaned-up/removed? – Usage/dependency analysis (LSA settings, Java methods) – Dynamic usage information (CCM, CMW, Logging, log files…) – But we don’t always know! If in doubt, we’ll do the clean up – If it breaks something, we’ll have to see why and fix it – If needed, we can restore removed stuff (with some effort) 620-March-2013Vito Baggiolini

End of LS1 – a time to test We will do Radical changes from bottom to top – New HW, new drivers, new OS, 32/64bit, new FESA, new devices, new CMW, new Java, … Unit tests in the individual development teams Function and Integration Testing in the CO testbed – “Mini-Accelerator in the lab” – Replication of different hardware and software platforms – Covers CO core systems (OS, FESA, timing, CMW, RBAC, …) – Function tests and stress tests Dry LHC-style dry runs remain essential – Driven by OP – CO and all equipment groups participate – To be inserted in the official schedule – Proposal: 2 months, 2 weeks, 2 days before beam 720-March-2013Vito Baggiolini

Marine Pace, IEFC, 8 th Feb 2013 ACET project Acc. Ctrl. Expl. Tools Steen Jensen

Agenda General BE/CO upgrade strategy for LS1 (Vito, 10') Changes to the development tools and infrastructure – Development tools (Niall, 15') – Development platforms (VPC, cs-ccr-devX) (Luigi 10’) – Ideas for Development outside the TN (Vito 5’) – Linux platforms (consoles, back-end and front-end) (Vito, 5’) Changes to widely used software libraries – Brief introduction (Katarina, 5') – CMW and JAPC (Wojtek, 20') – LSA/InCA (Greg, 10') – Controls Configuration DirService (Zere, 10') – SDDS (Chris, 10') 20-March-2013Vito Baggiolini9