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

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


Copy link to this message
-
Re: Replacing the JSP web UIs to HTML 5 applications
are you planning to expose things like hdfs browsing and nn/dn logs over jmx?

thx

Alejandro
(phone typing)

On Oct 28, 2013, at 17:48, Haohui Mai <[EMAIL PROTECTED]> wrote:

> It seems more appealing to me that the UI should JMX directly, because:
>
> * We're support the JMX in the long term for other management software.
> * The information provided by the JMX API will be mostly identical of the
> JSON API. Today the Web UI covers most of the information provided by JMX.
> The Web UI does some trivial work to extract the information and renders it
> as HTML.
> * We can compatibility and unit tests for free.
>
> I do agree that the JMX APIs are imperfect and they should be revisited in
> the 3.0 timeframe. However, this is orthogonal of the discussions of
> transitioning from JSP-based Web UI to client-side JavaScript Web UI. The
> architecture of the new Web UI allows easy migration to any JSON-based APIs
> whenever they land in the trunk.
>
> Thanks,
> Haohui
>
>
> On Mon, Oct 28, 2013 at 5:13 PM, Alejandro Abdelnur <[EMAIL PROTECTED]>wrote:
>
>> 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 information.
>>>>
>>>> hope this clarifies.
>>>>
>>>> Thx
>>>>
>>>>
>>>> On Mon, Oct 28, 2013 at 4:06 PM, Haohui Mai <[EMAIL PROTECTED]>
>>> wrote:
>>>>
>>>>> Echo my comments on HDFS-5402:
>>>>>
>>>>> bq. If we're going to remove the old web UI, I think the new web UI
>> has
>>>>> to have the same level of unit testing. We shouldn't go backwards in
>>>>> terms of unit testing.
>>>>>
>>>>> I take a look at TestNamenodeJspHelper / TestDatanodeJspHelper /
>>>>> TestClusterJspHelper. It seems to me that we can merge these tests
>> with
>>>> the
>>>>> unit tests on JMX.
>>>>>
>>>>> bq. If we are going to
>>>>> remove this capability, we need to add some other command-line tools
>>>>> to get the same functionality. These tools could use REST if we have
>>>>> that, or JMX, but they need to exist before we can consider removing
>>>>> the old UI.
>>>>>
>>>>> This is a good point. Since all information are available through
>> JMX,
>>>> the
>>>>> easiest way to approach it is to write some scripts using Node.js.
>> The
>>>>> architecture of the new Web UIs is ready for this.
>>>>>
>>>>>
>>>>> On Mon, Oct 28, 2013 at 3:57 PM, Alejandro Abdelnur <
>> [EMAIL PROTECTED]
>>>>>> wrote:
>>>>>
>>>>>> Producing JSON would be great. Agree with Colin that we should
>> leave
>>>> for
>>>>>> now the current JSP based web ui.
>>>>>>
>>>>>> thx
>>>>>>
>>>>>>
>>>>>> On Mon, Oct 28, 2013 at 11:16 AM, Colin McCabe <
>>> [EMAIL PROTECTED]
>>>>>>> wrote:
>>>>>>
>>>>>>> This is a really interesting project, Haohui.  I think it will
>> make
>>>>>>> our web UI much nicer.
>>>>>>>
>>>>>>> I have a few concerns about removing the old web UI, however:
>>>>>>>
>>>>>>> * If we're going to remove the old web UI, I think the new web UI
>>> has
>>>>>>> to have the same level of unit testing.  We shouldn't go