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 Sat, 17 Sep 2011 18:47:09 GMT

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

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

Turns out half the problem is I can't remember how to use the module I wrote... Here is a
working properties file:

{code}
# Change the cluster name here
whirr.cluster-name=puppettest

# Change the number of machines in the cluster here
whirr.instance-templates=1 puppet:apache+puppet:ntp
whirr.firewall-rules=80

# For EC2 set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables.
whirr.provider=aws-ec2
whirr.identity=${env:AWS_ACCESS_KEY_ID}
whirr.credential=${env:AWS_SECRET_ACCESS_KEY}

# with puppet, you need to specify where to pull the modules from
puppet.apache.module-dir=git://github.com/metcalfc/puppet-apache.git
puppet.ntp.module-dir=git://github.com/puppetlabs/puppetlabs-ntp.git

# with puppet, you can set class parameters
ntp.servers=[ '0.pool.ntp.org', 'clock.redhat.com' ]
ntp.autoupdate=true

# By default use the user system SSH keys. Override them here.
whirr.private-key-file=${sys:user.home}/.ssh/id_whirr
whirr.public-key-file=${whirr.private-key-file}.pub

# Expert: specify alternate module sources instead of from git
#puppet.nginx.module-dir=/tmp/git-puppetlabs-nginx.tgz
#puppet.nginx.module-dir=/tmp/git-puppetlabs-nginx    
{code}

When I wrote my module I used {{apache}} not {{httpd}}. I've renamed the github repo to reflect
this and updated the above properties file.

Also we found that on Ubuntu during the install you'll need to run {{apt-get update}}.

> 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-results-aws-ec2.txt, WHIRR-385-results-cloudservers-us.txt,
WHIRR-385.patch, WHIRR-385.patch, WHIRR-385.patch, WHIRR-385.patch, 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

        

Mime
View raw message