Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] PerfSONAR visualization ideas.

Subject: perfsonar development work

List archive

Re: [pS-dev] PerfSONAR visualization ideas.


Chronological Thread 
  • From: "Jeff W. Boote" <>
  • To: Joe Metzger <>
  • Cc: Nicolas Simar <>, Szymon Trocha <>, Eric Boyd <>,
  • Subject: Re: [pS-dev] PerfSONAR visualization ideas.
  • Date: Tue, 03 Oct 2006 09:22:21 -0600

Joe Metzger wrote:
Hi,
My management has asked if perfSONAR could support some of the
visualizations that DREN is starting to use.

http://www.wcisd.hpc.mil/~phil/Planet-DREN/

This is an interesting integration of Toplogy, Utilization,
Latency and Bandwidth measurements.

Is anybody working on this?

(This is Phil Dykstra's stuff, right? Matt and I were helping him get some OWAMP data collected for the Abilene/DREN peering points... But, I don't know if he is integrating any of that into these visualizations. This is very nice work.)

I guess it depends on what you mean by 'supporting' those visualizations... I'm sure there are similar things in the works in CNM and Nemo (and perhaps Vedrin has ambitious plans for perfSONARUI).

I suspect the easiest way to support these types of visualizations is to make integrating the perfSONAR data into other applications as easy as possible. For example, if Phil could have his application consume the data that is made available from various perfSONAR MA's.

The trick would be to make sure we have geographical references for all subjects in the MA's.

I don't think anyone could adequately answer how difficult it would be to integrate pS data into Phil's application without knowing what kind of data collection his stuff uses. (And Phil probably doesn't know enough about perfSONAR to know from his side.)

But, I think these kinds of integrations are the way forward. Similar to the way that we have integrated into existing RRD infrastructures to make data available, we should integrate into existing visualization and analysis tools.

jeff



Archive powered by MHonArc 2.6.16.

Top of Page