[
https://issues.apache.org/jira/browse/WHIRR-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045055#comment-13045055
]
Chad Metcalf commented on WHIRR-255:
------------------------------------
It sure does. My concern is that abstracting a fully working master is a lot to
bite off. For example we use exported resources very common especially for
Hadoop clusters that would use monitoring (nagios) or security (kerberos). So
now you've got to deploy a database.
I agree 100% that puppet is great for a mechanism that can be used to manage a
cluster not only at deployment but in the future. My point was to build start
even more simple. Have the capability to use masterless or point to a master.
Then once that is working if you've time/use for it tackle building a master
from scratch.
Also from my use case, I've already got a master in ec2 that I can point this
to. The above allows for that as well as building your own.
> 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
