whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chad Metcalf (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=13104668#comment-13104668
] 

Chad Metcalf commented on WHIRR-385:
------------------------------------

If you are building a node definition to apply after all the requested puppet resources have
been identified I'd put it in {{/etc/puppet/manifests/site.pp}}. So to be clear the user specifies:

{code}
puppet:ntp+puppet:postgresql::server
ntp.server=10.1.1.1
postgresql::server.user=foo
puppet:ntp.module-dir=/path/to/ntp.tgz
puppet:postgresql.module-dir=git@github.com/someone/puppet-postgresql.git
{code}

Whirr then copies up the ntp.tgz with whatever pre-existing mechanism and drops it into {{/etc/puppet/modules/ntp}}.
Whirr instantiates a {{Module}} class which does a {{git clone}} of the postgres module and
drops it into {{/etc/puppet/modules/postgres}}.

Whirr then generates the site.pp which is going to look like this:

{code}
node default {
  class { 'ntp':
    server => '10.1.1.1',
  }
  class { 'postgres::server':
    user => 'foo',
  }   
}
{code}

We don't need the switch statement here since the user is specifying everything.

Now that the {{site.pp}} is on local disk, the modules are in the modulepath, and all is right
with the world. The system can {{puppet apply /etc/puppet/manifests/site.pp}} and thats it.


> 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

        

Mime
View raw message