[
https://issues.apache.org/jira/browse/WHIRR-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045041#comment-13045041
]
Chad Metcalf commented on WHIRR-255:
------------------------------------
I might suggest you follow a slightly different model. Take vagrant for
example. There are two routes to configure a box with puppet on vagrant:
Standalone, via puppet apply. Set a manifest/modules path and viola masterless
install. http://vagrantup.com/docs/provisioners/puppet.html
Server, via puppet agent. Set a puppet server and point the node to it.
Standard puppet rules apply.
http://vagrantup.com/docs/provisioners/puppet_server.html
If you need the functionality associated with a full puppet master you'll
likely want more control over its configuration then you're going to want to
encode in a template. thin configs/pluginsync/stored config db/etc. If you
don't need that level of functionality, masterless would be easier.
> Add support for Puppet
> ----------------------
>
> Key: WHIRR-255
> URL: https://issues.apache.org/jira/browse/WHIRR-255
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.3.0
> Reporter: Lars George
> Assignee: Andrei Savu
> Attachments: WHIRR-255+311.patch, WHIRR-255+311.patch,
> WHIRR-255.patch, WHIRR-255.patch, WHIRR-255.patch, WHIRR-255.patch
>
>
> Along the lines of WHIRR-49, implement support for Puppet to bootstrap
> servers.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
