[
https://issues.apache.org/jira/browse/WHIRR-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498547#comment-13498547
]
Roman Shaposhnik commented on WHIRR-676:
----------------------------------------
Steve, I've been thinking about exactly the same thing -- thanks for filing a
JIRA!
In the ideal world, I'd love to combine the configuration management
functionality that Bigtop's puppet code provides within each individual node
with an orchestration capabilities (some of which you've mentioned) of Whirr. I
filed WHIRR-681 to address this.
Once the WHIRR-681 gets fixed, the question then becomes whether using the
Whirr's puppet service working off of the Bigtop's puppet code would be the
best way to accomplish the task of deploying Bigtop in such a way that vendors
then can subclass it and arrive at [TheirDistro]Service.
What do you think?
> Convert CDH services to use Bigtop artifacts
> --------------------------------------------
>
> Key: WHIRR-676
> URL: https://issues.apache.org/jira/browse/WHIRR-676
> Project: Whirr
> Issue Type: Sub-task
> Reporter: Tom White
> Fix For: 0.9.0
>
>
> The CDH services predate Bigtop, but now that it's available we should change
> them to use Bigtop artifacts, and then vendor distributions can extend these
> as needed (and should be hosted outside Apache).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
