Today, Federico Sacerdoti wrote forth saying... > How about: > > ganglia://meta.rocksclusters.org/san diego grid/sdsc rocks > grid/meteor//compute-0-2 ? > > Not exactly strict URL, but close... We should probably eliminate > illegal URL characters (like spaces, etc). Would use existing standards > for the "ganglia address", which is good.
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) 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. -matt
