You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Kengo Seki (JIRA)" <ji...@apache.org> on 2017/06/08 08:56:20 UTC

[jira] [Commented] (BIGTOP-1407) create Bigtop stack definition for Ambari

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

Kengo Seki commented on BIGTOP-1407:
------------------------------------

[~rvs], I'm interested in this issue. I'd like to create a "Bigtop 1.2" (or 1.2.1?) stack definition based on your ODPi work. May I take this over?

In addition, I have a question and want some advice:

* What does "a Puppet-driven stack definition" you mentioned above mean?
* I'd rather contribute it as a part of bigtop (just like juju) than ambari. Because the former looks more controllable for us on merging patches, release timing, etc. I'm planning to put the files into mpack as you did on AMBARI-19429, so it isn't necessarily to be included in ambari release. Is this OK, or should I upgrade the bigtop 0.8 stack definition in ambari's source tree?

> create Bigtop stack definition for Ambari
> -----------------------------------------
>
>                 Key: BIGTOP-1407
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1407
>             Project: Bigtop
>          Issue Type: Sub-task
>          Components: deployment
>    Affects Versions: 0.9.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 1.3.0
>
>
> Since Bigtop 0.8.0 is getting to being done we can target that well crafted stack as the first attempt to provide a stack definition for the upcoming Ambari integration work.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)