You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@whirr.apache.org by "Karel Vervaeke (Updated) (JIRA)" <ji...@apache.org> on 2012/03/26 12:07:25 UTC

[jira] [Updated] (WHIRR-370) Templating for configuration files

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

Karel Vervaeke updated WHIRR-370:
---------------------------------

    Attachment: WHIRR-370.patch

Patch introduces velocity, exposed via ClusterActionEvent.getTemplateEngine().

The patch also fixes WHIRR-561 (ganglia configuration).

The user can use custom templates by putting the template in the classpath (e.g. $WHIRR_HOME/conf) and adding a pointer in the recipe (e.g. hadoop-metrics.template=my-custom-hadoop-metrics.properties.vm

Notes / possible improvements:
- whirr-hadoop now has a test dependency on whirr-ganglia (which is kinda ugly)
- support adding templates via non-classpath locations (generally, support changing the velocity engine configuration, which should be easy since it's configured via a property object).
- support multiple template engines via plugin mechanism? (meh)

                
> Templating for configuration files
> ----------------------------------
>
>                 Key: WHIRR-370
>                 URL: https://issues.apache.org/jira/browse/WHIRR-370
>             Project: Whirr
>          Issue Type: Improvement
>          Components: core
>            Reporter: Tom White
>             Fix For: 0.9.0
>
>         Attachments: WHIRR-370.patch
>
>
> Service configuration is currently done via the Whirr properties file by using a special per-service prefix (e.g. 'hadoop-common'). Using a templating approach (using e.g. Velocity) would make changing properties more familiar to users, and would make it easier for service implementors (since they wouldn't need to implement a generator class for each configuration file).
> It might even be possible to support the old syntax (so users can still configure everything from one file if they wished) by, e.g., appending all properties starting 'hadoop-common' to the core-site.xml template, etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira