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

caijialiang commented on AMBARI-25951:
--------------------------------------

I have a few ideas, but I'm unsure whether they should be included in version 
3.3. Perhaps we could initiate a separate discussion.

Regarding the issue of decoupling the stack:

I believe decoupling the stack from Ambari and releasing it independently is a 
sound idea, offering the following advantages:

1. Decoupling Ambari and stack releases allows for more flexible versioning of 
the stack, which can be released as an mpack.
   
2. This would significantly enhance development and debugging processes, as 
well as allow users to customize actions like adding new components or 
upgrading component versions. Often, Ambari releases involve minimal changes 
while most modifications occur in the stack. During the development and 
debugging of the stack, any changes require recompiling Ambari and reinstalling 
the cluster, which can be quite cumbersome. If we separate the stack and 
provide an mpack installation option within Ambari, both the installation and 
debugging of the stack, as well as user-initiated stack updates, would become 
much simpler. I've observed many people struggling with the need to recompile 
and reinstall Ambari for stack updates.

3. In fact, Bigtop already supports packaging the stack into mpacks, offering 
convenience. Going forward, by incorporating the features of mpack v2, we could 
entirely manage the stack using REST APIs. We could even consider creating a 
stack service plugin library.

These are my thoughts on addressing the stack decoupling matter. It might be 
worth initiating a discussion to delve further into this topic.

> Support Bigtop stack 3.3.0
> --------------------------
>
>                 Key: AMBARI-25951
>                 URL: https://issues.apache.org/jira/browse/AMBARI-25951
>             Project: Ambari
>          Issue Type: Task
>            Reporter: Lei Yao
>            Priority: Major
>             Fix For: 2.9.0
>
>
> Since Apache Bigtop prepare for releasing 3.3.0 ,  Bigtop stack 3.3.0  should 
> be supported



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to