Open Stack

On 5/8/20 10:24 PM, Jeremy Stanley wrote:
> On 2020-05-08 22:06:14 +0200 (+0200), Thomas Goirand wrote:
>> On 5/8/20 7:58 PM, Jeremy Stanley wrote:
> [...]
>>> whether the Puppet OpenStack team wants the burden of spending a
>>> cycle targeting support for a Puppet version which will be EOL the
>>> month after the release (especially given deployment projects
>>> usually release as much as a month after the coordinated release
>>> already).
>>
>> I don't see how this can be a burden. It's not as if the language
>> changed that much and if there was major incompatibilities.
> [...]
> 
> Well, it does mean keeping those modules working with two major
> versions of Puppet which, speaking from past experience, is not
> easy (and a big part of why we decided to replace all our
> orchestration and configuration management in OpenDev with something
> other than Puppet after the Puppet 3->4->5 transition).

My understanding is that adding compatibility to a new version isn't
easy, but keeping compat backward isn't that hard.

> How much of a strain that is on the Puppet OpenStack team, I can't
> say.

It means at least keeping one CI job running with puppet 5. This could
be the Debian one if I succeed in restoring Debian as a voting set of jobs.

Cheers,

Thomas Goirand (zigo)