Open Stack

Hello Thomas,
Please see below suggestion.

Best regards
________________________________________
From: Tobias Urdin <tobias.urdin at binero.com>
Sent: Wednesday, May 20, 2020 11:18 AM
To: openstack-discuss at lists.openstack.org
Subject: Re: [puppet] Puppet 5 is officially unsupported in Victoria release

Hello,
I'm thinking that we maybe we can compromise on certain points here.

I would say it's pretty certain we would not break any Puppet 5 code in itself in the
Victoria cycle since we are already behind most of the new features anyways.

What if:

* We officially state Puppet 5 is unsupported
* Remove Puppet 5 as supported in metadata.json
* Only run Puppet 6 integration testing for CentOS and Ubuntu

But we:

* Keep a promise to not break Puppet 5 usage in Victoria
* Keep Puppet 5 unit/syntax testing (as well as Puppet 6 of course)
* Debian can run integration testing with Puppet 5 if you fix those up

The benefit here is that we would not expose new consumers to use Puppet 5
but there is also drawbacks in that:

* You cannot use Puppet 5 and do a "puppet module install" since metadata.json
would cause Puppet 5 to not be supported (a note here is that we don't even test
that this is possible with the current state of the modules i.e checking or conflict or faulty dependencies
in the metadata.json files)

Since the only issue here is that downstream Debian wants to use Puppet 5 I think this is a fair
compromise and since you package the Puppet modules in Debian I assume you don't need any
support being stated in metadata.json for Puppet 5 explicitly.

What do you think?

Best regards
Tobias

________________________________________
From: Thomas Goirand <zigo at debian.org>
Sent: Monday, May 11, 2020 5:37 PM
To: openstack-discuss at lists.openstack.org
Subject: Re: [puppet] Puppet 5 is officially unsupported in Victoria release

On 5/11/20 2:03 PM, Takashi Kajinami wrote:
> Hi,
>
>
> IIUC the most important reason behind puppet 5 removal is that puppet 5
> is EOLed soon, this month.
>  https://puppet.com/docs/puppet/latest/about_agent.html
>
> As you know puppet-openstack has some external dependencies, this can
> cause the problem with our support for puppet 5.
> For example if any dependencies remove their compatibility with puppet 5,
> we should pin all of them to keep puppet 5 tests running.
> This is the biggest concern I know about keeping puppet 5 support.
>
> While it makes sense to use puppet 5 for existing stable branches from a
> stable
> management perspective, I don't think it's actually reasonable to extend
> support
> for EOLed stuff in master development with possibly adding pins to old
> modules.
> IMO we can delay the actual removal a bit until puppet 6 gets ready in
> Debian,
> but I'd like to hear some actual plans to have puppet 6 available in Debian
> so that we can expect short gap about puppet 5 eol timing, between
> puppet-openstack
> and puppet itself.
>
> Thank you,
> Takashi

Thank you, a bit more time, is the only thing I was asking for!

About the plan for packaging Puppet 6 in Debian: I don't know yet, as
one will have to do the work, and that's probably going to be me, since
nobody is volunteering... :(

Now, about dependencies: if supporting Puppet 5 gets on the way to use a
newer dependency, then I suppose we can try to manage this when it
happens. Worst case: forget about Puppet 5 if we get into such a bad
situation. Until we're there, let's hope it doesn't happen too soon.

I can tell you when I know more about the amount of work that there is
to do. At the moment, it's still a bit blurry to me.

Cheers,

Thomas Goirand (zigo)