perfsonar development work

[Fausto Vetter <>]

Hi,

Since tool and schedule has an n-to-n relationship (if we think in  
database concepts :) ), I guess the best way to do is to use metadatas  
like bellow:
- tool metadata
- schedule metadata
- metadata to join tool and schedule

Fausto


> Now, this might sound silly - but the part I always struggle with is
> what 'order' things should be chained:
>
> data -> cron -> owamp
>         or
> data -> owamp -> cron
>
> It probably doesn't matter that much. But, it would be good to have a
> clear reason that can give guidance across multiple service/message
> definitions. For example, I am hitting a similar issue with bwctl:
>
> data -> bwctl-scheduling -> iperf
>         or
> data -> iperf -> bwctl-scheduling
>
> (This is for a new version of the bwctl schema. The current one
> basically has a single metadata that includes iperf and bwctl options.
> But the next version of bwctl will support other throughput tools such
> as nuttcp and thrulay so I was trying to factor out the bwctl specific
> things.)
>
> jeff



--
Fausto Vetter
NPD/UFSC

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.