Hi Viraj, Thank you for your confirmation. I'm glad to hear that you're on board with the plan.
Hi All, Let's proceed as discussed. Below are the features I have created: https://issues.apache.org/jira/browse/AMBARI-26164 - Web UI technology stack upgrade https://issues.apache.org/jira/browse/AMBARI-26165 - Admin UI technology stack upgrade https://issues.apache.org/jira/browse/AMBARI-26166 - Views UI technology stack upgrade Please start creating the JIRA tickets and associate them with any of the above features. Thanks & Regards, Mohammad Arshad On Sat, Oct 5, 2024 at 9:31 PM Viraj Jasani <[email protected]> wrote: > Sounds good, we can proceed! > Thank you everyone!! > > > On Thu, Oct 3, 2024 at 12:10 AM Mohammad Arshad < > [email protected]> > wrote: > > > Thank you, Viraj, Lucas, and Vanshu, for your responses. > > > > I hope Lucas and Vanshu's inputs have clarified things. > > > > Viraj, are these answers satisfactory for you? > > > > Do you have any additional questions or comments to add? > > > > On Wed, Oct 2, 2024 at 5:48 PM Hassija, Vanshu <[email protected] > > > > wrote: > > > > > Hi, > > > The idea is to serve two different urls for old and new UI. A switch in > > > navbar of the application would enable to switch between these two. > > > Thanks > > > Vanshu Hassija > > > > > > Get Outlook for iOS<https://aka.ms/o0ukef> > > > ________________________________ > > > From: Contact ODP <[email protected]> > > > Sent: Wednesday, October 2, 2024 5:25:01 PM > > > To: [email protected] <[email protected]> > > > Subject: Re: [Discuss] Ambari UI Modernization > > > > > > Hi to all, > > > > > > I think that to provide both option, we can use do it like in Apache > > Ranger > > > or Apache Atlas Web ui with a switch to latest UI under the Admin menu. > > > > > > Regards, > > > > > > Lucas > > > > > > Le mar. 1 oct. 2024 à 22:58, Viraj Jasani <[email protected]> a > écrit : > > > > > > > Thank you for the detailed plan on this. Great initiative indeed! > > > > > > > > > Both the old and new UIs should be accessible to users, allowing > them > > > to > > > > switch between the two. > > > > > > > > Curious about this, how can we provide both options? Do you mean > > separate > > > > urls? > > > > > > > > > The development process should be incremental. > > > > > > > > How about we create a feature branch for this? > > > > > > > > > > > > On Tue, Oct 1, 2024 at 9:45 AM Mohammad Arshad <[email protected]> > > > wrote: > > > > > > > > > Hi All, > > > > > > > > > > I am reaching out to discuss the Ambari UI technology stack > upgrade. > > > > > > > > > > The Ambari UI is currently using outdated versions of Ember js and > > > > Angular > > > > > js, which have multiple security vulnerabilities that cannot be > > fixed. > > > > > We plan to upgrade the Ambari UI technology stack to React js. > > > > > This mainly involves upgrading the Ambari Web UI from Ember js to > > React > > > > js > > > > > and the Ambari Admin UI from Angular js to React js. > > > > > > > > > > We plan to implement the upgrade with the following considerations: > > > > > 1. Both the old and new UIs should be accessible to users, allowing > > > them > > > > to > > > > > switch between the two. The old UI can be phased out once the new > UI > > is > > > > > stable and mature. > > > > > 2. The upgrade should encompass all aspects of the Ambari UI, > > including > > > > > Ambari Admin, Ambari Web, and Ambari Views. > > > > > 3. The development process should be incremental. After each > change, > > > the > > > > > system should remain functional, mainly ensuring that the old UI > > > > > functionality is not disrupted at any time. > > > > > > > > > > As upgrading the UI framework is a significant change, active > > > > participation > > > > > and feedback from all stakeholders are crucial. > > > > > Looking forward to your thoughts and feedback. > > > > > > > > > > > > > > > Thanks & Regards > > > > > Mohammad Arshad > > > > > > > > > > > > > > >
