1 / 6

The SLC 5.6 upgrade issue

The SLC 5.6 upgrade issue. Helge Meinhard CERN-IT GDB, 09-Feb-2011. What Happened – User P erspective. LHCb (and LCD) use tcmalloc.so glibc dependent May require recompilation when glibc changes Not part of SLC Code run on RHEL/SLC 5.6 without recompiling tcmalloc.so broke

gamma
Télécharger la présentation

The SLC 5.6 upgrade issue

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The SLC 5.6 upgradeissue HelgeMeinhard CERN-IT GDB, 09-Feb-2011

  2. What Happened – User Perspective • LHCb (and LCD) use tcmalloc.so • glibc dependent • May require recompilation when glibc changes • Not part of SLC • Code run on RHEL/SLC 5.6 without recompiling tcmalloc.so broke • Emergency work-around needed checking whether running on 5.5 or 5.6 • (Not using rpaths may have avoided the problem)

  3. What happened – Service Provider Perspective (1) • 5.6 release history: • RedHat released RHEL 5.6 on 13-Jan • CERN released SLC 5.6 on 20-Jan • FNAL released SL 5.6 last week • CERN rolled out SLC 5.6 on desktops and central systems around 28-Jan • Announcement channels: • Desktops: linux-announce@cern.ch, http://cern.ch/linux • Central systems: cern-quattor-announce@cern.ch, motd on lxplus

  4. What happened – Service Provider Perspective (2) • Testing before roll-out: • Test repositories for desktops (about one week) • Central systems: 10% lxplus capacity for about one week

  5. Certification Policy • Major releases (e.g. SLC6): full certification cycle of several months • Minor releases: • Security updates, bug fixes, functionality enhancements • Formal certification not considered necessary so far by Linux certification group

  6. CERN-IT Proposal • Keep process lightweight • No formal certification for minor releases • About one week for testing • Improve communication • Announcement to LHC Architects’ Forum • AF responsible for disseminating the information to experiments

More Related