[
https://issues.apache.org/jira/browse/WHIRR-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045064#comment-13045064
]
Andrei Savu commented on WHIRR-255:
-----------------------------------
I understand. I will keep that in mind and rework the patch to match your
requirements.
We could to this in a few steps, probably as multiple JIRAs:
* masterless Puppet deployment (most of the components are already in place)
* dummy Puppet master server (no database, no special configs, version control
support) with Puppet agents executed as needed by running "whirr run-puppet"
(this approach implemented by the current patch)
* only Puppet agents using an external Puppet master - I believe we are going
to need to have a convention in place for setting hostnames. Are IPs good
enough? How should we handle certificates? Auto-signing?
> 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
