====== DARWIN account requests ====== ===== UD allocations ===== A UD allocation((For more information about the type of UD allocations that can be requested and how to apply please see the [[https://docs.google.com/document/d/1yO9issKJ2klPVa_rvFrsMM0GHth3Z3B-OEOypwTN3bc/edit?tab=t.0#heading=h.kf4wo65fvvyo|UD DARWIN Allocations Information and Guidelines]] document.)) provides access to DARWIN resources for UD faculty or staff acting as the Principle Investigator (PI) and users sponsored by that PI. If you do not have an active allocation, the following forms can be used to request an allocation: * [[https://docs.google.com/forms/d/e/1FAIpQLSfM5tkR_HtxRFWTj68rdEVZcJeJ5Z3xkETnZIGt8rxbyunH6w/viewform|Startup]] for first-time users (to become familiar with the DARWIN system); can be transformed into a Research allocation * [[https://docs.google.com/forms/d/e/1FAIpQLSdvCx_zPCW1kc0wlsn_wBH1aP7Xp6jOHTTx0dut__vA5bbO2g/viewform|Education]] for work associated with a UD class; the allocation period is strongly-tied to the beginning and end of an academic term * [[https://docs.google.com/forms/d/1mxqfRUA3XnXw_MEsypPxKU4HLg6jwWDZRrn7bpxV5ao/edit|Research]] for all other cases Please allow a minimum of two weeks processing of an allocation request. After being granted a UD allocation, a //workgroup// is created on the cluster. The PI is the administrative point of contact for that workgroup and is responsible for establishing and enforcing group-use policies for workgroup users. Modifications to an active allocation prior to expiration, such as * extending the expiration date to allow more time for completing work * for a Research allocation: * renewal (new CPU/GPU/storage resources in a subsequent time period following expiration) * additional resources (credit of CPU/GPU/storage resources to current time period) should use the [[https://docs.google.com/forms/d/1R9Nnov1cxoG6IQk39UXgerqPWyi8-q7zeOKLtL49D48/viewform|Allocation Extension form]]. ==== UD allocation accounts ==== The PI associated with an active allocation should request the addition and removal of workgroup users by submitting a [[https://services.udel.edu/TDClient/32/Portal/Requests/ServiceDet?ID=23|Research Computing High Performance Computing (HPC) Clusters Help Request]]. Click the green **Request Service** button and complete the form including //DARWIN Account Request// in the short description, selecting //How to use it?// for the type of information you are looking for, and in the description indicate the workgroup name and users to add or remove. There are two types of user that can be added: * **UD community members**: provide the UD email address and full name * **HPC guests**: provide the full name and email address (preferably a university, institution or organization; not personal) A UD community member's account will reuse the same UDelNet ID and password used on other UD systems. When the UD community member's UDelNet ID or password is changed via the [[https://www.udel.edu/myudsettings|My UD Settings page]], the change will be reflected on DARWIN by the next day (after 12:15 a.m.). In the meantime, the old UDelNet ID or password should continue to be used on DARWIN. HPC guest accounts are distinguished by a username having the form //**hpcguest**////«uid-number»// and an initial password sent in a PDF when the account is created. The //«uid-number»// is a unique 4-digit numerical identifier associated with the account. HPC guests can [[https://www.hpc.udel.edu/user/password.php|change their password]]: click the ''login'' button at the top of the page and enter the //**hpcguest**////«uid-number»// and current password to login. Upon successful completion of the password page, the new password will take effect immediately on DARWIN. Passwords should always comply with UD's [[http://www1.udel.edu/security/bestpractices/passwords.html|password recommendations]]. ==== UD allocation workgroups ==== The workgroups of which a user is a member determine which computing nodes, job queues, and storage resources that user may use. Each workgroup has a unique descriptive group name (//gname)// chosen by the PI. A user can generate a list of the workgroups of which they are a member using the ''workgroup'' command: $ workgroup -q workgroups 1002 it_css Subsequently, a list of all members of a workgroup can be generated using the ''hpc-group-info'' command: $ hpc-group-info -a it_css name = it_css gid-number = 1002 description = John Huffman member = traine; Student Training; traine@UDel.Edu member = trainf; Faculty Training; trainf@UDel.Edu There are additional //user-class// groups of which the user may also be a member: * //everyone//: this is the default group for all DARWIN users * //ud-user//: every UD community member user is a member of this group * //hpc-guests//: every HPC guest user is a member of this group * //facstaff//: every non-student user is a member of this group * //students//: every student user is a member of this group The user-class groups are used to restrict access to software, for example. ===== ACCESS allocations ===== An ACCESS allocation provides DARWIN resources to a PI who has been granted an overarching allocation within the NSF ACCESS computational federation. See the [[https://allocations.access-ci.org/|ACCESS Allocations portal]] for more information. After being granted an ACCESS allocation on DARWIN, a //workgroup// is created on the cluster. The PI is the administrative point of contact for that workgroup and is responsible for establishing and enforcing group-use policies for workgroup users. ==== ACCESS allocation accounts ==== Once an ACCESS PI has been granted a DARWIN workgroup the [[https://allocations.access-ci.org/|ACCESS Allocations portal]] should be used to add or remove user accounts: * If the individual has an ACCESS portal user account, the existing account ID should be used * If the individual does **not** have an ACCESS portal user account, the individual should visit the [[https://identity.access-ci.org/new-user|ACCESS User Registration]] page to create one and provide the chosen account ID with the PI It may take //up to 10 business days// to process an ACCESS allocation account request on DARWIN. ACCESS users will be assigned a username having the form **xsedeu**//«uid-number»//. The //«uid-number»// is a unique 4-digit numerical identifier assigned to the user. An email with the subject "''[darwin-users] New DARWIN ACCESS (XSEDE) account information''" will be sent to the ACCESS user once the account is established on DARWIN. Directions in the email **MUST** be followed to set a password on the account prior to accessing any cluster resources; see [[abstract:darwin:system_access:system_access#logging-on-to-darwin-for-access-xsede-allocation-users | Logging on to DARWIN for ACCESS (XSEDE) Allocation Users]] for details. ==== ACCESS allocation workgroups ==== The workgroups of which a user is a member determine which computing nodes, job queues, and storage resources that user may use. Each workgroup has a unique descriptive group name (//gname)// chosen by the PI. A user can generate a list of the workgroups of which they are a member using the ''workgroup'' command: $ workgroup -q workgroups 1120 xg-tra180011 Subsequently, a list of all members of a workgroup can be generated using the ''hpc-group-info'' command: $ hpc-group-info -a xg-tra180011 name = xg-tra180011 gid-number = 1120 description = Student Training member = xsedeu1201; Student Training; traine@udel.edu There are additional //user-class// groups of which the user may also be a member: * //everyone//: this is the default group for all DARWIN users The user-class groups are used to restrict access to software, for example.