[
https://issues.apache.org/jira/browse/BIGTOP-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Slawski updated BIGTOP-1689:
----------------------------------
Description:
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.
was:
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 template is
created.
> puppet: Allow merging abritary configuration in site.xml files
> --------------------------------------------------------------
>
> Key: BIGTOP-1689
> URL: https://issues.apache.org/jira/browse/BIGTOP-1689
> Project: Bigtop
> Issue Type: Improvement
> Components: deployment
> Reporter: Peter Slawski
>
> 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)
