Hi, Kanak and Kishore

It seems I will not able participant $subject since my enrollment for
college will not vaild to GSOC.
thought inform here.
But I will help on this task.

Thanks


On Tue, Mar 18, 2014 at 12:08 PM, madhuka udantha
<[email protected]>wrote:

>
>
>
> On Tue, Mar 18, 2014 at 11:48 AM, Kanak Biscuitwala 
> <[email protected]>wrote:
>
>> I envision it being a single webapp for both viewing and administration.
>
> great
>
> That webapp could be a single dashboard or multiple.
>
> Yap,  We can have separate dashboard with different views (Personalisation
> modal for views), Or we can have tab concept for it.
>
>
>> Certainly, we want to have both node-local and cluster-global views (and
>> even cross-cluster views). I haven't thought through the user experience
>> enough to give a good answer.
>>
> Firstly we can have mock UI of dashboard, and discuss on those about UI
> experiences.
> We will need list down
>
>    - cluster operations on each view
>    - priorities on each operation on each view
>
>
>
>>
>> Kanak
>>
>> ----------------------------------------
>> > From: [email protected]
>> > Date: Tue, 18 Mar 2014 11:15:04 +0530
>> > Subject: Re: [GSOC 2014] Helix dashboard
>> > To: [email protected]
>> > CC: [email protected]; [email protected]
>> >
>> > Thanks Kanak for quick reply.
>> >
>> >
>> > On Tue, Mar 18, 2014 at 10:54 AM, Kanak Biscuitwala <
>> [email protected]>wrote:
>> >
>> >> I believe the REST API is complete with respect to admin operations. If
>> >> you see discrepancies in either the API or the documentation, we would
>> >> really appreciate it if you created a JIRA ticket so that we can
>> address
>> >> them.
>> >>
>> > Sure Thanks, I will create JIRAs I found the discrepancies
>> > Are we think to have one dashboard for cluster (master states)/ Node
>> wise?
>> >
>> >
>> >> Regarding your other email, we would like to have something with a JVM
>> >> backend in case we need to expose something that requires direct
>> access to
>> >> Helix code or even ZooKeeper.
>> >
>> > JVM backend is important as to access Helix and ZooKeeper
>> >
>> > Pure AJAX-ish dashboards would force exclusive use of the REST/command
>> line
>> >> API,
>> >
>> > Yes,
>> >
>> >
>> > which may not be flexible enough moving forward.
>> >
>> >
>> >> Kanak
>> >>
>> >> ----------------------------------------
>> >>> From: [email protected]
>> >>> Date: Tue, 18 Mar 2014 10:38:32 +0530
>> >>> Subject: Re: [GSOC 2014] Helix dashboard
>> >>> To: [email protected]
>> >>> CC: [email protected]; [email protected]
>> >>>
>> >>> Thanks Kanak,
>> >>>
>> >>> For sharing the link.
>> >>>
>> >>> As cluster management operations of Helix are supported via, Java API,
>> >>> Command Line Interface and REST Interface.
>> >>> Are those API identical? (I found few APIs that are not available via
>> >> REST,
>> >>> or those not documented).
>> >>> I will planing to go through over source code briefly regard those
>> >>> interfaces.
>> >>>
>> >>>
>> >>> On Tue, Mar 18, 2014 at 1:52 AM, Kanak Biscuitwala <
>> [email protected]
>> >>>wrote:
>> >>>
>> >>>>
>> >>>> You can find a reference for the REST API at
>> >>>> http://helix.apache.org/0.6.2-incubating-docs/tutorial_admin.html
>> >>>>
>> >>>> Cool, looks good!
>> >>>>
>> >>>> Kanak
>> >>>>
>> >>>> ----------------------------------------
>> >>>>> From: [email protected]
>> >>>>> Date: Tue, 18 Mar 2014 01:48:34 +0530
>> >>>>> Subject: Re: [GSOC 2014] Helix dashboard
>> >>>>> To: [email protected]
>> >>>>> CC: [email protected]; [email protected]
>> >>>>>
>> >>>>> Hi All,
>> >>>>>
>> >>>>> Is there any REST specification in Helix/[1] ? REST API
>> documentation?
>> >>>>> I was looking some Helix documentation and tutorial. Checking
>> available
>> >>>>> API.
>> >>>>>
>> >>>>> I was looking some dashboard(/open source) to get UI components
>> ideas,
>> >>>>> features, user interaction level.
>> >>>>> dashing[2], jslate[3], stashboard[4], openstack[5] and wso2 UES[6],
>> >>>>> playframework[7] and hawt.io[8].
>> >>>>> Lot of dashboard contains responsive UI and HTML5 capabilities.
>> >>>>>
>> >>>>> Thanks
>> >>>>>
>> >>>>> [1] https://issues.apache.org/jira/browse/HELIX-99
>> >>>>> [2] http://shopify.github.io/dashing/
>> >>>>> [3] http://jslate.com/pages/home
>> >>>>> [4] http://www.stashboard.org/
>> >>>>> [5] https://www.openstack.org/software/openstack-dashboard/
>> >>>>> [6] http://wso2.com/products/user-engagement-server/
>> >>>>> [7] http://www.playframework.com/
>> >>>>> [8] http://hawt.io/
>> >>>>>
>> >>>>>
>> >>>>> On Mon, Mar 17, 2014 at 10:50 AM, kishore g <[email protected]>
>> >> wrote:
>> >>>>>
>> >>>>>> Thanks Madhuka for taking this up. Feel free to use any tool that
>> is
>> >>>>>> compatible to Apache License.
>> >>>>>>
>> >>>>>> thanks,
>> >>>>>> Kishore G
>> >>>>>>
>> >>>>>>
>> >>>>>> On Sun, Mar 16, 2014 at 10:05 PM, madhuka udantha <
>> >>>>>> [email protected]> wrote:
>> >>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> On Mon, Mar 17, 2014 at 3:56 AM, Kanak Biscuitwala <
>> >>>> [email protected]>wrote:
>> >>>>>>>
>> >>>>>>>> Just to be clear, the repository you referred to is out of date.
>> The
>> >>>>>>>> current location is available at
>> >>>> http://helix.apache.org/sources.htmland mirrored by
>> >>>>>>>> https://github.com/apache/helix
>> >>>>>>>
>> >>>>>>> Thanks Kanak,
>> >>>>>>> I was able build it (0.7.1-incubating-SNAPSHOT). I will go on some
>> >>>> source
>> >>>>>>> code in there regard to $subject.
>> >>>>>>>
>> >>>>>>> I am following online Doc[1] to understand rest/ API of helix.
>> >>>>>>> Here are few jira[2,3,4] I was looking to get the idea of rest
>> API.
>> >>>>>>> I believe while we will progressing jira[3] also be able complete
>> >> some
>> >>>>>>> far as it is about rest specification.
>> >>>>>>> Is there any UI level boundaries/limitation for $subject (If
>> licence
>> >> is
>> >>>>>>> fine with Apache We can proceed)?
>> >>>>>>>
>> >>>>>>> [1]
>> >> http://helix.apache.org/0.7.0-incubating-docs/tutorial_admin.html
>> >>>>>>> [2] https://issues.apache.org/jira/browse/HELIX-46 (resolved)
>> >>>>>>> [3] https://issues.apache.org/jira/browse/HELIX-99
>> >>>>>>> [4] https://issues.apache.org/jira/browse/HELIX-46 (resolved)
>> >>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> Thanks for your interest. Please let us know if there is any way
>> we
>> >>>> can
>> >>>>>>>> help.
>> >>>>>>>>
>> >>>>>>>> Kanak
>> >>>>>>>>
>> >>>>>>>> ----------------------------------------
>> >>>>>>>>> From: [email protected]
>> >>>>>>>>> Date: Mon, 17 Mar 2014 02:21:49 +0530
>> >>>>>>>>> Subject: Re: [GSOC 2014] Helix dashboard
>> >>>>>>>>> To: [email protected]
>> >>>>>>>>> CC: [email protected]; [email protected]
>> >>>>>>>>>
>> >>>>>>>>> Hi, Kanak
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> Thanks for replying. I have worked with some clustering[5]/
>> >>>>>>>> dashboard[6]
>> >>>>>>>>> open source work. I went through [2,3] for helix and I am going
>> >>>> through
>> >>>>>>>>> documentation[7]. I will try go over briefly on source[7] and
>> >>>>>>>> wikis/codes
>> >>>>>>>>> on [1,4].
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> Since listed operations are currently available via REST, Java,
>> and
>> >>>>>>>> command
>> >>>>>>>>> line APIs,
>> >>>>>>>>>
>> >>>>>>>>> +1,
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> We can make AJAX/ WS calls from front end (FE) to back end (BE)
>> >> rest
>> >>>>>>>>> services to get data. We can go from grass level even (With
>> >>>>>>>> bootstrap). But
>> >>>>>>>>> Since there few library/project for such thing we can used for
>> it
>> >> as
>> >>>>>>>> email
>> >>>>>>>>> thread has gone.
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> For common administrative operations as been listed. We will
>> need
>> >> UI
>> >>>>>>>> wire
>> >>>>>>>>> frames and mainly for viewing data over dashboard.
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> Thanks
>> >>>>>>>>>
>> >>>>>>>>> Madhuka
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> [1] https://github.com/linkedin/helix
>> >>>>>>>>>
>> >>>>>>>>> [2] https://www.youtube.com/watch?v=s3IsSfwIPB4
>> >>>>>>>>>
>> >>>>>>>>> [3]
>> >>>>>>>>
>> http://www.slideshare.net/amywtang/apache-con-buildingddsusinghelix
>> >>>>>>>>>
>> >>>>>>>>> [4] https://git-wip-us.apache.org/repos/asf/helix.git
>> >>>>>>>>>
>> >>>>>>>>> [5]
>> >>>>>>>>>
>> >>>>>>>>
>> >>>>
>> >>
>> http://madhukaudantha.blogspot.com/2013/12/wso2-application-server-clustering.html?q=cluster
>> >>>>>>>>>
>> >>>>>>>>> [6]
>> >>>>>>>>>
>> >>>>>>>>
>> >>>>
>> >>
>> http://madhukaudantha.blogspot.com/2013/07/creating-dashboard-with-ues.html?q=UES
>> >>>>>>>>>
>> >>>>>>>>> [7] http://helix.apache.org/0.6.2-incubating-docs/index.html
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> On Sun, Mar 16, 2014 at 12:24 AM, Kanak Biscuitwala <
>> >>>>>>>> [email protected]>wrote:
>> >>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> Hi Madhuka,
>> >>>>>>>>>>
>> >>>>>>>>>> The general idea is that right now, Helix uses global stores
>> like
>> >>>>>>>>>> ZooKeeper to manage distributed systems in a high-level way.
>> >>>> However,
>> >>>>>>>> the
>> >>>>>>>>>> only way to view Helix state right now is through viewers of
>> those
>> >>>>>>>> stores
>> >>>>>>>>>> like ZooInspector. This is difficult to understand because all
>> you
>> >>>>>>>> see is
>> >>>>>>>>>> some JSON organized into directories, and it's overall pretty
>> >>>>>>>> independent
>> >>>>>>>>>> of Helix concepts. We'd like a Helix-specific
>> viewer/administrator
>> >>>>>>>>>> dashboard for this reason.
>> >>>>>>>>>>
>> >>>>>>>>>> If you haven't already, I recommend visiting
>> >>>> http://helix.apache.org,
>> >>>>>>>>>> reading up on concepts and tutorials, and perhaps trying a
>> recipe
>> >> or
>> >>>>>>>> two.
>> >>>>>>>>>>
>> >>>>>>>>>> The dashboard should show realtime data, and also support basic
>> >>>>>>>> workflows
>> >>>>>>>>>> for doing common administrative operations:
>> >>>>>>>>>>
>> >>>>>>>>>> 1. Pausing a cluster or resource
>> >>>>>>>>>> 2. Disabling a resource, partition, or participant
>> >>>>>>>>>> 3. Triggering a rebalance
>> >>>>>>>>>> 4. Changing the assignment of partitions to participants
>> >>>>>>>>>> 5. Adding a new resource
>> >>>>>>>>>> 6. Configuring a new participant
>> >>>>>>>>>> 7. Resetting partitions, resources, and participants that are
>> in
>> >>>> error
>> >>>>>>>>>> state
>> >>>>>>>>>> 8. Setting configuration properties
>> >>>>>>>>>>
>> >>>>>>>>>> All of these operations are currently available via REST, Java,
>> >> and
>> >>>>>>>>>> command line APIs, so you can call these internally on the
>> >>>> dashboard.
>> >>>>>>>>>>
>> >>>>>>>>>> As for UI support, that can be up to you. We're all pretty good
>> >>>>>>>> systems
>> >>>>>>>>>> developers, but not necessarily experienced at frontend
>> >> development.
>> >>>>>>>> What I
>> >>>>>>>>>> would like to see is the realtime cluster state, and then what
>> the
>> >>>>>>>> cluster
>> >>>>>>>>>> state will look like if you commit pending changes. Then, once
>> >>>>>>>> committed,
>> >>>>>>>>>> the changes will take place.
>> >>>>>>>>>>
>> >>>>>>>>>> I hope this was helpful. Feel free to respond if you have any
>> >>>>>>>> questions.
>> >>>>>>>>>>
>> >>>>>>>>>> Thanks,
>> >>>>>>>>>> Kanak
>> >>>>>>>>>>
>> >>>>>>>>>> ----------------------------------------
>> >>>>>>>>>>> From: [email protected]
>> >>>>>>>>>>> Date: Sat, 15 Mar 2014 22:09:25 +0530
>> >>>>>>>>>>> Subject: [GSOC 2014] Helix dashboard
>> >>>>>>>>>>> To: [email protected]; [email protected]
>> >>>>>>>>>>> CC: [email protected]
>> >>>>>>>>>>>
>> >>>>>>>>>>> Hi,
>> >>>>>>>>>>>
>> >>>>>>>>>>> While I was going through GSOC project I found[1], I went
>> through
>> >>>>>>>> mail
>> >>>>>>>>>>> thread[2] seems interesting as I was working with some
>> dashboard,
>> >>>>>>>> gadgets
>> >>>>>>>>>>> and OSAPI [4].
>> >>>>>>>>>>>
>> >>>>>>>>>>> I like to know bit more on[1], regard what time of data level
>> are
>> >>>>>>>> planing
>> >>>>>>>>>>> to show in dashboard and to which level of UI support
>> >>>>>>>> (HTML5/dragging-
>> >>>>>>>>>>> drooping/resposive UI)?
>> >>>>>>>>>>>
>> >>>>>>>>>>> Thanks
>> >>>>>>>>>>>
>> >>>>>>>>>>> [1]
>> >> https://issues.apache.org/jira/browse/HELIX-60?filter=12326260
>> >>>>>>>>>>> [2]
>> >>>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>
>> >>>>
>> >>
>> http://mail-archives.apache.org/mod_mbox/incubator-helix-dev/201303.mbox/%3CCABaj-QZPbN8W6WZ1OZNCFk7yCLFPcmiGV5wHdM=dyd0hbtx...@mail.gmail.com%3E
>> >>>>>>>>>>> [3]
>> >>>>>>>>
>> http://www.dzone.com/links/r/wso2_user_engagement_server_ues.html
>> >>>>>>>>>>> [4]
>> >>>>>>>>>>
>> >>>>>>>>
>> >>>>
>> http://madhukaudantha.blogspot.com/search/label/OpenSocial%20container
>> >>>>>>>>>>> --
>> >>>>>>>>>>> Cheers,
>> >>>>>>>>>>> Madhuka
>> >>>>>>>>>>> http://madhukaudantha.blogspot.com
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> --
>> >>>>>>>>> Cheers,
>> >>>>>>>>> Madhuka Udantha
>> >>>>>>>>> http://madhukaudantha.blogspot.com
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> --
>> >>>>>>> Cheers,
>> >>>>>>> Madhuka Udantha
>> >>>>>>> http://madhukaudantha.blogspot.com
>> >>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>> Cheers,
>> >>>>> Madhuka Udantha
>> >>>>> http://madhukaudantha.blogspot.com
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Cheers,
>> >>> Madhuka Udantha
>> >>> http://madhukaudantha.blogspot.com
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > Cheers,
>> > Madhuka Udantha
>> > http://madhukaudantha.blogspot.com
>>
>>
>
>
>
> --
> Cheers,
> Madhuka Udantha
> http://madhukaudantha.blogspot.com
>



-- 
Cheers,
Madhuka Udantha
http://madhukaudantha.blogspot.com

Reply via email to