[
https://issues.apache.org/jira/browse/WHIRR-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104139#comment-13104139
]
Adrian Cole commented on WHIRR-385:
-----------------------------------
OK. here's the latest thoughts :)
So, with Chad's patch, we have the right syntax to bootstrap (ex. install
modules) and configure (apply manifests). We'll still need to work out
firewall rules, but this is a great start.
Alex and I deliberated for 90 minutes just now and have an idea of how this
will flow:
- user will specify the module or specific class they want applied, encoded
into the role-name:
ex. puppet:ntp+puppet:postgresql::server
- user can specify properties that correspond to the module source:
ex.
puppet:ntp.module-dir=/path/to
puppet:postgresql.module-dir=/path/to
- user can can specify attribs by prefixing the attribs with the puppet
manifest, where the first part (module or class) is stripped off
ex.
ntp.server=10.1.1.1
postgresql::server.user=foo
create a PuppetClusterActionHandler that does the following:
-- manifests = all services that are prefixed with puppet: and remove the
puppet: prefix
-- modules = unique set of manifests trimming ::.*
-- beforeBootstrap install modules along with puppet + deps
-- beforeConfigure apply manifests w/ attribs parsed from properties prefixed
by manifest name
concerns:
- if a manifest has a dot in it, it breaks syntax for grabbing attribs from
properties
- TODO firewall rules
- TODO service start order
nice to haves:
- way to specify modules can come from classpath, file on disk, http, etc.
- modules stored in source repository so that we can offline test
Thoughts on the approach?
> 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
>
> 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
