RE: jvsd

Thanks Dan. Dor -Original Message- From: Dan Smith [mailto:dsm...@pivotal.io] Sent: יום ד 19 אוקטובר 2016 18:19 To: geode Subject: Re: jvsd Hi Dor, jvsd hasn't yet been merged to develop, so for now you still have to check out the feature/GEODE-78 branch and build it from s

RE: jvsd

Thanks Dave. Dor -Original Message- From: Dave Barnes [mailto:dbar...@pivotal.io] Sent: יום ד 19 אוקטובר 2016 18:42 To: geode Subject: Re: jvsd Hi Dor, JVSD is in the Geode Repo on a feature branch, feature/GEODE-78. See http://geode.docs.pivotal.io/docs/tools_modules/jvsd.html for

Re: jvsd

Hi Dor, JVSD is in the Geode Repo on a feature branch, feature/GEODE-78. See http://geode.docs.pivotal.io/docs/tools_modules/jvsd.html for details. -Dave On Wed, Oct 19, 2016 at 1:43 AM, Dor Ben Dov wrote: > Hi, > > Where can I get the latest version of it ? > > > Regards, > Dor > > This messag

Re: jvsd

Hi Dor, jvsd hasn't yet been merged to develop, so for now you still have to check out the feature/GEODE-78 branch and build it from source. Here are some instructions: https://github.com/apache/incubator-geode/blob/feature/GEODE-78/geode-jvsd/README.md 0-Dan On Wed, Oct 19, 2016 at 1:43 AM, D

Re: jVSD

Hello Dor, jVSD doesn't read statistics in runtime from Geode, it only opens and presents statistics stored in files. You need to use GFSH commands to manage and monitor Geode in runtime. Best regards. On Thu, Oct 13, 2016 at 10:54 AM, Dor Ben Dov wrote: > Hi, > > Can one tell me how the data

RE: jVSD

Thanks Juan for the quick response. Dor -Original Message- From: Juan José Ramos [mailto:jra...@pivotal.io] Sent: יום ה 13 אוקטובר 2016 17:33 To: dev@geode.incubator.apache.org Subject: Re: jVSD Hello Dor, jVSD doesn't read statistics in runtime from Geode, it only opens and pre

Re: jvsd

+1 If its not part of a release its documentation shouldn't be either. -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: 631-835-4771 On Thu, Sep 22, 2016 at 7:58 PM, Joey McAllister wrote: > If it isn't on develop or planned for release, then I vote for removing it > from the u

Re: jvsd

> > > README on the feature branch. > > > > > > On Thu, Sep 22, 2016 at 7:40 PM, Anthony Baker > > wrote: > > > > > > > Corporate org structures don’t get a voice on ASF mailing lists, only > > > > community participan

Re: jvsd

e on ASF mailing lists, only > > > community participants :-) > > > > > > Anthony > > > > > > > > > Begin forwarded message: > > > > > > *From: *Dave Barnes > > > *Subject: **Re: jvsd* > > > *Date: *September 22

Re: jvsd

:-) > > > > Anthony > > > > > > Begin forwarded message: > > > > *From: *Dave Barnes > > *Subject: **Re: jvsd* > > *Date: *September 22, 2016 at 4:37:19 PM PDT > > *To: *dev@geode.incubator.apache.org > > *Reply-To: *dev@geode.incub

Re: jvsd

> Corporate org structures don’t get a voice on ASF mailing lists, only > community participants :-) > > Anthony > > > Begin forwarded message: > > *From: *Dave Barnes > *Subject: **Re: jvsd* > *Date: *September 22, 2016 at 4:37:19 PM PDT > *To: *dev@geode.incubator.apac

Re: jvsd

Who are you "end users"? On Thu, Sep 22, 2016 at 7:37 PM, Anthony Baker wrote: > When the first instruction is `git checkout feature/GEODE-78` I think it’s > clear the target audience is not end users. > > Beyond that, it feels to early to document a feature whose final form may > look significa

Re: jvsd

When the first instruction is `git checkout feature/GEODE-78` I think it’s clear the target audience is not end users. Beyond that, it feels to early to document a feature whose final form may look significantly different than it does today. Anthony > On Sep 22, 2016, at 5:06 PM, Kirk Lund wr

Re: jvsd

+1 *Spring Boot* does this too (in some places, for instance, here [1] and here [2]; and then from the docs...

Re: jvsd

Yeah, I'm with you there. Content for developers should live where developers are most likely to read it, and I don't think the wiki should be in lieu of the READMEs. I'm not a fan of trying to host any sort of documentation geared toward a single audience in more than one place (e.g., a README *a

Re: jvsd

And by Wiki, I mean GitHub's Wiki associated with the (source code) Repository. Between GitHub Wiki and README, README wins every time for reason previously mentioned. On Thu, Sep 22, 2016 at 5:28 PM, John Blum wrote: > Personally, as a engineer, I am more of a fan of the GitHub README (or > ev

Re: jvsd

Personally, as a engineer, I am more of a fan of the GitHub README (or even Wiki), rather than a separate site. A lot easier for users to update (submit a PR). On Thu, Sep 22, 2016 at 5:06 PM, Kirk Lund wrote: > +1 > > On Thursday, September 22, 2016, Joey McAllister > wrote: > > > If it isn't

Re: jvsd

+1 On Thursday, September 22, 2016, Joey McAllister wrote: > If it isn't on develop or planned for release, then I vote for removing it > from the user guide altogether. I like the recommendation to keep this and > similar (non-develop branch) information on the wiki, so the community can > stil

Re: jvsd

If it isn't on develop or planned for release, then I vote for removing it from the user guide altogether. I like the recommendation to keep this and similar (non-develop branch) information on the wiki, so the community can still easily access it. On Thu, Sep 22, 2016 at 4:51 PM Kirk Lund wrote:

Re: jvsd

JVSD isn't labeled as Experimental because it isn't even on develop or in part of any Geode release candidate. As far as I know, it exists only on an incomplete and out-of-date feature branch. Hence, my vote is to remove any mention of it from the docs until it merges to develop or at a minimum get

Re: jvsd

I would vote for including it as an "experimental" feature. On Thu, Sep 22, 2016 at 4:37 PM, Dave Barnes wrote: > Process for handling Experimental docs is still being hammered out. Common > element among working scenarios is isolation from the body of the User > Guide proper, so I'll remove the

Re: jvsd

Process for handling Experimental docs is still being hammered out. Common element among working scenarios is isolation from the body of the User Guide proper, so I'll remove the JVSD component from the User Guide's Tools and Modules section. Could go on the Wiki, could go in an appendix. We'll see

Re: jvsd

Truthfully, I don't think this is any different than API features that have been annotated with "@Experimental" (e.g. LucenceService ). I.e. nothing is going to stop a user from trying to

Re: jvsd

I think that providing documentation for jvsd before it is included in the source and binary release distributions will only confuse users. +1 for removing. Anthony > On Sep 22, 2016, at 2:39 PM, Dave Barnes wrote: > > JVSD has appeared in the Geode user manual since M2. See > http://geode.d

Re: jvsd

JVSD has appeared in the Geode user manual since M2. See http://geode.docs.pivotal.io/docs/tools_modules/jvsd.html. Kirk, are you recommending that we remove this? On Thu, Sep 22, 2016 at 10:57 AM, Kirk Lund wrote: > I would recommend not mentioning jVSD at all in the Geode 1.0 docs. Right > now

Re: jvsd

I would recommend not mentioning jVSD at all in the Geode 1.0 docs. Right now it's just a Jira ticket and feature branch. I think the docs should only cover what's in Geode 1.0. If there's some doc or wiki page about proposed future features or features currently looking for contributors/developer

Re: jvsd

Bumping this. Any thoughts? On Tue, Sep 20, 2016 at 10:50 AM Dave Barnes wrote: > To what degree should jVSD be mentioned in the docs? The current writeup is > essentially "go get it if you want it, but be warned that it's not fully > baked and we don't support it". > Would that still be the app

Re: jvsd

To what degree should jVSD be mentioned in the docs? The current writeup is essentially "go get it if you want it, but be warned that it's not fully baked and we don't support it". Would that still be the appropriate jVSD policy for 1.0.0? On Tue, Sep 20, 2016 at 10:42 AM, Dan Smith wrote: > I d

Re: jvsd

I don't think we should try to include jVSD in 1.0.0 at this point, because it introduces dependencies that might make the 1.0.0 release more complicated such as the MultiAxisChartFX dependency. But I think the should try to get it to develop sooner rather than later to make it easier for people to

Re: jvsd

Hi Gal, This page talks about the goals and status for jvsd: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61309918 Here’s another thread which discussed options for moving forward: http://mail-archives.apache.org/mod_mbox/geode-dev/201605.mbox/%3c14840688a62caa4197a28aaccda9d2

Re: JVSD status

: vf...@pivotal.io [mailto:vf...@pivotal.io] > Sent: יום ב 21 מרץ 2016 21:00 > To: dev@geode.incubator.apache.org > Subject: Re: JVSD status > > There is still significant work to make jvsd usable as a tool for review > of the geode metrics. > > The initial work was to make s

RE: JVSD status

Vince, As far as I understood, the jVSD tool can be found in one of the branches, are you planning to put it in the 'main' branch ? Dor -Original Message- From: vf...@pivotal.io [mailto:vf...@pivotal.io] Sent: יום ב 21 מרץ 2016 21:00 To: dev@geode.incubator.apache.org Subject

Re: JVSD status

There is still significant work to make jvsd usable as a tool for review of the geode metrics. The initial work was to make sure it could be built, and generally worked ( started, open stats files, basic graphs). But there is still significant work needed to get to point where it can be part o

Re: JVSD status

As I know; initial work was done to donate the code to apache...Its one of the project community can pick-up and contribute without knowing much of the Geode... -Anil. On Sun, Mar 20, 2016 at 11:04 PM, Nitin Lamba wrote: > Just wanted to know where this is at. > > Don't see any JIRA activity [