You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2014/11/02 05:24:33 UTC
[jira] [Commented] (BIGTOP-1505) Need a better way to express jdk
package dependency in Puppet recipes
[ https://issues.apache.org/jira/browse/BIGTOP-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14193686#comment-14193686 ]
Roman Shaposhnik commented on BIGTOP-1505:
------------------------------------------
That's actually pretty easy to workaround. All you need to do is:
{noformat}
jdk_package_name,bash
{noformat}
in your config/site.csv
> Need a better way to express jdk package dependency in Puppet recipes
> ---------------------------------------------------------------------
>
> Key: BIGTOP-1505
> URL: https://issues.apache.org/jira/browse/BIGTOP-1505
> Project: Bigtop
> Issue Type: Improvement
> Components: deployment
> Affects Versions: 0.8.0
> Reporter: Konstantin Boudnik
> Fix For: 0.9.0
>
>
> Currently, we have an explicit dependency in Puppet recipes on a jdk package (e.g. hadoop-hdfs-datanode class). However, we might be having an environment where jdk isn't setup from a package - e.g. one can use bigtop_toolchain for that, meaning that JDK will be installed from a tarball.
> In such environment, Puppet will be failing to deploy a cluster. Let's think of a better fix for this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)