T2D = a T2 with sufficient network and storage bandwidth to be allowed to transfer directly to/from other T1 and T2D sites
-----Original Message-----
From: Testbed Support for GridPP member institutes [mailto:[log in to unmask]] On Behalf Of Ewan MacMahon
Sent: 06 April 2011 16:28
To: [log in to unmask]
Subject: Re: Sonar test summary
> -----Original Message-----
> From: Sam Skipsey [mailto:[log in to unmask]]
> Sent: 06 April 2011 16:22
>
> > What exactly does being a T2D imply, and require? Does this just mean
> > being used in the caching mode that Graeme was describing at Sussex?
> >
>
> Essentially, IIRC... but that also has concomitant effects on the amount
> of work a site would expect (plus, it can only be good for a region to
> have T2Ds, since they may end up caching copies of important data for the
> cloud).
>
OK; I've just been having a look at the March GDB atlas presentation,
and if I'm reading it correctly the T2D idea seems to be the associating
a Tier 2 with multiple Tier 1s/clouds. based on Graeme's Sussex talk the
'tier 2 as cache' thing is PD2P.
So; to unpick this a bit - am I right in thinking that some sites will
be T2D sites (and if so, what exactly are the requirements?) and all
Tier 2 space will be used according to the PD2P 'caching' mode, and none
by planned data placement?
Ewan
|