[jira] [Issue Comment Deleted] (BIGTOP-1689) puppet: Allow merging arbitrary site configuration

["Olaf Flebbe (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BIGTOP-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olaf Flebbe updated BIGTOP-1689:
--------------------------------
    Comment: was deleted

(was: Packaging for RPM is not quite right:

{code}
[olaf@centos7 bigtop]$ sudo rpm -U  `pwd`/output/bigtop-utils/noarch/bigtop-utils-1.1.0-1.el7.centos.noarch.rpm 
ls: cannot access /usr/lib/bigtop-utils/bigtop-configure/bin: No such file or directory
{code}

{code}
[olaf@centos7 bigtop]$ rpm -qpl output/bigtop-utils/noarch/bigtop-utils-1.1.0-1.el7.centos.noarch.rpm 
...
/usr/lib/bigtop-utils/bigtop-configure/bigtop-configure-1.0.0-SNAPSHOT-assembly
/usr/lib/bigtop-utils/bigtop-configure/bigtop-configure-1.0.0-SNAPSHOT-assembly/bin
/usr/lib/bigtop-utils/bigtop-configure/bigtop-configure-1.0.0-SNAPSHOT-assembly/bin/merge-config
/usr/lib/bigtop-utils/bigtop-configure/bigtop-configure-1.0.0-SNAPSHOT-assembly/lib
/usr/lib/bigtop-utils/bigtop-configure/bigtop-configure-1.0.0-SNAPSHOT-assembly/lib/bigtop-configure-1.0.0-SNAPSHOT.jar
/usr/lib/bigtop-utils/bigtop-configure/bigtop-configure-1.0.0-SNAPSHOT-assembly/lib/commons-cli-1.3.1.jar
/usr/lib/bigtop-utils/bigtop-configure/bigtop-configure-1.0.0-SNAPSHOT-assembly/lib/commons-configuration-1.10.jar
...
{code}

shouldn't it be  {{/usr/lib/bigtop-utils/bigtop-configure//usr/lib/bigtop-utils/lib/commons-cli-1.3.1.jar}} ?

Is there a specific reason to use alternatives ? I would suggest to use a simple symbolic link into {{/usr/bin}}
)

> puppet: Allow merging arbitrary site configuration
> --------------------------------------------------
>
>                 Key: BIGTOP-1689
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1689
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: deployment
>    Affects Versions: 0.8.0
>            Reporter: Peter Slawski
>            Assignee: Rob Leidle
>             Fix For: 1.1.0
>
>         Attachments: BIGTOP-1689.1.patch, BIGTOP-1689.2.patch, BIGTOP-1689.3.patch, BIGTOP-1689.4.patch
>
>
> Puppet should be flexible in allowing arbitrary configuration name value pairs to be merged into a given site.xml file that was generated from a template.
> For example, the following could be included in site.yaml which would add a configuration entry for hadoop.tmp.dir in core-site.xml:
> {code}
> hadoop::common_hdfs::hadoop_core_site_overrides:
>   "hadoop.tmp.dir": "/mnt/var/lib/hadoop/tmp"
> {code}
> This could be implemented as a puppet custom-function taking in the output of template:
> {code}
>     file {
>       "/etc/hadoop/conf/core-site.xml":
>         content => merge_site(template('hadoop/core-site.xml'),  $hadoop_core_site_overrides)
>         require => [Package["hadoop"]],
>     }
> {code}
> Perhaps another approach would be to have site.xml templates be created from a single map of name value pairs. The merge would happen before the file content is generated from the template.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)