Sure, thanks Kengo.

I'll rebase commit history and submit a PR later.


Best Regards,
Zhiguo Wu
---- Replied Message ----
| From | Kengo Seki<[email protected]> |
| Date | 6/1/2024 13:11 |
| To | dev<[email protected]> |
| Subject | Re: [DISCUSS] New subproject: Bigtop Manager |
Just created a new repository for bigtop-manager.
https://github.com/apache/bigtop-manager

Would you try to import the latest codebase, Zhiguo?

Kengo Seki <[email protected]>

On Sat, Jun 1, 2024 at 11:19 AM Kengo Seki <[email protected]> wrote:

Given no explicit objection in around two weeks, let's move things forward.
Since its release cycle is expected to be different with the Bigtop
packages, I'll create a new repo for it and let you know once it's
prepared.

Kengo Seki <[email protected]>

On Fri, May 31, 2024 at 5:22 PM 吴治国 <[email protected]> wrote:

Thanks everyone for your support.

If there are no objections, could we possibly create a repository for 
bigtop-manager? Or is there another process required?

Best Regards,
Zhiguo Wu


---- Replied Message ----
| From | Yuqi Gu<[email protected]> |
| Date | 5/22/2024 17:47 |
| To | <[email protected]> |
| Subject | Re: [DISCUSS] New subproject: Bigtop Manager |
That's awesome!

As Kengo mentioned, there are significant development dependencies and
synchronization barriers between Bigtop and other deployment solutions like
Ambari. It could harm Bigtop's consistency and integrity and reduce our
development efficiency.

Therefore, we have withdrawn support for Ambari and its Management Pack.

I believe Bigtop-manager, a sub-project of Bigtop, could be a viable
alternative. It has the potential to promote Bigtop as the optimal solution
for users in the future.
+1 from my side.

Thanks.

BRs,
Yuqi

吴治国 <[email protected]> 于2024年5月22日周三 16:12写道:

Thanks, Lei, Kengo and Evans.

The lack of user-friendly UI has been a barrier for new and/or light
users considering adopting Bigtop. Ambari might be a solution, but IMO it
has a maintainability problem caused from its legacy architecture and
outdated software stack, and it seems difficult to improve them gradually.
Couldn't agree more.

Just curious do we have demo/slide or other materials at hand can be
share? would love to get more holistic understanding :)
You can follow this README file[1] to set up your local environment.
However, the functionality is currently limited, that's why I hope that
perhaps by promoting it as a subproject of Bigtop, we can attract more
contributors to accelerate its development process.

Best Regards,
Zhiguo Wu

[1]:
https://github.com/kevinw66/bigtop-manager/blob/main/dev-support/README.md



---- Replied Message ----
| From | Kengo Seki<[email protected]> |
| Date | 5/18/2024 11:27 |
| To | <[email protected]> |
| Subject | Re: [DISCUSS] New subproject: Bigtop Manager |
Thank you so much for your proposal, Zhiguo!

The lack of user-friendly UI has been a barrier for new and/or light
users considering adopting Bigtop. Ambari might be a solution, but IMO
it has a maintainability problem caused from its legacy architecture
and outdated software stack, and it seems difficult to improve them
gradually.
Bigtop Manager is created by Zhiguo and his collaborators from scratch
to tackle this problem. In my understanding, it's easier to maintain
since it's built with modern frameworks such as Spring Boot 3 and
Vue.js 3, and supports recent LTS versions of JDK (17 and 21). I also
believe his technical skill and sense of responsibility for
maintaining it, so I'll submit my +1 for accepting it into the Bigtop
codebase, though it may be required to check if its functionality and
quality is enough before including it into our release.

Kengo Seki <[email protected]>

On Fri, May 17, 2024 at 2:32 PM 吴治国 <[email protected]> wrote:

Hello everyone,


Due to the fact that Bigtop's native deployment solution (Puppet script)
is difficult for general users to configure and fully utilize, many of them
install the components manually or use them in combination with other
frameworks. To address this, I have developed a project called Bigtop
Manager, which is inspired by Apache Ambari and Cloudera Manager.

The project's repository is hosted on Github[1] and has been developed for
more than a year, and has also been incubated in OpenEuler community for
about a half year, while this project has not yet met the standards for
production-level use, I believe that promoting it as a subproject of Bigtop
now could bring more benefits to the project and accelerate its development
progress.

I would like to know your opinion about this, thanks.

Best Regards,
Zhiguo Wu

[1]: https://github.com/kevinw66/bigtop-manager

Reply via email to