[
https://issues.apache.org/jira/browse/BIGTOP-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307319#comment-14307319
]
Evans Ye commented on BIGTOP-1634:
----------------------------------
{quote}I should be around for triaging fallout of this change for at least the
next six months. I can not, however, promise continued involvement in
Bigtop{quote}
That's fine. I can take the maintainer role of the journalnode stuff once you
complete the work. To me I'd like to avoid half implement feature w/o
explicitly support on it, so if you can get the feature to the finish line,
then I personally would be happy to +1 and commit this.
{quote}It'd basically be a step backwards in terms of elegance and reduction
of complexity{quote}
I see, and I agree with you. I've tried a different array reputation on yamls
for vm and docker provisioner. I think it should work with only slightly
updates. So let's stick to the current approach and I'll fire a jira to update
both provisioners once this is in.
> Puppet class parameter and hiera conversion
> -------------------------------------------
>
> Key: BIGTOP-1634
> URL: https://issues.apache.org/jira/browse/BIGTOP-1634
> Project: Bigtop
> Issue Type: Improvement
> Components: deployment
> Affects Versions: backlog
> Reporter: Michael Weiser
> Labels: patch
> Attachments:
> 0001-BIGTOP-1634-puppet-Replace-extlookup-with-hiera-use-.patch,
> 0001-BIGTOP-1634-puppet-Replace-extlookup-with-hiera-use-.patch,
> 0002-BIGTOP-1634-Add-enhanced-configuration.patch
>
>
> As discussed on the DEV list:
> Update the puppet code to use self-contained, parametrised classes and proper
> scoping. Replace all extlookup calls bei either explicit or automatic hiera
> parameter lookups. Implement HA/non-HA alternative via hiera lookup
> hierarchy. Replace append_each from bigtop_util by suffix from stdlib. Do
> file imports via puppet:/// scheme. Remove bigtop_util because remaining
> function get_settings is not needed any more.
> Additionally: Add additional configuration options for zookeeper and yarn as
> well as a new class for journalnode configuration.
> I've separated it into two patches of ease of review:
> 0001: actual hiera/class conversion
> 0002: functional enhancements including journalnode configuration on top of
> that. Mainly meant as an example for ease of further expansion and
> containment of changes to single modules.
> This JIRA is meant for the stuff contained in 0001, the actual hiera
> conversion. I can resubmit 0002 as a separate JIRA if desired. Also it should
> be possible to backport 0002 to the current puppet code base without much
> fuss.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
