[
https://issues.apache.org/jira/browse/BIGTOP-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036440#comment-14036440
]
Nate DAmico commented on BIGTOP-1047:
-------------------------------------
Looks like this issue is most up to date with 3.x dev efforts
In discussing with [~rvs] our org can take on the lead going forward with
puppet updating. We have been using parts of the bigtop modules for sometime
in our service engagements and have begun to productize around it.
We probably want to create some sub-tasks to incrementally start getting things
in check. First would be picking initial service to upgrade and harmonize
design patter for 3.x as a couple approaches. Combined with this would be for
group to decide on the "canonical" configuration parameters and defaults to be
shipped with.
>From there we can use as initial as template and roll through the other
>services. We will also aim to get some latest efforts we have underway with
>Accumulo and Spark/Shark
> Support Puppet 3.x
> ------------------
>
> Key: BIGTOP-1047
> URL: https://issues.apache.org/jira/browse/BIGTOP-1047
> Project: Bigtop
> Issue Type: Improvement
> Components: Deployment
> Affects Versions: 0.6.0
> Reporter: Andrey Klochkov
> Attachments: BIGTOP-1047--n2.patch, BIGTOP-1047.patch
>
>
> Currently bigtop-deploy/puppet module supports Puppet 2.x only. In
> particular, this is because of using dynamic scoping which was deprecated
> since 2.5 and not supported in 3.x. This task is to get rid of dynamic
> scoping to make bigtop-deploy/puppet working with Puppet 3.x.
> More on dynamic scoping in Puppet:
> http://docs.puppetlabs.com/guides/scope_and_puppet.html
--
This message was sent by Atlassian JIRA
(v6.2#6252)
