Thank You Wangda for driving the proposal.
I had taken the branch code and applied against trunk. Also verified basic
operations in all pages. Looks fine to me for now.
I am fine in merging the new UI base to trunk.
On Sat, Sep 10, 2016 at 4:25 AM Wangda Tan <wheele...@gmail.com> wrote:
> YARN devs,
> We propose to merge YARN-3368 (YARN next generation web UI) development
> branch into trunk for better development, would like to hear your thoughts
> before sending out vote mail.
> The new UI will co-exist with the old YARN UI, by default it is disabled.
> Please refer to User documentation of the new YARN UI
> for more details.
> In addition, There’re two working-in-progress features need the new UI to
> be merged to trunk for further development.
> 1) UI of YARN Timeline Server v2 (YARN-2928)
> 2) UI of YARN ResourceManager Federation (YARN-2915).
> *Status of YARN next gen web UI*
> Compeleted features
> - Cluster Overview Page
> - Scheduler page
> - Applications / Application / Application-attempts pages
> - Nodes / Node page
> Integration to YARN
> - Hosts new web UI in RM
> - Integrates to maven build / package
> - Added dependencies to LICENSE.txt/NOTICE.txt
> - Documentated how to use it. (In
> Major items will finish on trunk:
> - Security support
> - RM HA support
> We have run the new UI in our internal cluster for more than 2 months, lots
> of people have tried the new UI and gave lots of valuable feedbacks and
> reported suggestions / issues to us. We fixed many of them so now we
> believe it is more ready for wider folks to try.
> Merge JIRA for Jenkins is: https://issues.apache.org/jira/browse/YARN-4734
> The latest Jenkins run
> gave +1.
> Please share your thoughts about this.