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 Sat, 17 Sep 2011 00:15:10 GMT

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

Alex Heneveld commented on WHIRR-385:
-------------------------------------

Looks like the puppet nginx wants vhost info from somewhere. The following puppet recipe makes
and serves a simple site:

{noformat}
include nginx

file { '/tmp/www': ensure => directory }
file { '/tmp/www/mysite': ensure => directory }
file {'/tmp/www/mysite/index.html':
  ensure => present,
  content => "<i>hello world<i>",
}

nginx::resource::vhost { 'mysite': www_root => '/tmp/www/mysite' }
{noformat}

Deploying a {{puppet:nginx}} role isn't very useful it seems. We want to write our own module,
say {{mysite}} with the above in the {{mysite/manifests/init.pp}} (or getting a more interesting
site from somewhere...); then we can ask whirr for a {{puppet:mysite}} role (remembering to
set the {{module-dir}} for stdlib, nginx, and mysite).

Is this a more realistic scenario?


> 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