LPC EOS collaborative groups

LPC Collaborative Group

Membership of LPC Collaborative Group

LPC EOS collaborative groups are designed to encourage collaboration with shared EOS space larger than individuals can have.


• To check membership in a LPC Collaborative group (FNAL account access for EOS space in the group), at the cmslpc-el9 command line do: getent group | grep ^lpcgroupname. The output will look something like the following (partial output):

  • lpcgroupname:x:9955:user1,user2,user3,user4

  • Group members of lpcgroupname are listed in the first line and are: user1,user2,user3,user4

Add user to LPC Collaborative Group

• To request LPC Collaborative group access (for EOS and/or NFS space usage), fill out the LPC Service Portal form: "Modify Account on LPC Collaborative Group".
  • Use your Fermilab Services Username and password, or Kerberos (after one time configuration of browser following instructions on the Fermilab Single Sign on Page.)
  • Choose "Add" to add a user to the group. You can fill out this form for yourself or another user.
  • Be sure to include the reason to join. The LPC Collaborative group convener(s) will approve or reject.
  • Once the account is added, up to 1 Fermilab business day to propagate to all the cmslpc systems.

  LPC Collaborative Group usage

• If you are a member of one of the LPC Collaborative groups, you can utilize the storage areas allocated to that LPC Collaborative group on NFS or EOS. These LPC Collaborative group areas are located at:
• ~lpcgroupname/nobackup  (quota limit set; ksu lpcgroupname to the LPC Collaborative group user before writing) - note that for xrdcp transfers you do NOT ksu, do them as yourself.
• /uscmst1b_scratch/lpc1/3DayLifetime/lpcgroupname
• /store/group/lpcgroupname
• note that the /store/group/lpcgroupname area is a soft link to /store/user/lpcgroupname on EOS T3_US_FNALLPC, as CRAB requires the group, but the local filesystem puts everything in user
• File permissions for files made in the group account NFS areas are by default only allowed to write by LPC Collaborative group members (either as ksu lpcgroupname or as yourself from Crab3 jobs or xrdcp.) By default, all CMS users with a Fermilab account can read the files on NFS, and all EOS files can be read by all CMS users with a valid grid certificate via xrootd.

Request a new LPC Collaborative Group Account - policies

• LPC Collaborative group areas are created for broad collaboration across institutions. All LPC Collaborative group requests, both for new accounts and existing quota increases have to be approved by LPC coordinators.
• To check a list of existing LPC Collaborative groups, in Fermilab ServiceNow LPC Service Portal, after authenticating with your Fermilab Single Sign on, the form:
  • In the LPC Service Portal, choose: Modify Account on LPC Collaborative Group (Show me how - outdated 9/25/2018[β]).
  • The pull-down menu lists the currently available LPC Collaborative groups.
  • Note that in the cluster command line you may use getent group, but that also lists system groups as well as LPC Collaborative Groups.
  • You may also Contact LPC Support for more information about existing groups
  
  
• To request a new LPC Collaborative group, in the LPC Service Portal, choose "Add LPC Collaborative Group". Do note that we expect you to review existing groups to see if one fits your needs, and we may have unused groups that would work. This request will go to LPC Coordinators for approval. The request will contain:
  • Group area name (must have "lpc" at the start now): lpcgroupname
  • Your institution
  • Requested allocation of space in EOS (logical space only, that is, not including recplication)
  • Approximate number of members (this can include future members who don't yet have FNAL accounts
  • Number of members from non-US institutions
  • Who will be the approver(s)/convener(s) of the group? You can check the box if that includes yourself, and you will put in names which will be matched against the FNAL database for convener(s)
  • Members. You will put in names that are matched against the FNAL database for users to add to the group when it's created
  • Reason for request (has to be collaborative in nature across multiple institutes):

Convener(Approvers) of LPC Collaborative Group

• Each LPC Collaborative group has one or more conveners who is in charge of the following:
• Approve or Reject add/Remove new member tickets.
• Note that email approvals ONLY work from the email that Fermilab has as your main email (check at tele.fnal.gov on a FNAL VPN)
• If your email doesn't work you won't get any notification, but you can check your approvals online using one of these type of links in your email: Click here to view Approval Request: LINK or Click here to view the details of the Requested Item: RITM links after authenticating with Fermilab Single Sign On - you will see a menu for "Approve" or "Deny".
  • If you cannot find your approvals, you can also see a list in the LPC Service Portal in the upper right "Approvals", alternately, a co-convener may have already approved the request
• Marguerite Tonjes as LPC Computing Support is added as co-convener for all groups to assist in case of missing approvals or missing conveners
• Information about how to find LPC group EOS quota at this link
• Clean up out of date files with assistance of group members, note that NOTHING is backed up on FNAL EOS. Advanced tools to find out EOS usage (see the eosdu script as well as the "find" commands to locate files more than a year old or large files). In all cases do NOT use the fuse mount for file removal, as that may crash EOS.
• Conveners can be added or removed for a group with the LPC Service Portal ticket Add/Remove an LPC Convener. This action will be approved by LPC Coordinators

EOS disk space

To understand how much space a user or LPC Collaborative group has on the EOS (T3_US_FNALLPC /store/user) filesystem, consult the dedicated EOS Mass Storage page.