You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Olaf Flebbe (JIRA)" <ji...@apache.org> on 2017/04/22 16:25:04 UTC
[jira] [Commented] (BIGTOP-2746) Migrate to Puppet 4
[ https://issues.apache.org/jira/browse/BIGTOP-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980012#comment-15980012 ]
Olaf Flebbe commented on BIGTOP-2746:
-------------------------------------
Since we use puppet from the distros I do care of EOL of a distro, but not that much about EOL at puppetlabs.
In order to get a reasonable datapoint, I just converted a docker instance to puppet 4 and tested whether the toolchain works:
I will push the effort in a branch. To make the story short: Many changes for no extra gain.
The infrastructure changes are large (new puppet root in /opt/puppetlabs, puppet package is gone, has to use puppet-agent), we are now depend on a thirdparty product not contained in a distribution. And I see no extra gains, for now.
I am +1 for having our puppet code future proof, so it is ok to have it puppet4 compatible, but I am -1 for switching to puppetlabs distro, for now, unless we get some benefits.
I found one glitch, which should have been detected earlier before. Will open a JIRA shortly to fix that.
> Migrate to Puppet 4
> -------------------
>
> Key: BIGTOP-2746
> URL: https://issues.apache.org/jira/browse/BIGTOP-2746
> Project: Bigtop
> Issue Type: Improvement
> Components: deployment
> Affects Versions: 1.2.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 1.3.0
>
>
> Puppet 3.x is EOL starting 2017. We need to make sure next release of Bigtop runs on Puppet 4.x
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)