RE: jvsd

Thanks Dan. Dor -Original Message- From: Dan Smith [mailto:dsm...@pivotal.io] Sent: יום ד 19 אוקטובר 2016 18:19 To: geode <dev@geode.incubator.apache.org> Subject: Re: jvsd Hi Dor, jvsd hasn't yet been merged to develop, so for now you still have to check out the feature/GE

RE: jvsd

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

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 <dor.ben-...@amdocs.com> wrote: > Hi, > > Where can I get the

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

jvsd

Hi, Where can I get the latest version of it ? Regards, Dor This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp

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 <dor.ben-...@amdocs.com> wrote: > Hi

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 presents

jVSD

Hi, Can one tell me how the data being read by the jVSD on runtime from Geode / Gemfire? Is this above being saved also or exported / can it be saved ? Regards, Dor This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement

Re: jvsd

en 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 <kl...@apache.org> w

Re: jvsd

+1 Thanks, Dave! On Fri, Sep 23, 2016 at 9:37 AM Dave Barnes <dbar...@pivotal.io> wrote: > Good observations, John. > A clarification: JVSD is Geode-only. The corresponding GemFire tool, VSD, > enjoys a more 'mainstream' status, at least for now, so it still appears in >

Re: jvsd

Good observations, John. A clarification: JVSD is Geode-only. The corresponding GemFire tool, VSD, enjoys a more 'mainstream' status, at least for now, so it still appears in the GF user guide. On Fri, Sep 23, 2016 at 9:34 AM, John Blum <jb...@pivotal.io> wrote: > +1 >

Re: jvsd

(even just explaining all the metrics and what they mean, how they are visualized should be sufficient). On Fri, Sep 23, 2016 at 9:32 AM, Dave Barnes <dbar...@pivotal.io> wrote: > Here's a proposal based on what I've seen in this thread: > 1. We remove JVSD documentation from the user

Re: jvsd

Here's a proposal based on what I've seen in this thread: 1. We remove JVSD documentation from the user manual. 2. We save what's been written so far (mostly just build instructions) as a README on the feature branch. On Thu, Sep 22, 2016 at 7:40 PM, Anthony Baker <aba...@pivotal.io>

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

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

Re: jvsd

22, 2016, Joey McAllister < > > jmcallis...@pivotal.io> > > >> wrote: > > >> > > >> > If it isn't on develop or planned for release, then I vote for > > removing > > >> it > > >> > from the user guide altogether. I l

Re: jvsd

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 > >>

Re: jvsd

ion on the wiki, so the community >> can >> > still easily access it. >> > >> > On Thu, Sep 22, 2016 at 4:51 PM Kirk Lund <kl...@apache.org >> <javascript:;>> >> > wrote: >> > >> > > JVSD isn't labeled as Experimental be

Re: jvsd

iki, so the community > can > > still easily access it. > > > > On Thu, Sep 22, 2016 at 4:51 PM Kirk Lund <kl...@apache.org > <javascript:;>> > > wrote: > > > > > JVSD isn't labeled as Experimental because it isn't even on develop or > in &

Re: jvsd

on the wiki, so the community can > still easily access it. > > On Thu, Sep 22, 2016 at 4:51 PM Kirk Lund <kl...@apache.org <javascript:;>> > wrote: > > > JVSD isn't labeled as Experimental because it isn't even on develop or in > > part of any Geo

Re: jvsd

;kl...@apache.org> wrote: > 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 do

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

Re: jvsd

dy 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 what emerges. > Any favorites among the readers of this thread? > Silence = "Docs group gets to pick" >

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

Re: jvsd

On Thu, Sep 22, 2016 at 3:19 PM, Anthony Baker <aba...@pivotal.io> wrote: > 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, 2

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

Re: jvsd

Bumping this. Any thoughts? On Tue, Sep 20, 2016 at 10:50 AM Dave Barnes <dbar...@pivotal.io> 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

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

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

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

Re: MultiAxisChartFX and jvsd

I don't see the contradiction. MultiAxisChartFX is GPL with class path exception like the JDK. It cannot be relicensed to Apache 2.0. Per ASF rules it may not be shipped as part of the binary distribution either. The library can be downloaded separately, like the JDK, to run the jVSD application

RE: MultiAxisChartFX and jvsd

6 19:55 To: dev@geode.incubator.apache.org Subject: Re: MultiAxisChartFX and jvsd BTW, the jVSD is apache 2 licensed. It is dependent on the JRE, like all other java products. The JavaFX, included with the JRE, is licensed the same as the JRE. The MultiAxisChartFX is licensed the same as the JRE. The plan is to wo

Re: MultiAxisChartFX and jvsd

BTW, the jVSD is apache 2 licensed. It is dependent on the JRE, like all other java products. The JavaFX, included with the JRE, is licensed the same as the JRE. The MultiAxisChartFX is licensed the same as the JRE. The plan is to work the changes in the chart library into the JavaFX project

Re: MultiAxisChartFX and jvsd

; To: dev@geode.incubator.apache.org > Subject: Re: MultiAxisChartFX and jvsd > > Do you have a suggestion for a better graphing package in Java? JavaFX > graphing library is very fast and extensible. > > On Tue, May 10, 2016 at 9:45 AM Dor Ben Dov <dor.ben-...@amdocs.com> &g

RE: MultiAxisChartFX and jvsd

- From: Jacob Barrett [mailto:jbarr...@pivotal.io] Sent: יום ג 10 מאי 2016 19:47 To: dev@geode.incubator.apache.org Subject: Re: MultiAxisChartFX and jvsd Do you have a suggestion for a better graphing package in Java? JavaFX graphing library is very fast and extensible. On Tue, May 10, 2016

Re: MultiAxisChartFX and jvsd

Do you have a suggestion for a better graphing package in Java? JavaFX graphing library is very fast and extensible. On Tue, May 10, 2016 at 9:45 AM Dor Ben Dov <dor.ben-...@amdocs.com> wrote: > Any news on the jVSD and when it will be merged to the main branch ? > Any thought mayb

RE: MultiAxisChartFX and jvsd

Antony, It looks like replacing the javafx is the solution, unless I am missing something ? Dor From: Anthony Baker [mailto:aba...@pivotal.io] Sent: יום ב 09 מאי 2016 19:32 To: dev@geode.incubator.apache.org Subject: Re: MultiAxisChartFX and jvsd jvsd is not on the near-term roadmap proposed

RE: MultiAxisChartFX and jvsd

Any news on the jVSD and when it will be merged to the main branch ? Any thought maybe to replace the javafx with different solution maybe ? Thanks Dor -Original Message- From: Daniel Farcovich Sent: יום ג 10 מאי 2016 08:37 To: Jacob Barrett Cc: dev@geode.incubator.apache.org Subject

RE: MultiAxisChartFX and jvsd

Hi Jake, Do you know when is jVSD going to be merged into the develop branch? Thanks, Daniel -Original Message- From: Jacob Barrett [mailto:jbarr...@pivotal.io] Sent: Monday, May 09, 2016 6:09 PM To: dev@geode.incubator.apache.org Subject: Re: MultiAxisChartFX and jvsd A complete

Re: MultiAxisChartFX and jvsd

jvsd is not on the near-term roadmap proposed by William last week. Community contributions are always welcome! Anthony > On May 9, 2016, at 8:08 AM, Jacob Barrett <jbarr...@pivotal.io> wrote: > >> Is jvsd going to be merged to the main branch anytime soon? signatu

Re: MultiAxisChartFX and jvsd

A complete rewrite of MultiAxisChartFX is not planned. The MultiAxisChartFX is derived from the OpenJDK XYChart and carries the same GPL with class path exception that the JDK does. The plan is to merge jVSD into the develop branch with the dependency as is. The binary distribution

MultiAxisChartFX and jvsd

Hi, Is jvsd going to be merged to the main branch anytime soon? Will MultiAxisChartFX class be replaced by another class which complies with Apache 2.0 license? Thanks, Daniel From: Juan José Ramos [mailto:jra...@pivotal.io] Sent: יום ד 06 אפריל 2016 10:56 To: u...@geode.incubator.apache.org

Re: JVSD status

the community and there is a specification for jvsd on the Geode site for the desired feature set that should be targeted. *Vince Ford* GemFire Sustenance Engineering Beaverton, OR USA http://www.pivotal.io Open Source Project Geode https://geode.incubator.apache.org/ <https://network.pivotal.io/produ

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

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

Re: JVSD status

> Don't see any JIRA activity [1] since mid-Feb though all the subtasks are > resolved. Is JVSD working but currently parked on a feature branch [2]? > > Thanks, > Nitin > > [1] https://issues.apache.org/jira/browse/GEODE-78 > [2] > > https://git-wip-us.apache.org/re

JVSD status

Just wanted to know where this is at. Don't see any JIRA activity [1] since mid-Feb though all the subtasks are resolved. Is JVSD working but currently parked on a feature branch [2]? Thanks, Nitin [1] https://issues.apache.org/jira/browse/GEODE-78 [2] https://git-wip-us.apache.org/repos/asf?p