Both sides previous revision Previous revision Next revision | Previous revision |
abstract:farber:account:account [2018-05-21 18:38] – [Cluster accounts] anita | abstract:farber:account:account [2021-01-25 13:34] (current) – [Passwords] anita |
---|
====== Farber account requests ====== | ====== Farber account requests ====== |
| |
All Farber cluster accounts must be sponsored by a [[:abstract:farber:account:stakeholders/|Farber stakeholder]] for a particular //investing-entity//. | All Farber cluster accounts must be sponsored by a principle stakeholder, also known as a stakeholder, someone who is responsible for managing or purchased HPC resources on the Farber cluster. All account requests must be submitted by a stakeholder. If you not a stakeholder, then you may try to seek sponsorship from an existing [[:abstract:farber:account:stakeholders/|Farber stakeholder]] for a particular //investing-entity// (workgroup). |
| |
To request a Farber account to be added or removed, the Farber stakeholder may | A Farber stakeholder may request a Farber account to be added or removed by submitting a [[https://services.udel.edu/TDClient/32/Portal/Requests/ServiceDet?ID=23|Research Computing High Performance Computing (HPC) Clusters Help Request]] and click on the green **Request Service** button and complete the form including Farber and all of the sponsored users' full name and email addresses, and the investing-entity unique group name (workgroup) baseed on |
| |
* contact the principle stakeholder for the //investing-entity// on Farber and provide the sponsored users' full name and email address. | |
| |
or | |
| |
* submit a [[http://www.udel.edu/deptforms/it/research_computing/index.html|Research Computing Help Request]] specifying the problem details as ''High-Performance Computing'', ''Farber Cluster'', account type: ''UD or HPC Guest'', and the problem description should include the sponsored users' full name and email address, and the investing-entity unique group name (workgroup). | |
| |
| * **UD community members:** UDelNet ID and full name |
| * **Guests:** Full name and email address (preferably a university, institution or organization; not personal) |
===== Cluster accounts ===== | ===== Cluster accounts ===== |
| |
group-use policies for his/her sponsored users. | group-use policies for his/her sponsored users. |
| |
<note important> Principle stakeholder's can request to add or remove access for a sponsored user on his/her //investing-entity// by submitting a [[http://www.udel.edu/deptforms/it/research_computing/index.html|Research Computing Help Request]] selecting ''High-Performance Computing'' and appropriate cluster for problem details. Please include in the problem description to add or remove | <note important> Principle stakeholder's can request to add or remove access for a sponsored user on his/her //investing-entity// by submitting a [[https://services.udel.edu/TDClient/32/Portal/Requests/ServiceDet?ID=23|Research Computing High Performance Computing (HPC) Clusters Help Request]] and click on the green **Request Service** button and complete the form including Farber in the problem description to add or remove |
| |
* **UD community members:** UDelNet ID and full name | * **UD community members:** UDelNet ID and full name |
| |
</note> | </note> |
| |
| ==== UD accounts ==== |
| |
If you are a UD community member, your cluster username and password are the same as your UDelNet ID | If you are a UD community member, your cluster username and password are the same as your UDelNet ID |
and password. You may change your UDelNet ID or password on the [[http://www.udel.edu/network|UD network page]], but it is only synced at noon and midnight daily. | and password. You may change your UDelNet ID or password on the [[http://www.udel.edu/network|UD network page]], but it is only synced at noon and midnight daily. |
| |
| ==== Guest accounts ==== |
If you are not a UD community member, IT will create a username having the form //hpcguest//<<//uid//>>, and | If you are not a UD community member, IT will create a username having the form //hpcguest//<<//uid//>>, and |
an initial password for you. It is based on the unique, 4-digit numerical identifier IT assigns to you. You can [[https://www.hpc.udel.edu/user/password.php|change your password]] via[[http://www.hpc.udel.edu|UD IT HPC]] page. The new password will immediately take effect on HPC systems. | an initial password for you. It is based on the unique, 4-digit numerical identifier IT assigns to you. You can [[https://www.hpc.udel.edu/user/password.php|change your password]] via [[http://www.hpc.udel.edu|UD IT HPC]] page by clicking on the ''login'' button at the top of the page and enter your //hpcguest//<<//uid//>> and current password. The new password will immediately take effect on HPC systems. |
| |
Your password should always comply with UD's [[http://www1.udel.edu/security/bestpractices/passwords.html|password | ==== Passwords ==== |
recommendations]]. | Passwords for UD or guest accounts should always comply with UD's [[http://www1.udel.edu/security/bestpractices/passwords.html|password recommendations]]. |
| |
| ==== Account information ==== |
^Command ^Function ^ | ^Command ^Function ^ |
| ''hpc-user-info -a'' <<//username//>> |Display info about a user | | | ''hpc-user-info -a'' <<//username//>> |Display info about a user | |
<code bash>getent group it_css</code> | <code bash>getent group it_css</code> |
| |
Together, ''gentent group'' and ''hpc-user-info -a'' let you determine the identities of a group's members. | Together, ''gentent group'' and ''hpc-user-info -a'' let you determine the identities of a cluster group's members. |
| |
| To get complete information regarding the cluster group and members, you can use the command ''hpc-group-info''. The output of this command will list the cluster group's information (''description = ''//stakeholder//), along with every member in the group ([[abstract:farber:app_dev:compute_env#using-workgroup-and-directories|workgroup]]) and their account information (Username, Full Name, Email Address). |
| |
| ''hpc-group-info -a'' <<//investing-entity//>> |