the format should also allow collection of summary data
ganglia://meta.rocksclusters.org/san diego grid///cpu/number
would point to the number of cpus on the entire san diego grid (since it
has an empty host tag). since the host tag is empty the "browser" would
"know" that the data was not available from the host but rather a meta
daemon.
translating this format to my original would look like...
meta.rocksclusters.org:san diego grid:::cpu:number
(number of CPUs on the san diego grid)
meta.rocksclusters.org:san diego grid:sdsc rocks
grid:meteor::compute-0-2:cpu:number
(number of CPUs on the meteor cluster host compute-0-2)
And translating it to my proposed format would look like this:
http://meta.rocksclusters.org/san%20diego%20grid/?cpu/number
http://meta.rocksclusters.org/san%20diego%20grid/sdsc%20rocks%20grid/meteor?compute-0-2/cpu/number
I'm pretty sure that slashes in GET queries are acceptable in HTTP. And
even if not, they can be as far as we're concerned.
Or we can always take the post-? substring and replace whatever delimiter
we *do* use with a slash to get the RRD path.
Uh, that was the point of this exercise, right?
so guys.. fed and i just talked on the phone for about an hour and he
understands what i was talking about with the url thing now. i think i
wasn't explaining myself very well before. now that fed knows what i'm
talking about he might be able to explain it better.
I understand what you're talking about (I think), I'm just throwing out
ideas on the format...
