[
https://issues.apache.org/jira/browse/WHIRR-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105968#comment-13105968
]
Alex Heneveld commented on WHIRR-385:
-------------------------------------
So you're suggesting install all the modules for which properties are defined
onto every machine, not trying to be more clever about installing just the
necessary modules for the roles (manifests) at particular machines? That sounds
good.
It is easy to support comma-separated syntax -- but I think there is a problem
with it:
{noformat}
puppet:[email protected]/someone/puppet-stdlib.git,[email protected]/someone/puppet-nginx.git
whirr.instance-templates=1 puppet:nginx
{noformat}
Because we don't know which subdir of {{modules}} to put the code in (i.e. how
to know that the {{puppet-stdlib.git}} needs to go in a directory {{stdlib}};
maybe we could to inspect the downloaded code to find that out but seems easier
to disallow comma-separated paths). So I'll go for installing all the modules
defined with {{puppet:*.module-dir}}. If that's too wasteful then let's attack
the multi-entry path problem. IOW:
{noformat}
puppet:[email protected]/someone/puppet-nginx.git
puppet:[email protected]/someone/puppet-stdlib.git
whirr.instance-templates=1 puppet:nginx
{noformat}
(Re nginx, the root cause was a missing {{puppet}} group. Adding {{useradd
puppet}} to the puppet install script makes it all happy.)
> Implement support for using nodeless, masterless Puppet to provision and run
> scripts
> ------------------------------------------------------------------------------------
>
> Key: WHIRR-385
> URL: https://issues.apache.org/jira/browse/WHIRR-385
> Project: Whirr
> Issue Type: New Feature
> Components: new service
> Affects Versions: 0.7.0
> Reporter: Alex Heneveld
> Attachments: WHIRR-385.patch, WHIRR-385.patch, WHIRR-385.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> As a user of Whirr, I'd like to be able to use puppet scripts (manifests,
> modules) from within Whirr to set up machines and clusters, because there are
> a lot of OS-neutral capabilities and a large number of actively maintained
> scripts which I could benefit from.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
