LCG Management Board

Europe/Zurich
CERN

CERN

Les Robertson
Description
16:00 CERN/10:00 EDT/09:00 CDT

Phone access code: 0193504

Mute/unmute your phone dialing # # 1

Telephone conference:
a. Dial +41227676000 and enter access code 0193504 followed by # , or
b. To have the system call you, click here: https://audioconf.cern.ch/call/0193504

Email Distribution List: worldwide-lcg-management-board@cern.ch
Email List Archive: worldwide-lcg-management-board (requires NICE authentication)

See also the: Management Board Wiki
    • 16:00 17:20
      AGENDA
      • 16:00
        Minutes and Matters Arising 5m
      • 16:05
        Action List Review 5m
      • 16:10
        GSSD Working Group: Mandate, Membership, Chair 5m
        Speaker: K.Bos
      • 16:15
        Update on Targets and Milestones for 2007 15m
        1. Demonstrate Tier0-Tier1 data export at 65% of full nominal rates per site using experiment-driven transfers
          • Load generators for ALICE, ATLAS & CMS ok
        2. Demonstrate Tier0-Tier1 data export at 50% of full nominal rates (as above) in conjunction with T1-T1 / T1-T2 transfers
          • Inter-Tier transfer targets taken from ATLAS DDM tests / CSA06 targets
        3. Demonstrate Tier0-Tier1 data export at 35% of full nominal rates (as above) in conjunction with T1-T1 / T1-T2 transfers and reprocessing / analysis stripping at Tier1s
          • Tier1 production activity needs to be defined per-VO and depends on computing model / production plans for that VO.
        4. Provide SRM v2.2 endpoint(s) that implement(s) all methods defined in SRM v2.2 MoU, all critical methods pass tests
          • Proposal that requirement on bring online methods be relaxed as that they are not required in Q1 2007. (i.e. can still pass milestone without them, e.g. success with).

        Questions:

        • With respect to milestone 3 above, could a generic sub-milestone be written that is VO-independent, e.g. every file transferred to a Tier1 is read at least once by a Grid job running at that site?
          • This would allow VO-specific milestones, e.g. that couple to conditions DB deployment models, to remain as experiment milestones, which is probably where they belong...
          • Some explicit targets for the WMS at each Tier1 would nevertheless have to be established (derived from the above).
        • Does it make sense to have (an) explicit database milestone(s) at this level? (Which would clearly have to be experiment-specific).
          • Maybe same comment as above applies...
        Speaker: J.Shiers
        SRM v2.2 critical methods
      • 16:30
        Reliability and Availability Data Summary for December 2006 10m
        Speaker: L.Robertson
      • 16:40
        Follow-up on Groups, Roles and Job Priorities 20m
      • 17:00
        AOB 5m