perfsonar development work

["Jeff W. Boote" <>]

Maciej Glowiak wrote:
> Hi Jeff,
>
> I fully agree, that we should follow the eventType naming scheme. But in 
> fact there was previously defined "echo" eventType for handling echo. To 
> be honest I didn't recognize the eventType before, because LS determined 
> the message by its type which was "EchoRequest". I missed the eventType 
> at all.

I understand. No problem. (We probably should think about a good naming scheme 
for message types too - but another day.)

> Recently Roman wrote generic Echo handler for all services and he used 
> just "echo" event type. To distinguish the generic Echo from 
> LS-parametrized-echo I add just a suffix ".ls", but of course I should 
> have followed the naming scheme. Anyway, I wasn't sure how it should 
> look like, because echo is not a characteristic/metric.

No problem. I just saw the check-in related to eventType and wanted to try and 
get the new naming scheme into services as quickly as possible.

> Perhaps some examples would be useful on "Generalities" page.

Ok - I will answer as best I can here, and update this page as well.

> I was a bit confused:
>
> "ggf.org/ns/nmwg/characteristic/echo/1.0"
> is not appropriate

I agree.

> "perfSONAR/characteristic/echo/1.0"
> contains no "LS", so:
>
> "perfSONAR/characteristic/echo.ls/1.0"
>
> but is "perfSONAR" valid organization name?
> and it's still not a characteristic. So:
>
> "perfSONAR/tools/echo.ls/1.0"
> or better:
> "perfSONAR/tools/echo/ls/1.0"
> but is "echo/ls" valid tool name?
> and what with perfSONAR.
>
> And so on. If they're defined, I'll follow the examples.

The general definition of valid namespaces is defined by the OGF standard 
found at:
        http://www.ogf.org/documents/GFD.84.pdf

It looks like I was not complete enough on the wiki. (I should have prefixed the 
namespace rules with 'http://'.)

Basically, ORG should be a domain name. So, for perfsonar services I believe we 
should in general use something like:

        schemas.perfsonar.net

We also have some latitude to define the hierarchy under schemas.perfsonar.net 
in a way that makes sense for us. For example, we can add a sub-dir to that 
'org' if we want. So, for administrative support eventTypes like 'echo' perhaps 
we should come up with our own hierarchy under perfSONAR. How about:

http://schemas.perfsonar.net/tools/admin/echo/ls/2.0

http://schemas.perfsonar.net/tools/admin/echo/2.0 can be a generic version that 
any service can use, and can be extended by ones at lower levels.

Since this is under the perfsonar domain, we can define this ourselves so if 
anyone has another suggestion that makes more sense I'm fine with it. But, I 
would like to get this formalized as quickly as possible.

Also, has anyone written an RNC for echo messages yet? I'm currently working 
with Verena to create a bwctl RNC, and I've also started an owamp RNC - so I 
could pretty easily help with an echo one right now if that would be helpful. 
Then echo messages could be validated using the schema validation tools that 
Jason put on the NMWG site recently.

jeff