whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Heneveld (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WHIRR-385) Implement support for using nodeless, masterless Puppet to provision and run scripts
Date Wed, 14 Sep 2011 17:05:09 GMT

    [ https://issues.apache.org/jira/browse/WHIRR-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104669#comment-13104669

Alex Heneveld commented on WHIRR-385:

Re (2) I'm cool with skipping the symbolic role names if we don't need to list or set up differently-properties
instances of the same service. They can always be added in without an API change. Relevant
example config then looks like:

ntp::server.ntp_sources="0.pool.ntp.org 1.pool.ntp.org"
whirr.instance-templates=1 puppet:ntp::server+puppet:ntp

I've started looking at supporting the : syntax inside roles; more on this to follow.

Re (3) again I'm all for simplifying so long as result remains useful (and can be extended).
One directory or git, not multiple paths until we need (and we'll deal with the multiple properties
or path-sep char/syntax then).

*roles-based node default switch*: I like this, the more I understand it. Any objections to
going this route? I presume the node def switch statement just lives in {{manifests/site.pp}}.
 I will have a look at how to pass in roles / read them from a file.

If we go this route would it be reasonable to have a single {{puppet.modulepath}} property
from the config?  Or do you need to be able to specify a different path per-module?

> 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


View raw message