hpc documentation

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Caviness account requests ======

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 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
  * **Guests:** Full name and email address (preferably a university, institution or organization; not personal)

in the description.
===== Cluster accounts =====

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
//investing-entity// (workgroup) consists of the stakeholders who combined funds to purchase a particular
compute node or set of nodes. Each workgroup has a //principal stakeholder// who is the
administrative point of contact for its compute nodes.

There are two types of cluster accounts: //stakeholders// and //sponsored users//. Sponsored users
are researchers having at least one stakeholder willing to share his/her cluster resources
(compute nodes, storage allocation).

For each workgroup, the principal stakeholder is responsible for establishing and enforcing
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// (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
  * **Guests:** Full name and email address (preferably a university, institution or organization; not personal)

in the description.
</note>

==== UD accounts ====

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 [[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 ====
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 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.

==== Passwords ====
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 ^
| ''hpc-user-info -a'' <<//username//>> |Display info about a user |
| ''hpc-user-info -h''            |Display complete syntax |

For example,
<code bash>
[traine@caviness ~]$ hpc-user-info -a traine
full-name = Student Training
last-name = Student Training
home-directory = /home/1201
email-address = traine@udel.edu
</code>


===== Cluster groups =====

The cluster groups of which you are a member determine which computing nodes, job queues, and
storage resources you may use. Each group has a unique descriptive group name (//gname)//. There are
two categories of group names: //class// and //investing-entity//.

**//The class category//**:** **All users belong to the group named //everyone//. Members of the UD
community also belong to the group named //ud-user//. Non-UD users are members of the group named
//hpc-guests//. Other group names currently include //facstaff//, //students//, and
//stakeholders//.

**//The investing-entity category//**: Each investing-entity has a unique group name (e.g., //nanotech//
or the principal stakeholder's username) also referred to as [[abstract:caviness:app_dev:compute_env#using-workgroup-and-directories|workgroup]]. The investing-entity's stakeholders and its sponsored
users are members of that cluster group. To see the usernames of all members of an
investing-entity's group, type the ''getent group'' <<//investing_entity//>> command.

Use the command ''groups'' to see all of your groups. The example below is for user ''traine''

<code bash>
$ groups
everyone ud-users students it_css
</code>

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).

''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.