+1 (binding) Thanks Wangda for proposing this. Right now YARN-2928’s proposed UI work is heavily based on YARN-3368. Merging back YARN-3368 to trunk will unblock the future progress of the next gen ATS work.
Meanwhile, the code used in YARN-3368 is completely separated with our existing YARN UIs (the new UI uses ember.js and works with YARN’s REST APIs). This means the new UI can land in trunk as an alpha and safely co-exist with the stable UI. We may potentially attract more contributors to actively working on the new UI after the merge. Li Lu > On Feb 24, 2016, at 17:10, Wangda Tan <[email protected]> wrote: > > YARN Devs, > > We propose to merge YARN-3368 (YARN next generation UI) development branch > into trunk. The reason to do the merge is web UI of Timeline server v2 > (YARN-2928) is depending on the framework, and YARN-2928 is planned to > merge back to trunk shortly. > > Status of YARN-3368: > Now it is runnable from end-to-end, which includes: > * Scheduler page, which contains a select-able queue hierarchy view and > also related scheduler information. > * Apps table, app page, app-attempt page and also timeline view of > app-attempts/containers. > * Cluster overview page, which contains several charts to show overview of > the cluster (such as total memory, total apps, etc.) > > We plan to continue develop this feature after merge back to trunk, please > refer to sub tasks of YARN-3368. > > Since YARN-3368 hasn't integrated to neither Hadoop's maven build system > nor RM web service, so the merge is completely safe. Ticket for the merge > task is: YARN-4734. > > The vote will run for 7 days, ending Wednesday, Mar 2. Please feel free to > comment if you have any questions/doubts. I'll start with my +1 (binding). > > Thanks, > Wangda
