T3UserMeeting200909 < CmsTier3

<!-- keep this as a security measure:
   #uncomment if the subject should only be modifiable by the listed groups 
   # * Set ALLOWTOPICCHANGE = Main.TWikiAdminGroup,Main.CMSAdminGroup
   * Set ALLOWTOPICRENAME = Main.TWikiAdminGroup,Main.CMSAdminGroup
   #uncomment this if you want the page only be viewable by the listed groups
   #* Set ALLOWTOPICVIEW = Main.TWikiAdminGroup,Main.CMSAdminGroup,Main.CMSAdminReaderGroup
-->

---+ CMS T3_CH_PSI User Meeting

The meeting will take place on Mon, Sep 14 2009, approx. 9:30h
An EVO Room in the CMS community will be reserved for external listeners.

Slides for the meeting: [[%ATTACHURL%/PSI-T3-20090914.pdf][PSI-T3-20090914.pdf]]


---++ Planned Program

   * What resources do we have in Switzerland in terms of CPU and storage?
   * (my take on ) what tasks to ideally do on
      * the Grid
      * T2_CH_CSCS
      * T3_PSI_CH
   * CMS data management and how it relates to end users
      * How to register your output files in the central DBs (_local publishing_)
      * CMS name space
         * (How to discover the exact filename of a dataset file at another site)
      * How to transfer data between centers, expected transfer times, possible optimizations
         * Problem: Copying of user generated data between sites (cannot yet be done with phedex - file sizes! CMS may provide merge jobs at some point)
      * Short discussion on how we should organize the management of our space (getting rid of old sets in a convenient way, without undue wasting of everybody's time) 
      * Short guidelines on how to access data
   * Developing the T3 (next upgrades)
      * discussion on what use cases users would like to have the systems optimized for, e.g.
         * interactive vs. batch use
         * should we introduce one more queue with short turnaround times?
         * requirements for graphical interactive work? NX-service?
   * Can we improve the communications and information exchange between users and admins? We want to have a lean and efficient system with as few points of entry as possible, and the minimum of policies.
      * Communication tools
         * CERN wiki
         * CSCS T3 and T2 wiki
         * email lists
         * chat?
      * where to report problems, trouble tickets.
   * Very short explanation on how the CMS sites are organized centrally, how the information flows between sites (FacOps project)

AOB:
   * [[https://twiki.cern.ch/twiki/bin/view/CMS/CMST2Associations][CMS group associations to Tier-2s]]. We currently only are associated with b-physics. Other associations required (e.g. ewk)?
      *  CMS requires for every group association 50 TB of extra storage space, i.e. in total (50 + Ngroups * 50) TB
      * [[https://cmsweb.cern.ch/phedex/prod/Reports::SiteUsage?node=T2_CH_CSCS][Current usage by group for T2_CH_CSCS]]

---++ Your Suggestions

   * F. Ronga: would it be conceivable to have commissioned links with additional Tier2s (other than CSCS, that is).
      * DF: maybe. But CMS tries to keep the number of links low (every link needs entries in the DB and effort to keep alive in the infrastructure). T3s are at the bottom of the priorities. We need a clear use case for this. As I see it, it would be most desirable to have links to multiple T1 centers, because they are the main source of the data sets. But the T1s want to limit the connections.

-- Main.DerekFeichtinger - 24 Aug 2009
Attachments
Topic attachments
I	Attachment	History	Action	Size	Date	Who	Comment
pdf	PSI-T3-20090914.pdf	r1	manage	716.5 K	2009-09-13 - 19:39	DerekFeichtinger
This topic: CmsTier3 > WebHome > T3UserMeeting200909
Topic revision: r8 - 2009-09-13 - DerekFeichtinger