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] [Updated] (WHIRR-385) Implement support for using nodeless, masterless Puppet to provision and run scripts
Date Thu, 15 Sep 2011 23:48:09 GMT

     [ 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

Thanks. Attached is a mostly-working rough cut.  The patch supports the syntax discussed above,
it installs puppet, grabs module code from git as per config, and applies a call to the manifest
class with the attributes set from config.  It has an integration test for nginx showing how
things work. However--

* Suspect we do need module paths for this to be useful, or some magic dependency resolution.
 nginx depends on the stdlib module (which I cheated on and make installed as part of {{install_puppet.sh}}
but that's not a scalable solution).  Is this a priority?
* nginx looks like it isn't happy on the AWS linux boxes.  I hit the following error which
I think isn't to do with this issue but might be to do with nginx.  Or maybe nginx is just
a bad candidate for AWS.  The error is:  err: /Stage[main]/Nginx::Service/Exec[rebuild-nginx-vhosts]:
Failed to call refresh: /bin/cat /tmp/nginx.d/* > /etc/nginx/conf.d/vhost_autogen.conf
returned 1 instead of one of [0] at /etc/puppet/modules/nginx/manifests/service.pp:21

I'll maybe try ntp instead.  Apart from the above, next steps are:

* transferring local directories for the modulepath (in addition to git)
* creating and running a single {{site.pp}} for all subroles (instead of single apply for
each subrole; this requires detecting when we've done all the subroles which is a bit fun..)

Re vbox -- don't think it's available quite yet, but possibly a BYON config is more efficient.
 i'm just using AWS which is okay; not great, but a lot faster since switching to your install_puppet
script with the {{--no-rdoc --no-ri}}  J


> 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
>
>   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