SL(C)3 is the reference platform for gLite 3.0, SL(C)4 is the reference
platform for gLite 3.1.
The 'glite people' are not waiting until everything is ready - services
are being released as they become available. Currently the WN, UI and
glite-FTM are in production. The BDII and lcg-CE are in PPS. DPM/LFC is
about to enter certification. There is a summary here;
https://twiki.cern.ch/twiki/bin/view/EGEE/Glite31NodeTracker
Oliver Keeble Information Technology Department
[log in to unmask] CERN
+41 22 76 72360 CH-1211 Geneva 23
Ilja Livenson wrote:
> A small side note - SLC3 is still a reference platform for glite3,
> right? And not SL3. So I'm just curios as to when (if) to expect some
> official announcement from the glite people that now everything works on
> slc4 (really, migrating from one old distro to another is at least a
> questionable solution).
>
> atb,
> Ilja
>
> David Groep wrote:
>> Kyriakos Ginis wrote:
>>
>>> On Thu, Nov 01, 2007 at 12:59:13PM +0100, Andreas Haupt wrote:
>>>
>>>> that's not true. Plain SL3 is entering the "legacy mode" on 1st of
>>>> December. After that only the version 3.0.9 is provided with
>>>> security updates. But there *is* a maintained SL until October 2010:
>>>>
>>>> https://www.scientificlinux.org/distributions/
>>>>
>>> And here is the announcement from the developers:
>>>
>>> http://listserv.fnal.gov/scripts/wa.exe?A2=ind0710&L=scientific-linux-announce&T=0&P=458
>>>
>>>
>>>
>>>
>>
>> Good to hear that the support will remain for SL as well. But the
>> announcement (also on the web site) could be interpreted in a
>> different way -- which is just what I accidentally did:
>>
>>
>>> Two things will happen in the transition phase.
>>>
>>> * December 1, 2007
>>> A new yum-conf for S.L. 301, 302, 303, 304, 305, 307, and 308. This new
>>> yum-conf will change both your cron.yum and your /etc/yum.conf. It
>>> will not
>>> change your release to become SL 309, but it will change the security
>>> update
>>> (errata) section to point to SL 309's security update area. This will
>>> allow
>>> you to continue to get security updates as you transition to SL 3.0.9.
>>> * mid February 2008
>>> S.L. 301, 302, 303, 304, 305, 307, and 308 will be moved into
>>> scientific/obsolete. From experience, we know that users and admins will
>>> continue to use SL 3 until we remove them. We also know, that for one
>>> reason
>>> or another, a user will need one file or another from an old release.
>>> Our
>>> solution for both problems is to move the old releases into a directory
>>> called obsolete. We currently do not know how long we will keep the
>>> releases
>>> in there before removing them.
>>>
>>
>> So after Mid-February 2008, anything can happen. In particular, SL
>> 3.0.9 can
>> continue to have updates built for it, that are just not published in the
>> repository ;-)
>>
>> "We currently do not know how long we will keep the releases in there
>> before removing them"
>>
>> So the info at https://www.scientificlinux.org/news/sl3.legacy is
>> confusing
>> at least ...
>>
>> Cheers,
>> DavidG.
>>
>>
>>
>>
>>
|