You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "jay vyas (JIRA)" <ji...@apache.org> on 2014/07/04 19:45:34 UTC

[jira] [Commented] (BIGTOP-313) Move puppet configuration out of manifest and into extlookup() CSV

    [ https://issues.apache.org/jira/browse/BIGTOP-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052588#comment-14052588 ] 

jay vyas commented on BIGTOP-313:
---------------------------------

Some of the information in this patch needs to be transferred up to BIGTOP-1365, i think....

if somone gets a chance, please clarify for me why the configuration files go in "config/" instead of just {{--confdir}} . 

Seen some other folks who had some struggles getting the right  config option from googling around http://apachebigtop.pbworks.com/w/file/fetch/52304359/Puppet.pdf getting this working. 

> Move puppet configuration out of manifest and into extlookup() CSV
> ------------------------------------------------------------------
>
>                 Key: BIGTOP-313
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-313
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Deployment
>            Reporter: Patrick Taylor Ramsey
>            Assignee: Roman Shaposhnik
>            Priority: Minor
>              Labels: deploy, deployment, puppet
>             Fix For: 0.3.0, 0.4.0
>
>         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 was sent by Atlassian JIRA
(v6.2#6252)