Skip to Content.
Sympa Menu

perfsonar-dev - Re: BWCTL MA Schema

Subject: perfsonar development work

List archive

Re: BWCTL MA Schema


Chronological Thread 
  • From: Roman Lapacz <>
  • To: , Verena Venus <>, "Jeff W. Boote" <>
  • Cc: Roman Lapacz <>, Martin Swany <>, Szymon Trocha <>, perfSONAR developers list <>
  • Subject: Re: BWCTL MA Schema
  • Date: Mon, 09 Feb 2009 13:20:07 +0100

Jason Zurawski wrote:


The schema does not have 'throughput' or 'jitter' elements.


Corrected in my doc and the iperf schema in the main pS repo. Jitter *should* have been there since this is reported by iperf UDP tests.

Throughput is more descriptive than 'value' in my opinion (since there are many 'values' that can be returned by an iperf test). I have added throughput to the schema but kept value for now in case VV or anyone else has a use for it.

I think we should talk about deprecating the attribute or perhaps allowing it to stay with a use that will vary by service (I would prefer the latter).

Jason,

what about packet loss and fields containing units names (I understand we consider iperf default units but maybe it's better to clearly include them in the schema). Example:

IperfDatum =
element iperf:datum {
attribute throughput { xsd:string }? &
attribute throughputUnits { xsd:string }? & attribute jitter { xsd:string }? &
attribute jitterUnits { xsd:string }? & attribute loss { xsd:string }? &
attribute interval { xsd:string }? & attribute intervalUnits { xsd:string }? & (
(
attribute timeType { xsd:string } &
attribute timeValue { xsd:string }
) |
Time
)? }


Roman


You didn't mention loss earlier, but yes this should be there too. I will add it.

I just took a look at an example of iperf output :)


I have no problem adding the 'units' fields, but lets let everyone weigh in.

OK. Verena, Jeff what's your opinions on this?

Roman




Archive powered by MHonArc 2.6.16.

Top of Page