IMO, that will be good option. We can try to release the 2.8.0 first. Can we create one umbrella for planned tasks for branch-3 and Pending jira's for branch-2.8..?
Any other thoughts..? On 18/08/23, 9:18 AM, "Jialiang Cai" <jialiangca...@gmail.com <mailto:jialiangca...@gmail.com>> wrote: Hello Brahma, I agree with your second proposal: First, ambari 2.8 should only contain necessary bug fixes and then proceed with the release. Second, all the functionalities discussed in the previous ambari roadmap should be included in the branch3 beta release, including the significant feature of Python3 support. Could you please confirm if we have reached a consensus regarding the future release of ambari? If we have, please reply, and I will start working on the corresponding tasks. If you have any other better ideas, we can continue the discussion. Thank you. > On Aug 16, 2023, at 23:22, Battula, Brahma Reddy <bbatt...@visa.com.inva > <mailto:bbatt...@visa.com.inva>LID> wrote: > > > Having two stacks(3.2 and 3.3) in release shouldn't lead any confusion I > think, as HDP has so many stack versions in the past. > > Basically there is no 2.8.0 release in artifacts ( as release is cancelled) , > we'll be directly jumping to 2.9 from 2.7 which might lead the confusion in > future. If we think, stack wise one release, we need to release the 2.8.0 > again ( but all the jira's are marked as 2.8.0, so we might need to > selective, while releasing again.) > > And my second thought is, instead of releasing the 2.8 again, can't move to > 3.0 directly (anyway somepoint of time, we need to move to branch-3 from > branch-2.) > > > On 16/08/23, 3:05 PM, "Jialiang Cai" <jialiangca...@gmail.com > <mailto:jialiangca...@gmail.com> <mailto:jialiangca...@gmail.com > <mailto:jialiangca...@gmail.com>>> wrote: > > > Hello Brahma > > > I agree with you with the idea of re-initiating the Ambari 2.8 release, > creating a 2.8 branch, merging bug fixes after testing, and then re-releasing > it. > > > Presently, Ambari 2.8 corresponds to Bigtop 3.2, which has already been > released. Bigtop 3.3 added support for other components, including Ranger, > Knox, Phoenix, and others. > > > Additionally, post 2.8, we have added further components such as Ambari > infra, Ranger, Ambari log search, Phoenix, and Knox - the development for > these integrations is ongoing. > > > If I grasp correctly, you are suggesting to include additions from post 2.8, > corresponding to the Bigtop 3.3 version, in the release of Ambari 2.8, > ultimately meaning Ambari 2.8 will feature two distinct Bigtop stack versions. > > > So, this leads us to discuss the possible Ambari 2.9 release. The purpose of > including all new components from both Bigtop 3.3 and additions made to > Ambari post 2.8 in the Ambari 2.9 release is to avoid causing any confusion > to users about versions and make it clearer. > > > Regarding your comments on branch 3, could you please clarify what specific > tasks or changes you are thinking of implementing within this branch? > Understanding precisely what you're proposing will significantly assist us in > reaching a consensus and executing this plan more effectively. > > > I am looking forward to hearing from you on these thoughts, ensuring that we > provide the most reliable and effective product for our users. > > > Best, Jialiang > > >> On Aug 16, 2023, at 15:36, Battula, Brahma Reddy <bbatt...@visa.com.inva >> <mailto:bbatt...@visa.com.inva> <mailto:bbatt...@visa.com.inva >> <mailto:bbatt...@visa.com.inva>>LID> wrote: >> >> Thanks Jialiang Cai for initiating this discussion. Good to see features >> which you mentioned which are aligned with my initial roadmap discussion. >> >> IMO, we should go with two options. >> >> i) As 2.8 is cancelled , we can re-create the same branch and continue to >> work on the some of the following you mentioned and delivery the release.. >> ii) Create branch-3 (As Some point we need to move) and plan alpha, beta >> releases as there so many major changes are planned. So, that we can plan >> only bugfixes with 2.8...etc >> >> >> Even we need to consider, how ambari metrics releases will be streamlined >> with ambari release. >> >> >> Queries: >> 1) can't we use latest Hadoop version which is Hadoop-3.3.6..? >> 2) what about spark version, any chance to consider 3.4.0.? >> 3) Can we've hbase to 2.5 and zookeeper to 3.8..? >> 4) Can we namenode (RBF)/Yarn federation.? Multiple standby namenodes.? >> 5) Ambari scalability >> 6) Region server grouping for HBase. >> 7) Not urgent : Hive also we might need to revisit, as 4.0.0 beta is >> available.? >> >> >> Regards, >> Brahma >> >> >> >> >> On 16/08/23, 12:36 PM, "Lei Yao" <yao...@apache.org >> <mailto:yao...@apache.org> <mailto:yao...@apache.org >> <mailto:yao...@apache.org>> <mailto:yao...@apache.org >> <mailto:yao...@apache.org> <mailto:yao...@apache.org >> <mailto:yao...@apache.org>>> <mailto:yao...@apache.org >> <mailto:yao...@apache.org> <mailto:yao...@apache.org >> <mailto:yao...@apache.org>> <mailto:yao...@apache.org >> <mailto:yao...@apache.org> <mailto:yao...@apache.org >> <mailto:yao...@apache.org>>>>> wrote: >> >> >> Thanks Jialiang Cai for driving this work. >> I agree on this Ambari 2.9.0 plan. We need more contribution and PMC's >> attention. >> After all, we need to release a stable version based on Bigtop. >> BTW, it will be greatly appreciated if someone could provide some virtual >> machines on cloud. We can use them as a test environment or a public yum >> repository >> >> >> Best Regards. >> Lei Yao >> >> >> On 2023/08/16 05:43:50 Jialiang Cai wrote: >>> Due to the failed release of Ambari 2.8, and the fact that there are indeed >>> many areas in Ambari 2.8 that need to be improved for deployment, we plan >>> to rectify the 2.8 bugs and enhance some features in the 2.9 release. Since >>> no one in the community is currently promoting Ambari 2.9, I'm initiating a >>> discussion on the Ambari 2.9.0 Roadmap. >>> >>> The contributors to Ambari 2.9 are currently very few, only 2-3 people, so >>> we have temporarily set the following features that are under development: >>> >>> 1. Adaption of Hadoop 3.3.5 to the Bigtop stack and integration with Ambari. >>> 2. Support for the merged Ranger 2.4. >>> 3. Integration of the Ambari infrastructure (merged). >>> 4. Upgrading service versions to Bigtop 3.3.0. >>> 5. Support for Phoenix integration both in Ambari and Bigtop. >>> 6. Adding YARN TimelineService V2 and Registry DNS support (currently under >>> review). >>> 7. In-progress efforts to incorporate Logsearch support. >>> 8. Integration of Ambari Infra (merged). >>> 9. Exploring support for openEuler OS with Ambari. >>> 10. Future plans for adding Knox support. >>> 11. Incorporating a YARN view in Ambari Views. >>> 12. Addressing the continuous increase of WebSocket connections in the >>> Ambari web UI. >>> 13. Ongoing discussions about upgrading from Python 2 to Python 3. >>> >>> Our goal is for Ambari 2.9 to be the first stable big data version after >>> HDP becomes proprietary. We also aim to provide users with pre-compiled >>> RPMs and convenient installation methods. >>> >>> Here is the issue for discussion: >>> https://issues.apache.org/jira/browse/AMBARI-25951 >>> <https://issues.apache.org/jira/browse/AMBARI-25951> >>> <https://issues.apache.org/jira/browse/AMBARI-25951> >>> <https://issues.apache.org/jira/browse/AMBARI-25951;> >>> <https://issues.apache.org/jira/browse/AMBARI-25951> >>> <https://issues.apache.org/jira/browse/AMBARI-25951;> >>> <https://issues.apache.org/jira/browse/AMBARI-25951;> >>> <https://issues.apache.org/jira/browse/AMBARI-25951;> >>> <https://issues.apache.org/jira/browse/AMBARI-25951 >>> <https://issues.apache.org/jira/browse/AMBARI-25951> >>> <https://issues.apache.org/jira/browse/AMBARI-25951> >>> <https://issues.apache.org/jira/browse/AMBARI-25951;> >>> <https://issues.apache.org/jira/browse/AMBARI-25951>> >>> <https://issues.apache.org/jira/browse/AMBARI-25951;> >>> <https://issues.apache.org/jira/browse/AMBARI-25951;> >>> <https://issues.apache.org/jira/browse/AMBARI-25951;> >>> >>> We welcome everyone's discussion and opinions on the Ambari 2.9.0 Roadmap. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@ambari.apache.org >>> <mailto:dev-unsubscr...@ambari.apache.org> >>> <mailto:dev-unsubscr...@ambari.apache.org >>> <mailto:dev-unsubscr...@ambari.apache.org>> >>> <mailto:dev-unsubscr...@ambari.apache.org >>> <mailto:dev-unsubscr...@ambari.apache.org> >>> <mailto:dev-unsubscr...@ambari.apache.org >>> <mailto:dev-unsubscr...@ambari.apache.org>>> >>> <mailto:dev-unsubscr...@ambari.apache.org >>> <mailto:dev-unsubscr...@ambari.apache.org> >>> <mailto:dev-unsubscr...@ambari.apache.org >>> <mailto:dev-unsubscr...@ambari.apache.org>> >>> <mailto:dev-unsubscr...@ambari.apache.org >>> <mailto:dev-unsubscr...@ambari.apache.org> >>> <mailto:dev-unsubscr...@ambari.apache.org >>> <mailto:dev-unsubscr...@ambari.apache.org>>>> >>> For additional commands, e-mail: dev-h...@ambari.apache.org >>> <mailto:dev-h...@ambari.apache.org> <mailto:dev-h...@ambari.apache.org >>> <mailto:dev-h...@ambari.apache.org>> <mailto:dev-h...@ambari.apache.org >>> <mailto:dev-h...@ambari.apache.org> <mailto:dev-h...@ambari.apache.org >>> <mailto:dev-h...@ambari.apache.org>>> <mailto:dev-h...@ambari.apache.org >>> <mailto:dev-h...@ambari.apache.org> <mailto:dev-h...@ambari.apache.org >>> <mailto:dev-h...@ambari.apache.org>> <mailto:dev-h...@ambari.apache.org >>> <mailto:dev-h...@ambari.apache.org> <mailto:dev-h...@ambari.apache.org >>> <mailto:dev-h...@ambari.apache.org>>>> >>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@ambari.apache.org >> <mailto:dev-unsubscr...@ambari.apache.org> >> <mailto:dev-unsubscr...@ambari.apache.org >> <mailto:dev-unsubscr...@ambari.apache.org>> >> <mailto:dev-unsubscr...@ambari.apache.org >> <mailto:dev-unsubscr...@ambari.apache.org> >> <mailto:dev-unsubscr...@ambari.apache.org >> <mailto:dev-unsubscr...@ambari.apache.org>>> >> <mailto:dev-unsubscr...@ambari.apache.org >> <mailto:dev-unsubscr...@ambari.apache.org> >> <mailto:dev-unsubscr...@ambari.apache.org >> <mailto:dev-unsubscr...@ambari.apache.org>> >> <mailto:dev-unsubscr...@ambari.apache.org >> <mailto:dev-unsubscr...@ambari.apache.org> >> <mailto:dev-unsubscr...@ambari.apache.org >> <mailto:dev-unsubscr...@ambari.apache.org>>>> >> For additional commands, e-mail: dev-h...@ambari.apache.org >> <mailto:dev-h...@ambari.apache.org> <mailto:dev-h...@ambari.apache.org >> <mailto:dev-h...@ambari.apache.org>> <mailto:dev-h...@ambari.apache.org >> <mailto:dev-h...@ambari.apache.org> <mailto:dev-h...@ambari.apache.org >> <mailto:dev-h...@ambari.apache.org>>> <mailto:dev-h...@ambari.apache.org >> <mailto:dev-h...@ambari.apache.org> <mailto:dev-h...@ambari.apache.org >> <mailto:dev-h...@ambari.apache.org>> <mailto:dev-h...@ambari.apache.org >> <mailto:dev-h...@ambari.apache.org> <mailto:dev-h...@ambari.apache.org >> <mailto:dev-h...@ambari.apache.org>>>> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@ambari.apache.org >> <mailto:dev-unsubscr...@ambari.apache.org> >> <mailto:dev-unsubscr...@ambari.apache.org >> <mailto:dev-unsubscr...@ambari.apache.org>> >> <mailto:dev-unsubscr...@ambari.apache.org >> <mailto:dev-unsubscr...@ambari.apache.org> >> <mailto:dev-unsubscr...@ambari.apache.org >> <mailto:dev-unsubscr...@ambari.apache.org>>> >> For additional commands, e-mail: dev-h...@ambari.apache.org >> <mailto:dev-h...@ambari.apache.org> <mailto:dev-h...@ambari.apache.org >> <mailto:dev-h...@ambari.apache.org>> <mailto:dev-h...@ambari.apache.org >> <mailto:dev-h...@ambari.apache.org> <mailto:dev-h...@ambari.apache.org >> <mailto:dev-h...@ambari.apache.org>>> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@ambari.apache.org > <mailto:dev-unsubscr...@ambari.apache.org> > For additional commands, e-mail: dev-h...@ambari.apache.org > <mailto:dev-h...@ambari.apache.org> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ambari.apache.org <mailto:dev-unsubscr...@ambari.apache.org> For additional commands, e-mail: dev-h...@ambari.apache.org <mailto:dev-h...@ambari.apache.org> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ambari.apache.org For additional commands, e-mail: dev-h...@ambari.apache.org
