Our Puppet modules (http://forge.puppetlabs.com/theforeman) and Foreman
installer all support Puppet 2.7.x currently, but I'd like to propose
dropping 2.7 support and requiring 3.x, from Foreman 1.11.
Modules we depend upon are increasingly dropping tests for 2.7 and
sometimes compatibility. Our tests are currently affected by the
puppetlabs/concat module inadvertently dropping support, so are
considering it ourselves.
New installations on EL6 would then require Puppet Labs repositories for
3.x, and for Debian Wheezy installations to use 3.x from
wheezy-backports or Puppet Labs too. Currently these are optional, but
recommended. Other OSes all have 3.x available.
Does anybody rely on this still and would be overly affected?
This proposal is only for the Foreman installer and modules, not the
smart proxy.
···
--
Dominic Cleal
dominic@cleal.org
FYI, I posted to the users list to collect responses on whether dropping
Puppet 2.7 support from puppet-* is feasible.
This would provide an alternative to fixing the test failures in
puppet-puppet etc. seen under 2.7:
https://travis-ci.org/domcleal/puppet-puppet/jobs/93121732 (due to
https://github.com/puppetlabs/puppetlabs-concat/commit/a7789fa7).
Dom
···
-------- Forwarded Message --------
Subject: [foreman-users] Dropping Puppet 2.7 support from Foreman installer
Date: Thu, 26 Nov 2015 11:50:05 +0000
From: Dominic Cleal
Reply-To: foreman-users@googlegroups.com
To: Foreman users
Our Puppet modules (http://forge.puppetlabs.com/theforeman) and Foreman
installer all support Puppet 2.7.x currently, but I’d like to propose
dropping 2.7 support and requiring 3.x, from Foreman 1.11.
Modules we depend upon are increasingly dropping tests for 2.7 and
sometimes compatibility. Our tests are currently affected by the
puppetlabs/concat module inadvertently dropping support, so are
considering it ourselves.
New installations on EL6 would then require Puppet Labs repositories for
3.x, and for Debian Wheezy installations to use 3.x from
wheezy-backports or Puppet Labs too. Currently these are optional, but
recommended. Other OSes all have 3.x available.
Does anybody rely on this still and would be overly affected?
This proposal is only for the Foreman installer and modules, not the
smart proxy.
–
Dominic Cleal
dominic@cleal.org
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
No replies, so we've gone ahead with this
(https://github.com/theforeman/foreman-installer-modulesync/pull/23).
Puppet 2.7 support will be dropped in the next version of all of our
modules. Current released versions, including the versions in the
Foreman 1.10 installer will still work with 2.7, while 1.11's installer
will not.
···
On 26/11/15 11:50, Dominic Cleal wrote:
> Our Puppet modules (http://forge.puppetlabs.com/theforeman) and Foreman
> installer all support Puppet 2.7.x currently, but I'd like to propose
> dropping 2.7 support and requiring 3.x, from Foreman 1.11.
>
> Modules we depend upon are increasingly dropping tests for 2.7 and
> sometimes compatibility. Our tests are currently affected by the
> puppetlabs/concat module inadvertently dropping support, so are
> considering it ourselves.
>
> New installations on EL6 would then require Puppet Labs repositories for
> 3.x, and for Debian Wheezy installations to use 3.x from
> wheezy-backports or Puppet Labs too. Currently these are optional, but
> recommended. Other OSes all have 3.x available.
>
> Does anybody rely on this still and would be overly affected?
>
> This proposal is only for the Foreman installer and modules, not the
> smart proxy.
–
Dominic Cleal
dominic@cleal.org
As Puppet 4.x is out I suggest that it would be fair to drop Puppet <3.x.
···
On Thursday, November 26, 2015 at 6:50:12 AM UTC-5, Dominic Cleal wrote:
>
> Our Puppet modules (http://forge.puppetlabs.com/theforeman) and Foreman
> installer all support Puppet 2.7.x currently, but I'd like to propose
> dropping 2.7 support and requiring 3.x, from Foreman 1.11.
>
> Modules we depend upon are increasingly dropping tests for 2.7 and
> sometimes compatibility. Our tests are currently affected by the
> puppetlabs/concat module inadvertently dropping support, so are
> considering it ourselves.
>
> New installations on EL6 would then require Puppet Labs repositories for
> 3.x, and for Debian Wheezy installations to use 3.x from
> wheezy-backports or Puppet Labs too. Currently these are optional, but
> recommended. Other OSes all have 3.x available.
>
> Does anybody rely on this still and would be overly affected?
>
> This proposal is only for the Foreman installer and modules, not the
> smart proxy.
>
> --
> Dominic Cleal
> dom...@cleal.org
>
+1 - Jessie, Wheezy-backports and Trusty-backports all have 3.X, as
does EPEL7. Only EPEL6 still ships 2.7, so we'd have to document that,
I guess?
Greg
Re-reading my last post I should have suggested to drop support for Puppet
< 3.x for all aspects of Foreman. Including the smart proxy.
···
On Thursday, December 10, 2015 at 10:36:47 AM UTC-5, Michael Hurn wrote:
>
> As Puppet 4.x is out I suggest that it would be fair to drop Puppet <3.x.
>
> On Thursday, November 26, 2015 at 6:50:12 AM UTC-5, Dominic Cleal wrote:
>>
>> Our Puppet modules (http://forge.puppetlabs.com/theforeman) and Foreman
>> installer all support Puppet 2.7.x currently, but I'd like to propose
>> dropping 2.7 support and requiring 3.x, from Foreman 1.11.
>>
>> Modules we depend upon are increasingly dropping tests for 2.7 and
>> sometimes compatibility. Our tests are currently affected by the
>> puppetlabs/concat module inadvertently dropping support, so are
>> considering it ourselves.
>>
>> New installations on EL6 would then require Puppet Labs repositories for
>> 3.x, and for Debian Wheezy installations to use 3.x from
>> wheezy-backports or Puppet Labs too. Currently these are optional, but
>> recommended. Other OSes all have 3.x available.
>>
>> Does anybody rely on this still and would be overly affected?
>>
>> This proposal is only for the Foreman installer and modules, not the
>> smart proxy.
>>
>> --
>> Dominic Cleal
>> dom...@cleal.org
>>
>
Yes, documentation for EL6 and Wheezy would change to state that the PL
repo or wheezy-backports is required. Currently it's recommended but
optional.
A similar change was made to Precise when we moved to the Brightbox PPA,
it requires 3.x due to some packaging differences (#7227).
···
On 26/11/15 12:00, Greg Sutcliffe wrote:
> +1 - Jessie, Wheezy-backports and Trusty-backports all have 3.X, as
> does EPEL7. Only EPEL6 still ships 2.7, so we'd have to document that,
> I guess?
–
Dominic Cleal
dominic@cleal.org
Yes, that's a valid option now the installer support has been removed.
For the moment it's not causing any maintenance headaches that I'm aware
of, so it may as well stay. If it does start to cause problems then
removing support is certainly likely.
···
On 10/12/15 16:11, Michael Hurn wrote:
> Re-reading my last post I should have suggested to drop support for
> Puppet < 3.x for all aspects of Foreman. Including the smart proxy.
–
Dominic Cleal
dominic@cleal.org
Making a clean break now could save problems in the future. You could state
that it is no longer supported but no issues have been reported with the
older version.
···
On Thu, Dec 10, 2015 at 11:15 AM, Dominic Cleal wrote:
On 10/12/15 16:11, Michael Hurn wrote:
Re-reading my last post I should have suggested to drop support for
Puppet < 3.x for all aspects of Foreman. Including the smart proxy.
Yes, that’s a valid option now the installer support has been removed.
For the moment it’s not causing any maintenance headaches that I’m aware
of, so it may as well stay. If it does start to cause problems then
removing support is certainly likely.
–
Dominic Cleal
dominic@cleal.org
–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/YQNfxUzG_As/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
