| Both sides previous revision Previous revision Next revision | Previous revision |
| abstract:caviness:account:account [2021-01-25 13:34] – anita | abstract:caviness:account:account [2024-04-15 15:47] (current) – [UD accounts] anita |
|---|
| All Caviness 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 Caviness 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:caviness:account:stakeholders/|Caviness stakeholder]] for a particular //investing-entity// (workgroup). | All Caviness 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 Caviness 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:caviness:account:stakeholders/|Caviness stakeholder]] for a particular //investing-entity// (workgroup). |
| |
| A Caviness stakeholder may request a Caviness 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 Caviness and all of the sponsored users' full name and email addresses, and the investing-entity unique group name (workgroup) baseed on | A Caviness stakeholder may request a Caviness 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 Caviness Account Request in the title, select How to use it? for the type of information you are looking for, and include the workgroup name (i.e. ''workgroup -q workgroups'') and all of the sponsored users' full name and email addresses for |
| |
| * **UD community members:** UDelNet ID and full name | * **UD community members:** UDelNet ID and full name |
| * **Guests:** Full name and email address (preferably a university, institution or organization; not personal) | * **Guests:** Full name and email address (preferably a university, institution or organization; not personal) |
| | |
| | in the description. |
| ===== Cluster accounts ===== | ===== Cluster accounts ===== |
| |
| The cluster's compute nodes are organizationally identified by UD research | The cluster's compute nodes are organizationally identified by UD research |
| group names. A //stakeholder// is a UD researcher who contributed financially to a node's purchase. An | group names. A //stakeholder// is a UD researcher who contributed financially to a node's purchase. An |
| //investing-entity// consists of the stakeholders who combined funds to purchase a particular | //investing-entity// (workgroup) consists of the stakeholders who combined funds to purchase a particular |
| compute node or set of nodes. Each investing-entity has a //principal stakeholder// who is the | compute node or set of nodes. Each workgroup has a //principal stakeholder// who is the |
| administrative point of contact for its compute nodes. | administrative point of contact for its compute nodes. |
| |
| (compute nodes, storage allocation). | (compute nodes, storage allocation). |
| |
| For each investing-entity, the principal stakeholder is responsible for establishing and enforcing | For each workgroup, the principal stakeholder is responsible for establishing and enforcing |
| 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 [[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 Caviness 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// (workgroup) 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 Caviness Account Request in the title, select How to use it? for the type of information you are looking for, and include the workgroup name (i.e. ''workgroup -q workgroups''), and which users to add or remove by providing |
| |
| * **UD community members:** UDelNet ID and full name | * **UD community members:** UDelNet ID and full name |
| * **Guests:** Full name and email address (preferably a university, institution or organization; not personal) | * **Guests:** Full name and email address (preferably a university, institution or organization; not personal) |
| |
| | in the description. |
| </note> | </note> |
| |
| ==== UD accounts ==== | ==== 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 UD allocation 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 [[https://www.udel.edu/myudsettings|My UD Settings page]], but it is only synced at 12:15AM EST daily on Caviness, so basically the next day. In the meantime, you may continue to use the old password on Caviness until the update occurs. |
| |
| ==== Guest accounts ==== | ==== Guest accounts ==== |
| Passwords for UD or guest accounts should always comply with UD's [[http://www1.udel.edu/security/bestpractices/passwords.html|password recommendations]]. | Passwords for UD or guest accounts should always comply with UD's [[http://www1.udel.edu/security/bestpractices/passwords.html|password recommendations]]. |
| |
| ==== Account informataion ==== | ==== 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 | |
| investing-entity's group, type the ''getent group'' <<//investing_entity//>> command. | investing-entity's group, type the ''getent group'' <<//investing_entity//>> command. |
| |
| For example, the command below will display the usernames of the ''it_css'' members. | Use the command ''groups'' to see all of your groups. The example below is for user ''traine'' |
| |
| <code bash>getent group it_css</code> | <code bash> |
| | $ groups |
| | everyone ud-users students it_css |
| | </code> |
| |
| 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 workgroup and members, you can use the command ''hpc-group-info''. The output of this command will list the cluster workgroup's information (''description = ''//stakeholder//), along with every member in the workgroup ([[abstract:caviness:app_dev:compute_env#using-workgroup-and-directories|workgroup]]) and their account information (Username, Full Name, Email Address). |
| | |
| 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:caviness:app_dev:compute_env#using-workgroup-and-directories|workgroup]]) and their account information (Username, Full Name, Email Address). | |
| |
| ''hpc-group-info -a'' <<//investing-entity//>> | ''hpc-group-info -a'' <<//investing-entity//>> |
| | |
| | For example, using the following command |
| | |
| | <code bash>hpc-group-info -a it_css</code> |
| | |
| | will display all information about workgroup ''it_css'' and all members. To get help, use ''hpc-group-info --help'' to see all options. |
| | |