On 24/02/12 17:01, Ewan MacMahon wrote:
>> -----Original Message-----
>> From: Testbed Support for GridPP member institutes [mailto:TB-
>> [log in to unmask]] On Behalf Of Ian Collier
>>
>> The relevant installation guide is pretty foolproof:
>>
>> http://code.google.com/p/perfsonar-
>> ps/wiki/pSPerformanceToolkit32#NetInstall_CD
>>
> Great. That's the sort of thing I was hoping for when I
> followed the 'Getting Started' link on the PerfSonar front
> page, but it just goes to a big list of downloads.
You can get there (follow the product homepage link on the download page).
>
>> By all means base it on something else, but then if it does not behave as
>> expected you won't get much help from the developers.
>>
> I have now filed that idea under 'bad things to not do';
> we should clearly stick to the standard issue stuff.
>
>> The web interface makes it really very straightforward to enable all the
>> relevant tests (ie bandwidth only on one host and latency on another) and
>> then configure them for the hosts you choose.
>>
> Well in that case I think the main thing we need is a list of
> the hosts to make them talk to. Do we have one of those, and
> are the existing PerfSonar endpoints (like yours) generally
> open to being talked to, or do we need to let you know where
> the connections will be coming from?
The LHCONE workshop at Berkley has some talks that mention perfsonar
http://indico.cern.ch/conferenceDisplay.py?confId=160533
and
https://twiki.cern.ch/twiki/bin/view/LHCONE/SiteList
provides some useful info on how the lhcone guys are doing it.
AIUI, it's possible to set up communities in perfsonar. There's an ATLAS
community and an LHC community. I'm not sure if we want to create a
GridPP community or not.
There's also a couple of links on fasterdata.es.net which look like they
may be useful - though mainly they encourage you to set up a perfsonar
node.
Chris
|