bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shaposhnik (Commented) (JIRA)" <>
Subject [jira] [Commented] (BIGTOP-313) Move puppet configuration out of manifest and into extlookup() CSV
Date Thu, 12 Jan 2012 01:29:40 GMT


Roman Shaposhnik commented on BIGTOP-313:

Patrick, the patch looks great. It cleans up areas that  have been in dire need of a clean
up -- thanks a million for doing this!

> Move puppet configuration out of manifest and into extlookup() CSV
> ------------------------------------------------------------------
>                 Key: BIGTOP-313
>                 URL:
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Deployment
>            Reporter: Patrick Taylor Ramsey
>            Priority: Minor
>              Labels: deploy, deployment, puppet
>         Attachments: patch.txt
> Previously, bigtop-deploy puppet could only be configured by editing puppet manifests,
or through a small number of environment variables that set facter facts.  I've rewritten
cluster.pp to use extlookup to read most configuration options from a site-specific CSV file
with sane defaults for most options (only hadoop_head_node and bigtop_yumrepo_uri are required
to be set).  These changes should make it easier to automate deploying multiple clusters with
different configurations from the same manifests.
> As written, the CSV files must live in $confdir/config/, where $confdir is the puppet
config directory.  This means that if you are manually calling 'puppet agent' on these manifests
(rather than serving them from a puppet master), you are now required to specify --confdir
in addition to --modulepath.
> At some point in the future, may be worth moving to hiera, as yaml is a lot prettier
and more flexible than CSV.  I did this using extlookup so as not to introduce external dependencies
(since extlookup is now in puppet core).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message