You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Mark Grover (JIRA)" <ji...@apache.org> on 2013/02/05 20:30:13 UTC
[jira] [Commented] (WHIRR-681) enhance puppet service with an
ability to export cluster topology to the puppet code
[ https://issues.apache.org/jira/browse/WHIRR-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571637#comment-13571637 ]
Mark Grover commented on WHIRR-681:
-----------------------------------
A minor question here:
The interface being updated in this patch {{CreateSitePpAndApplyRoles}} is a public one. While I do see all references in Whirr code itself have been updated to match up with the new signature of the constructor, my question is should we create a new constructor instead of modifying the existing one to maintain compatibility with any existing 3rd party code outside of Whirr codebase that might be using it?
> enhance puppet service with an ability to export cluster topology to the puppet code
> ------------------------------------------------------------------------------------
>
> Key: WHIRR-681
> URL: https://issues.apache.org/jira/browse/WHIRR-681
> Project: Whirr
> Issue Type: Improvement
> Components: service/puppet
> Affects Versions: 0.8.1
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Attachments: WHIRR-681-2.patch.txt, WHIRR-681.patch.txt
>
>
> I would like to propose that we enhance puppet service (btw, there seems to be no service/puppet in the components list) by implement the capability that exports the cluster topology via extlookup queryable manifest that gets added to all the nodes same way site.pp does.
--
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