Mandate of the GSSD Working Group

  1. Establishing a migration plan from SRM v1 to SRM v2 so that the experiments can access the same data from the 2 endpoints transparently.
  2. Coordinating with sites, experiments, and developers the deploymentcof the various 2.2 SRM implementations and the corresponding Storage Classes.
  3. Coordinating the Glue Schema v1.3 deployment for the Storage Element and make sure that the information published are correct.
  4. Ensuring transparency of data access and the functionalities required by the experiments (see Baseline Service report).
  5. Coordinating the provision of the necessary information by the Storage Providers in order to monitor the status of storage resources, ensuring that all sites provide the experiments with the requested resources and with the correct usage.

One of the outcome of the GSSD group is to produce the precise guidelines per implementation focusing on deploying the specific storage classes for a specific VO. If needed, we will organize tutorials (for Tier-2s) and agree on mini SC targets with the experiments.

Experiments representatives, SRM developers, MSS providers, Tier-1 and Tier-2 representatives are involved in the discussions and in the work of the GSSD. However, in order to be effective, one experiment and one specific implementation will be targeted at a given time. Possibly working sub-groups will be put in place to proceed in parallel on multiple implementations.

-- Flavia Donno - 31 Jan 2007


This topic: LCG > WebHome > GSSD > GSSDMandate
Topic revision: r2 - 2007-01-31 - FlaviaDonno
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback