<!-- 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 --> %TOC% ---+ Policies for the resource allocation on the PSI Tier-3 These policies were agreed upon in the [[SteerBoardMeeting01][first]] and [[https://wiki.chipp.ch/twiki/bin/view/CmsTier3/SteerBoardMeeting02][second]] Steering Board meetings. 1 We organize the users along [[PhysicsGroupsOverview][Physics Groups]] 1 For the purpose of the cluster organization, *every user must be mapped exactly to one physics group* (even though the user may work for several). 1 The *resources available to a physics group* consist of the added up resources of its members. How these resources are used is up to the physics group's internal organization. 1 Each physics group has one *Responsible User* who * takes care of managing the group's resources (e.g. deciding what data sets to delete). * is the single point of contact for the cluster administrators for organizational issues. * can propose a guest user (see below). 1 The resources are equipartitioned between users. <!-- 1 Each group may define two *guest users* who may be an external user (i.e. not belonging to ETHZ, PSI, or !UniZ). * The guest user will not get own resources, but he can use the group's resources * The group's Responsible User is responsible for the guest user. * The Guest user's account will be of limited duration --> ---++ User Interface ( UIs ) policies %STARTSECTION{name="UisPerGroup" type="section"}% | *OS* | *UI Hostname* | *users group* | *Notes* | | RHEL7 | t3ui01 | PSI | 128GB RAM, 72cores, 5TB =/scratch= | | RHEL7| t3ui02 | ETHZ | 128GB RAM, 72cores, 5TB =/scratch= | | RHEL7 | t3ui03 | UNIZ | 128GB RAM, 72cores, 5TB =/scratch= | %ENDSECTION{name="UisPerGroup" type="section"}% ---++ Home policies * Every user has %GREEN% home directory /t3home/${USER} with default 10GB quota %ENDCOLOR% for development of software, documentation, etc.</br> It's configured with 1 daily, 1 weekly and 1 monthly snapshots placed beyond quota limit at /t3home/username/.snapshot </br> To check your quota allotment use the following command: <pre> ~% quota -s -f /t3home Disk quotas for user username (uid user_id): Filesystem blocks %GREEN%quota %ENDCOLOR% limit grace files quota limit grace t3nfs:/t3/home1 704M %GREEN% 10240M %ENDCOLOR% 11264M 927 4295m 4295m </pre> * For big size files there is %BLUE% /work/${USER} volume with effective space ~100GB%ENDCOLOR% and 2 daily snpashots. </br> =/shome= is a link to =/work= </br> Snapshots are a part of work quota. In a case quota is completely filled only administrator is in charge to help. Requests must be sent to the admin mailing list.</br> ---++ UIs /scratch and /tmp usage Sometimes shared working =/tmp= or the =/scratch= partitions of UIs and WNs are full because some user had filled them with big and later forgotten files or simply because a job went crazy. There was a clear users requirement to manage this space by themselves, so that there is no automatic cleaning. Please clean it timely and remember that */scratch is the least protected area and doesn't dedicated to keep important data for a long*. If you discover an abuse, write or call your colleague and invite him/her to cleanup. Otherwise your peers work could be blocked. Administrators can help when group members are still interested in outdated user files presence in scratch. In this case the owner has to be explicitly changed to a new responsible person.
This topic: CmsTier3
>
WebHome
>
Tier3Policies
Topic revision: r63 - 2019-12-18 - NinaLoktionova
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback