On 20 May 2014 22:06, Kanak Biscuitwala <[email protected]> wrote:

> There are a few ways you can get the data: the Helix REST API, the Helix
> Java API, or the ZooKeeper Java/C API.

Yes, I have tried REST API[1], java API[2] and some command line API.

If you're using Java APIs, then the server side code for the dashboard will
> need to be implemented in Java.
>
Yes.
AFIK rest API and java API not  identical regards the functions, Is I am
correct? or those API getting updating to common API?
 Since there are some java APIs used on dashboard, java will be used for
server side coding.

Reference:
[1] http://ayolajayamaha.blogspot.com/2014/05/dig-up-rest-interface.html,
http://ayolajayamaha.blogspot.com/2014/05/helix-rest-api.html
[2]
http://ayolajayamaha.blogspot.com/2014/05/how-to-run-helix-example-from-source.html


>
> ----------------------------------------
> > Date: Tue, 20 May 2014 14:05:59 +0530
> > Subject: Re: [GSOC] Current Status
> > From: [email protected]
> > To: [email protected]
> > CC: [email protected]; [email protected];
> [email protected]
> >
> > On 19 May 2014 21:19, Kanak Biscuitwala <[email protected]> wrote:
> >
> >> Something important to keep in mind is that ZooKeeper, the Helix
> >> controllers, and the REST admin endpoints may not be running on the same
> >> machines.
> >
> > Yes.
> > As they are running on separate machines, they will have their own JVM,
> > If need to interconnect each we can only use REST api, Am I correct?
> >
> >
> >> Thus, it is not reasonable to deploy ZK alongside the dashboard; instead
> >> the ZK address should be passed as a parameter when the dashboard is
> >> accessed, similar to how ZooInspector works. Then, in a test environment
> >> the ZK host:port is just localhost:nnn, and then that can easily be
> >> generalized to something that isn't colocated.
> >>
> >> You don't need to come up with a way to deploy Helix and ZK -- this is
> >> very specific to the individual user. For dashboard deployment, a user
> >> should not have to install something on each and every client machine.
> >> There should be something running in a server that a client can connect
> to
> >> via an unmodified browser,
> >
> > Therefore we will not need to consider chrome extension as it should to
> be
> > an unmodified browser.
> >
> >
> >
> >> ideally with a way to plug in URLs for ZK, the REST endpoint, etc. The
> >> best solution would be to have the dashboard run without any required
> >> installation by the user;
> >
> > Yes, It's the best Solution.
> >
> > all deployed code stays in the datacenter and on the client side is only
> JS.
> >>
> > In datacenter will contain dashboard codes, (calling jvm, command line
> api,
> > rest api)
> > javascript will only in client side browser ( some case in here we can
> used
> > helix REST api)
> >
> > In Short:
> > We have to keep the dashboard code on the server machine and fetch the
> data
> > from the client machines which doesn't have to install anything. Only JS
> is
> > used here. Does having JVMs in different machine affect the dashboard and
> > data representation? The Calls are via the REST API.
> >
> >
> > Reference:
> > [1] http://helix.apache.org/Architecture.html
> >
> >
> >> ----------------------------------------
> >>> Date: Fri, 16 May 2014 16:06:04 +0530
> >>> Subject: Re: [GSOC] Current Status
> >>> From: [email protected]
> >>> To: [email protected]
> >>> CC: [email protected]; [email protected];
> >> [email protected]
> >>>
> >>> Hi,
> >>>
> >>> 1.) These days I'm going through at Hawtio code & samples.Also building
> >>> simple sample UI to connect to the REST API using javascript. I'm
> looking
> >>> into Angularjs regards dashboard of Hawtio
> >>>
> >>> 2.) There are several ways to interconnect Helix and Hawtio
> dashboard[1].
> >>>
> >>> chrome extensions
> >>> executable jar
> >>> we deploy a WAR file
> >>> stand alone Java application
> >>>
> >>>
> >>> I'm looking for a suitable method to integrate both. I plan to run
> Helix
> >>> zookeeper as stand-alone and hawtio dashboard parallel. Then the JVM
> >>> interconnects both for data exchange. Do you have good solutions? or
> any
> >>> preferred way follow interconnect them.
> >>>
> >>> 3.) I also think to use d3js [2] for chatting and viewing helix cluster
> >>> information. It will be nice smooth and slickly. I have seen email
> thread
> >>> in HELIX about d3js so we can use some in there as well.
> >>>
> >>> [1] http://hawt.io/getstarted/
> >>> [2] http://d3js.org/
> >>>
> >>>
> >>> On 15 May 2014 08:12, Kanak Biscuitwala <[email protected]> wrote:
> >>>
> >>>> Thanks for sharing. It's great that you're documenting all your
> progress
> >>>> on the blog. As you know, don't hesitate to ask if have any questions
> or
> >>>> concerns.
> >>>>
> >>>> Kanak
> >>>>
> >>>> ----------------------------------------
> >>>>> Date: Thu, 15 May 2014 00:19:09 +0530
> >>>>> Subject: Re: [GSOC] Current Status
> >>>>> From: [email protected]
> >>>>> To: [email protected]; [email protected]; [email protected];
> >>>> [email protected]
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>> These are the steps I took to test the REST Interface and to get an
> >> idea
> >>>>> how we can pass parameters through the interface to build a
> dashboard.
> >>>>>
> >>>>> http://ayolajayamaha.blogspot.com/2014/05/dig-up-rest-interface.html
> >>>>>
> >>>>>
> >>>>>
> >>>>> On 10 May 2014 08:54, Ayola Jayamaha <[email protected]>
> >> wrote:
> >>>>>
> >>>>>> Installing hawtio dashboard and building it from source code.
> >>>>>>
> >> http://ayolajayamaha.blogspot.com/2014/05/running-hawtio-dashboard.html
> >>>>>>
> >>>>>>
> >>>>>> On 5 May 2014 09:30, Ayola Jayamaha <[email protected]>
> >> wrote:
> >>>>>>
> >>>>>>> Steps followed in checking REST API
> >>>>>>> http://ayolajayamaha.blogspot.com/2014/05/helix-rest-api.html
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> On 3 May 2014 12:21, Ayola Jayamaha <[email protected]>
> >> wrote:
> >>>>>>>
> >>>>>>>> Thanks Jason for the instructions.
> >>>>>>>>
> >>>>>>>> I will follow the steps that you have given.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On 3 May 2014 04:24, Zhen Zhang <[email protected]> wrote:
> >>>>>>>>
> >>>>>>>>> Hi Ayola,
> >>>>>>>>>
> >>>>>>>>> Thanks for the update. To test/check the rest API, you can start
> >>>>>>>>> Helix-rest-admin when you are running the Helix example in quick
> >>>> start.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>
> >>
> $HELIX_HOME/helix-admin-webapp/target/helix-admin-webapp-pkg/bin/run-rest-admin.sh
> >>>>>>>>> usage: java org.apache.helix.webapp.RestAdminApplication
> >>>>>>>>> --help Prints command-line
> >>>>>>>>> options info
> >>>>>>>>> --port <web service port, default: 8100> Provide web service
> >>>>>>>>> port
> >>>>>>>>> --zkSvr <ZookeeperServerAddress(Required)> Provide zookeeper
> >>>>>>>>> address
> >>>>>>>>>
> >>>>>>>>> It asks for a http port (default 8100) and the zkAddress (e.g.
> >>>>>>>>> localhost:2199). After you start Helix-rest-admin, you can use
> the
> >>>> rest
> >>>>>>>>> api:
> >>>>>>>>>
> http://helix.apache.org/0.6.2-incubating-docs/tutorial_admin.html
> >>>>>>>>>
> >>>>>>>>> Thanks,
> >>>>>>>>> Jason
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Fri, May 2, 2014 at 5:53 AM, Ayola Jayamaha <
> >>>>>>>>> [email protected]>wrote:
> >>>>>>>>>
> >>>>>>>>>> Hi,
> >>>>>>>>>>
> >>>>>>>>>> I was able to build helix from the source code with out test (I
> >> got
> >>>>>>>>> some
> >>>>>>>>>> test failures in TestZKUtil>ZkUnitTestBase.afterTest:93 there
> >> fore I
> >>>>>>>>> skip
> >>>>>>>>>> the test in helix building). I have started blog on those task,
> >>>> Think
> >>>>>>>>> it is
> >>>>>>>>>> OK with helix Developers?
> >>>>>>>>>>
> >>>>>>>>>> Helix build with out test was success[1].
> >>>>>>>>>> I try out helix admin API with helix sample ('Quick start')[2]
> >>>>>>>>>>
> >>>>>>>>>> How can I test/check the rest API sample or tutorial
> >>>>>>>>>> Currently I'm looking at hawtio dashboard samples.
> >>>>>>>>>>
> >>>>>>>>>> [1]
> >>>>>>>>>>
> >>>>>>>>>
> >>>>
> >>
> http://ayolajayamaha.blogspot.com/2014/03/build-helix-from-source-code.html
> >>>>>>>>>> [2]
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>
> >>
> http://ayolajayamaha.blogspot.com/2014/05/how-to-run-helix-example-from-source.html
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On 25 April 2014 22:56, Kanak Biscuitwala <[email protected]>
> >>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> This is a good time to make sure you can run get started with
> >> Helix
> >>>>>>>>> and
> >>>>>>>>>>> can successfully build it. As you go along, we will be
> available
> >> to
> >>>>>>>>>> answer
> >>>>>>>>>>> questions about the Helix codebase, architecture, the issue
> >>>>>>>>>>> tracking/communication/code review processes, and so on.
> >>>>>>>>>>>
> >>>>>>>>>>> Your plan sounds reasonable.
> >>>>>>>>>>>
> >>>>>>>>>>> Kanak
> >>>>>>>>>>> ________________________________
> >>>>>>>>>>>> Date: Fri, 25 Apr 2014 22:32:25 +0530
> >>>>>>>>>>>> Subject: [GSOC] Current Status
> >>>>>>>>>>>> From: [email protected]
> >>>>>>>>>>>> To: [email protected]
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thanks and I accept all your support to achieve it
> successfully.
> >>>>>>>>> Since
> >>>>>>>>>>>> this is my first gsoc project.
> >>>>>>>>>>>>
> >>>>>>>>>>>> What is the best thing to do on this phase of gsoc?
> >>>>>>>>>>>>
> >>>>>>>>>>>> Plan to do on this phase (2 weeks time)
> >>>>>>>>>>>> - helix api try out mainly for dashboard
> >>>>>>>>>>>> -hawito dashboard samples in other product
> >>>>>>>>>>>> - understanding and finding the best approach to helix
> dashboard
> >>>>>>>>>>>> [https://mail.google.com/mail/u/0/images/cleardot.gif]
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> --
> >>>>>>>>>>>> Best Regards,
> >>>>>>>>>>>> Ayola Jayamaha
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Best Regards,
> >>>>>>>>>> Ayola Jayamaha
> >>>>>>>>>>
> >>>>>>>>>> http://ayolajayamaha.blogspot.com
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Best Regards,
> >>>>>>>> Ayola Jayamaha
> >>>>>>>>
> >>>>>>>> http://ayolajayamaha.blogspot.com
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> Best Regards,
> >>>>>>> Ayola Jayamaha
> >>>>>>>
> >>>>>>> http://ayolajayamaha.blogspot.com
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Best Regards,
> >>>>>> Ayola Jayamaha
> >>>>>>
> >>>>>> http://ayolajayamaha.blogspot.com
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Best Regards,
> >>>>> Ayola Jayamaha
> >>>>>
> >>>>> http://ayolajayamaha.blogspot.com
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Best Regards,
> >>> Ayola Jayamaha
> >>>
> >>> http://ayolajayamaha.blogspot.com
> >>
> >>
> >
> >
> >
> > --
> > Best Regards,
> > Ayola Jayamaha
> >
> > http://ayolajayamaha.blogspot.com
>
>



-- 
Best Regards,
Ayola Jayamaha

http://ayolajayamaha.blogspot.com

Reply via email to