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
