[ 
https://issues.apache.org/jira/browse/BIGTOP-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14300287#comment-14300287
 ] 

Evans Ye commented on BIGTOP-1634:
----------------------------------

Hey [~michaelweiser] I got your point now. So topology settings and journal 
based HA should be the next steps after we get this in, correct? For the 
journalnode storage logic, I think its better to configure a different 
directory, but we can address this when we're actually implementing the 
journalnode logic.
Thanks for fixing the tachyon deployment, let me deploy *all* components on my 
side and see what's going on for others you mentioned.
I've applied your patch and now I can successfully deploy a cluster of hadoop 
and yarn. It seems we're getting close to the commit! Now, trys to enable 
kerberos. Will let you know the result:)




> 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)

Reply via email to