1 / 11

Migration to SL5

Migration to SL5. James N. Bellinger University of Wisconsin at Madison 21 July 2010. Reminder. Support for Scientific Linux 3 ends 1-October No further OS updates of any kind, including security Fermilab will not permit SL3 machines on the network after that date

sharla
Télécharger la présentation

Migration to SL5

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. Migration to SL5 James N. Bellinger University of Wisconsin at Madison 21 July 2010

  2. Reminder Support for Scientific Linux 3 ends 1-October No further OS updates of any kind, including security Fermilab will not permit SL3 machines on the network after that date We will maintain our Level3 support behind a firewall Old-style “setup” system fails on SL5 Therefore we needed a new “setup” system (SRT structure) This implied new releases

  3. New and Old Releases New releases support SL3, SL4, and SL5, and the structure can support future OS releases With old releases we: Build executable on SL3 Run on SL3 or SL4 With new releases we: Build executable on SL3 or SL4 or SL5 Run on the same or a higher version OS (SL3 on SL5 isn’t fully validated, though)

  4. Available Releases (.m) We only had requests to migrate 4 releases 6.1.4 → 6.1.4.m 6.1.4mc → 6.1.4mc.m 6.1.6 → 6.1.6.m 7.0.1 → 7.0.1.m development → development Validated to give same physics results as old releases A few files required header changes to comply with the new compiler Native C++ compiler, native java, native perl

  5. We Will Have to Use the New Releases For almost everybody, if you have a (for example) 6.1.6 working area all you will need to do is: setup 6.1.6.m gmake as usual If you don’t like harmless warnings about version mismatch just edit the .base_release file Run as usual After the 27-August shutdown you will be using the new setup system

  6. At Fermilab: Central systems Deprecated RETIRED lnx4 lnx3 lnx4 lnx3 lnx4 lnx3 SL3 SL5 SL3 SL5 SL3 SL5 lnx2 lnx1 lnx2 lnx1 lnx2 lnx1 SL4 SL4 lnx5 SL5 SL4 lnx5 SL5 SL5 lnx5 SL5 SL5 SL5 cdfsoft cdfsoft cdfsoft SL3 SL3 SL? Several utilities need to migrate off cdfsoft 27-July Keeping options in case of trouble Now 27-August

  7. At Fermilab: cdfgrid Default target OS for CafSubmit becomes SL5 Some cdfgrid stays SL4 as fallback

  8. At Fermilab: Trailer machines O(200) SL4 machines Need to upgrade to SL4.8 (easy) or SL5 O(100) SL3 machines Need to upgrade to SL4.8 or SL5 by 1-Oct Less than 60 days! Issues w/ 32-bit SL5 support University machines: decide which they want to upgrade and which to retire

  9. Remote Sites Remote sites should have their administrator pull whichever new releases they require, in whichever flavors they require Please, update “development lite” regularly! Eg: have crontab with something like 16 04 * * * ${HOME}/execute_rebuild 1> ${HOME}/er.log 2>&1 ./pull_products 6.1.4mc.m same form as before ./pull_cdfsoft2 6.1.4mc.m same form as before And pull the appropriate binaries: ./pull_bins 6.1.4mc.m GCC_4_1 binaries for SL5

  10. Move Before You Have To Misfeatures in remote installations gave them delays in installing new releases http://www-cdf.fnal.gov/htbin/twiki/bin/view/CodeMigrationAnnouncements/ CodeMigrationAnnouncements Twiki page

  11. Thanks for the hard work! Ray Culbertson Lynn Garren Sasha Golossanov Stephan Lammel Marc Mengel Aidan Robson Simona Rolli Rick Snider Rick St.Denis Oksana Tadevosyan Costas Vellidis

More Related