Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Plain View
HDFS >> mail # dev >> Replacing the JSP web UIs to HTML 5 applications


+
Haohui Mai 2013-10-22, 22:59
+
Luke Lu 2013-10-25, 17:02
+
Haohui Mai 2013-10-26, 02:31
+
Colin McCabe 2013-10-28, 18:16
+
Alejandro Abdelnur 2013-10-28, 22:57
+
Haohui Mai 2013-10-28, 23:10
+
Haohui Mai 2013-10-28, 23:06
+
Alejandro Abdelnur 2013-10-28, 23:18
+
Haohui Mai 2013-10-28, 23:58
+
Alejandro Abdelnur 2013-10-29, 00:13
+
Zheng, Kai 2013-10-29, 12:22
+
Haohui Mai 2013-10-29, 18:28
+
Luke Lu 2013-10-30, 07:34
Copy link to this message
-
Re: Replacing the JSP web UIs to HTML 5 applications
I'm also not convinced that a Javascript-based approach is the way to go.
We shouldn't switch the default UI until (at a minimum) we have the
command-line tools that Colin requested, and even then I'd still want to
retain support for text-based browsers like elinks unless there are
compelling technical reasons not to.

Haohui, I'm sympathetic since you've already done all this work on a
pure-JS version, but it's also true that the existing JSP pages could be
cleaned up to achieve basically the same visual effect while also still
working in text-only browsers.

Thanks,
Andrew
On Wed, Oct 30, 2013 at 12:34 AM, Luke Lu <[EMAIL PROTECTED]> wrote:

> I don't think that we have reached a consensus that the new javascript only
> UI is the right direction to go. Most people considered it "interesting". I
> personally think it's inappropriate for core Hadoop UI, as it increases
> attack surface of the UI and taking away existing mitigation options from
> users unnecessarily. See my latest comments on HDFS-5333 for "concrete"
> examples.
>
> __Luke
>
>
> On Tue, Oct 29, 2013 at 11:28 AM, Haohui Mai <[EMAIL PROTECTED]> wrote:
>
> > I would like to summarize the discussions so far. It seems that we have
> > reached two consensus:
> >
> > 1. The new JavaScript-based UI is the right direction to go.
> > 2. For now we should keep the old JSP pages around for compatibility
> > reasons.
> >
> > There're some debates on the usages of the JMX / JSON APIs, but this is
> > orthogonal to switching the UI, thus I consider it as a technical detail.
> > We can continue the discussions in the public jira.
> >
> > The new UI has already landed in the trunk, based on the consensus it
> seems
> > that we can switch the default UI to the new one shortly. The user can
> > still access the old web UI using the same URLs.
> >
> > The only question remain is that who is going to maintain the old web UI.
> > My answer is that we should leave them as deprecated and focus the effort
> > on the new web UI.
> >
> > Thanks,
> > Haohui
> >
> >
> >
> > On Tue, Oct 29, 2013 at 5:22 AM, Zheng, Kai <[EMAIL PROTECTED]> wrote:
> >
> > > > having /JMX for monitoring integration and a /JSON end point for the
> UI
> > > IMHO, this makes sense, especially for the long term. JMX interface
> > serves
> > > as management console in admin perspective, WebUI serves as end user
> > > interface. Both might share same functionality codes, but that does not
> > > validate we couple them together.
> > >
> > > Thanks & regards,
> > > Kai
> > >
> > > -----Original Message-----
> > > From: Alejandro Abdelnur [mailto:[EMAIL PROTECTED]]
> > > Sent: Tuesday, October 29, 2013 8:14 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: Replacing the JSP web UIs to HTML 5 applications
> > >
> > > Isn't using JMX to expose JSON for the web UI misusing JMX?
> > >
> > > I would think a more appropriate approach would be having /JMX for
> > > monitoring integration and a /JSON end point for the UI data.
> > >
> > > Thanks.
> > >
> > >
> > > On Mon, Oct 28, 2013 at 4:58 PM, Haohui Mai <[EMAIL PROTECTED]>
> > wrote:
> > >
> > > > Alejandro,
> > > >
> > > > If I understand correctly, that is the exact approach that the new
> web
> > > > UI is taking. The new web UI takes the output from JMX and renders
> > > > them as HTML at the client side.
> > > >
> > > > ~Haohui
> > > >
> > > >
> > > > On Mon, Oct 28, 2013 at 4:18 PM, Alejandro Abdelnur <
> [EMAIL PROTECTED]
> > > > >wrote:
> > > >
> > > > > Haohui,
> > > > >
> > > > > If you have NN and DNs producing JSON instead HTML, then you can
> > > > > build JS based web UIs. Take for example Oozie, Oozie produces
> JSON,
> > > > > it has a
> > > > built
> > > > > in JS web ui that consumes JSON and Hue has built an external web
> UI
> > > > > that also consumes JSON. In the case of Hue UI, Oozie didn't have
> to
> > > > > change anything to get that UI and improvements on the Hue UI don't
> > > > > require changes in Oozie unless it is to produce additional
+
Haohui Mai 2013-10-30, 20:14
+
Colin McCabe 2013-11-01, 17:56
+
Haohui Mai 2013-11-02, 03:35
+
Haohui Mai 2013-10-29, 00:48
+
Alejandro Abdelnur 2013-10-29, 01:01
+
Haohui Mai 2013-10-29, 01:09
+
Larry McCay 2013-10-29, 01:12
+
Haohui Mai 2013-10-29, 02:28
+
Larry McCay 2013-10-29, 02:44