FWIW, I agree with Brahma, we should focus on releasing 2.7.7 to get the
dev/test efforts rolling first before we shift our attention to "bigdop
only" releases for Ambari. And when the time comes for 2.8.0 (or 3.0.0), we
can discuss more about moving towards "bigtop mpack" based support only.

On Sun, Jun 19, 2022 at 9:21 AM Battula, Brahma Reddy
<[email protected]> wrote:

> IMO, Bigtop mpack will not immediate goal for us at least for 2.7.7, as
> there will be lot work needs to done to support latest stack and existing
> the cluster upgrades.
>
> I am preparing draft road map. Let's see how that can be.
>
>
> On 19/06/22, 9:42 PM, "吴治国" <[email protected]> wrote:
>
>     Hey guys,
>
>     There are some difficulties for users to use Ambari since HDP is
> behind the paywall, I think this is the first problem we have to solve.
>     Because the Bigtop stack is fully tested, and it's also belongs to
> ASF, I think it's an ideal choice.
>
>     Since Ambari 2.7.5 and 2.7.6 have been released, there are limited
> things we can do, so I consider:
>     1、We should help Bigtop community to provide bgtp-ambari-mpack to
> support Ambari 2.7.5 and 2.7.6.
>     2、Start the development of Ambari 2.8.0, in this version, I prefer to
> drop HDP completely and use Bigtop as default.
>
>     Normally, from Bigtop side, a Bigtop version only supports one Ambari
> version, and current bgtp-ambari-mpack is for Ambari 2.7.5, so I think we
> can first consider the combination of Bigtop 3.1.0 + Ambari 2.7.5.
>     Users can download Ambari 2.7.5 from the Bigtop release site by
> setting the OS repository, and install bgtp-ambari-mpack manually.
>
>     Regarding Ambari 2.7.6, we can consider it later.
>     Regarding Ambari 2.8.0, I'm more inclined to support Bigtop 3.1.0
> first.
>     What do you think?
>
>     Best Regards,
>     Zhiguo Wu
>
>     ---------------------------------------------------------------------
>     To unsubscribe, e-mail: [email protected]
>     For additional commands, e-mail: [email protected]
>
>
>

Reply via email to