perfsonar development work

[Joe Metzger <>]

Hi,
I am trying to identify appropriate tools for the LHCOPN community to
deploy to monitor latency and congestion on their links using the
perfSONAR framework.  I am concern because they need to
start moving forward with monitoring now. And I am not sure all
the necessary perfSONAR components exist yet.


The expected deployment would look something like:
1. Each site deploys a one-way delay measurement point (MP).

2. Each site deploys a measurement archive (MA).

3. All the MA's and MP's register with a common LS, (or a
   set of cooperating LS's in a multi-LS environment.)

4. Each site configures their MP to run continuous
   tests to their neighbors of interest, and publish
   the results in their MA.

5. A GUI allows end users to visualize the data.

6. Some sites with NOCs, deploy an alarm tool that regularly
   fetches the data for a given subset of links from the
   MA's and raises alarms if the performance is out of spec:
   IE no data for a recent period, or the latency exceeds
   some threshold criteria.

I am aware of efforts to address some of these issues, but I am
not sure when it will all come together.

I expect the current RRDMA and/or the SQLMA and the LS will meet the needs.

I am not as clear about the MP, or the component that will
cause the MP to make continuous tests. Who is working on these?

Will the perfSONARUI work to visualize the data?

Is anybody outside of SLAC working on data analysis and automatic
alarm generation?

--Joe