Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 07/14/2015 01:46 AM, Perry, Sean wrote:
>> -----Original Message----- From: Doug Hellmann
>> [mailto:doug at doughellmann.com] Sent: Monday, July 13, 2015 3:41
>> PM To: openstack-dev Subject: Re: [openstack-dev] [all] Time to
>> remove Python2.6 jobs from master
>> 
>> Excerpts from Robert Collins's message of 2015-07-14 09:05:43
>> +1200:
>>> On 14 July 2015 at 02:10, Jeremy Stanley <fungi at yuggoth.org>
>>> wrote:
>>>> On 2015-07-13 09:39:36 -0400 (-0400), Doug Hellmann wrote: 
>>>> [...]
>>>>> On the other hand, how much longer will we be supporting
>>>>> Juno? A matter of months, right?
>>>> 
>>>> The reason it's being brought up again at this point is to
>>>> ask whether it's more important that we keep master
>>>> clients/libs working with 2.6 for several more months, or be
>>>> able to push forward with our constraints overhaul between
>>>> now and then. I'll be hard to have the necessary tooling in
>>>> place before the liberty release if we can't actually use it
>>>> before then (since that's roughly when juno EOL is
>>>> scheduled).
>>> 
>>> Additional detail: - generating 2.6 pins for global
>>> requirements requires access to 2.6 where the periodic job runs
>>> *and where devs are generating updates*. - so that means docker
>>> or lxc or something in both the CI system and widely available
>>> for devs.
>>> 
>>> So its a non-trivial impact; we can do it to move things
>>> forward, but it would be a lot cheaper not to.
>> 
>> I don't *want* to keep 2.6 support around, and I do understand
>> that the requirements work will be made easier.  I'm just trying
>> to understand what other impact dropping it will have.
>> 
> 
> It will break RHEL 5 (maybe early 6 too) and older RH systems.
> Ubuntu older than 9 I think (which is beyond unsupported). Not sure
> about other Linux dists.
> 
> Basically if RHEL 5 is no longer a valid target and we are sure all
> of the 6s have updated then let's nuke it from orbit.
> 

I don't believe there was any release of RHEL-OSP that targeted RHEL
5. As for RHEL 6, the last version that got support for it was OSP5
which is based on Icehouse.

Speaking of RDO, there were attempts to get nova pieces of Juno
backported to RHEL 6 (mostly for CERN). Other than that, I don't think
anyone considers to run anything Kilo+ on RHEL 6, and it will probably
fail to work properly since a lot of underlying platform components in
RHEL 6 would be not ready for new features. (RHEL-OSP could
potentially get all the needed pieces in place, but there was a
decision not to go this route and instead require RHEL 7 for anything
Juno+).

Ihar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVpMlOAAoJEC5aWaUY1u57aqMH/jUqVjZeYTFGIG5ncxU62IuU
Jenu/c5GaGiwMdU4dDG4x25hH6NRN3vNmbXE6oF5HrkbCq7oqih7IjoTI/3Wfo6U
Pwk951VU986duN8syxH+dINWZiOrZ8UNDgO2VI3Tn15TUG/S3eZtMTuM9BHoLn2K
cQYlqZrKQnKVK+zNHdZI7X58P728BNeWONUl5ry7mwOZcWDs7PzvsGJ1t8zrDsE4
sGT3QT3x9VCi+tVD17DW7ZuBA+W1oVtNp3RdDkIN5fsaSE0WDZPr9PPW6jIxHNKo
BP+GS7GPvqZEOK2A4I1foZg6tpkDYlxQo1D5Pz7Ep/9LIDahvE5EUQHRQoUPVH8=
=CuFo
-----END PGP SIGNATURE-----