[
https://issues.apache.org/jira/browse/WHIRR-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Heneveld updated WHIRR-385:
--------------------------------
Attachment: WHIRR-385.patch
Attaching latest patch -- this fixes the remaining issues mentioned above.
Specifically:
* you can specify module-dir as gits, or as tgz files or directories on local
file system (these latter ones are shipped to destinations as blobs)
* all properties {{puppet.*.module-dirs}} are installed on all machines which
have any puppet role, on bootstrap for first such role
* the manifests are collected into a {{site.pp}} which is run as part of the
configure of the last puppet role
(The behaviour of the last two items can be reverted to previous description
with {{runStrategy}} flags in the {{PuppetClusterActionHandler}}.)
> 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,
> 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
