Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] perfsonarbuoy collector owamp database with multiple measurement sets

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] perfsonarbuoy collector owamp database with multiple measurement sets


Chronological Thread 
  • From: Andrew Lake <>
  • To: Ben Nelson <>
  • Cc:
  • Subject: Re: [perfsonar-user] perfsonarbuoy collector owamp database with multiple measurement sets
  • Date: Fri, 14 Feb 2014 14:58:38 -0500

Hi,

The <DATE>_TESTSPEC tables map to the testspec blocks in the owmesh, not the
mesurementset. I don't think there is an issue here. Even if something is
inserting one testspec for every measurementset, there shouldn't be an issue.
The description field is not used anywhere and the protocol that interacts
with tools like the graph don't even see the description.

Thanks,
Andy

On Feb 12, 2014, at 2:32 PM, Ben Nelson
<>
wrote:

> Hello,
>
> I'm running perfsonar with multiple measurement sets, and have a
> question on how the db structure is supposed to work with owamp vs
> bwctl. In my bwctl db, each measurement set gets a new row in the
> <DATE>_TESTSPEC table, with the description of the row matching the
> description for that particular measurement set in owmesh.conf.
>
> In my owamp db, the <DATE>_TESTSPEC table is only populated with one
> entry which seems to have the description of the first measurement set
> that enters data into that table for that date period. The bwctl and
> owamp measurement sets I have in my owmesh.conf are setup in a similar
> manner, just adjusting the description, testspec, and measurement set
> name. Should I be seeing this behavior in my owamp db or should there
> be multiple entries in the TESTSPEC table for each measurement set?
>
> I can provide the owmesh configuration if that would be helpful.
>
> Thanks,
> Ben
>
> --
> Ben Nelson, Systems Engineer
> Indiana University GlobalNOC
> <>
>




Archive powered by MHonArc 2.6.16.

Top of Page