Czars roles and responsibilities

Some users have the privilege to manage the computing resources allocated to their laboratory or their group, to give a new password to a user or to request new resources. These users are called czars in the CC-IN2P3 jargon. There are different types of czars whose roles apply to a laboratory and/or to a group:

  • account czar: he is responsible for the validation of request for accounts made for a laboratory or, in some case authorized by IN2P3, for non-CNRS collaborators of experiments.
  • password czar: he is responsible of the AFS passwords. He can reset it when a user has forgotten it. Usually a account czar is also password czar but this is not a rule.
  • request czar: he is responsible for the resources requests (CPU/GPU, storage) for his group.
  • storage czar: he is responsible of the storage spaces allocated to the group (THRONG, SPS, HPSS, iRODS)
  • computing czar (batch): he is responsible for the management of priorities within his group on the computing platform.

To have a group czars listed, you may use the command lines below from an interactive server (the -p option without any arguments will give the storage czars list):

% laboinfo -l <labo code> -p <czarType={password,requete,batch}>
% laboinfo -g <group name> -p <czarType={password,requete,batch}>

where “requete” stands for “request”.

Technical tasks

Creation of new accounts (account czar)

The account czar is the person who has been chosen by his laboratory leader to validate request for new account and laboratory change of a user. This czar does not have the necessary permissions to add a user to a group.

The form to request a new account is available at this address. The account request must be printed and signed by:

  • the laboratory leader;
  • the requesting user;
  • the account czar.

The czar must then send the scan of the signed document as an attached file to the user support.

For any operation on your account <username> please refer to the result of the command below:

% laboinfo -u <username> -p compte

For international collaborations, one of the account czar major roles is to request new accounts for people working in foreign laboratories, or non-CNRS staff.

Group change (account czar)

You can also contact your account czar when you want to switch group or add a group to your account. You must send an e-mail to your account czar with a copy to the computing czar of the new group. Your account czar will ask for your this modification via a ticket.

Laboratory change (account czar)

You must fill the same form for account request when you change lab. There is a check-box to indicate that it is for a change of laboratory and not for a new account. The account czar of your new laboratory will sign the request to validate the change.

Trainer (account czar)

Within the laboratories, the account czar is sometimes called “lab czar”. Very often, this czar has a role of trainer for new CC-IN2P3 users working in the same laboratory:

  • manage account opening requests;
  • manage group change requests;
  • train new users;
  • perform user or group registration requests in HPSS.

Password update (password czar)

The password czar has the privilege to change the password for a user belonging to the same laboratory. In order to identify your password administrators, use the following command from the interactive servers:

% laboinfo -l <lab code> -p password
% laboinfo -g <group name> -p password

For more information please read the paragraph Password modification by an adminisrator.

Resource requests (request czar)

The request czar makes the annual resource request for his group. This request is made in collaboration with the Support team of CC-IN2P3 in order to be as precise as possible in terms of computing and storage needs. The Support team enters this request, which is then arbitrated by the CC-IN2P3 management.

PBS ACL management (storage czar)

The storage czar is responsible for the management of the group disk space and its ACLs. Further details related to this topic can be found on the ACL management paragraph.

To know your storage czar name:

% laboinfo -g <group name> -p

THRONG space management (storage czar)

The THRONG space is not managed by any czar but by users. However your storage czar should be able to give you good advice for an efficient use of your that space.

SPS space management (storage czar)

The SPS is used to store large amount of data temporarily. This space is managed like the Unix directories /tmp or /scratch. When no more space is available, users are invited to clean up. The storage czar is responsible for this area and is entitled to manage quotas. He may give you advice on how to move and delete you data located in this area.

Computing czar description

The computing czar requests permission to provide users with access to the restricted queues. This request must be sent to the user support. The computing czar can also contact the Support team to boost a user’s production.

Some advice for czars

Account request

There is no need to double the request by sending the form by fax, a scan is enough. In case an account creation is delayed, update the ticket. Do not send e-mail to the CC-IN2P3 staff: always communicate via a ticket which guarantees the good handling of the request. Avoid manual overloading of the form, which prevents automatic processing. In case of error, or explanatory comment, submit a ticket. Do not accept logins such as abbreviation, nickname, fun, initials: they will be rejected, without second choice request.

Intermediate support

Try to be an intermediate support between your users and CC-IN2P3. Many requests can be solved locally, within the lab or the group. Regularly check the accounts of your laboratory and/or group and report the accounts to be deactivated. Consider revalidating an existing account that changes lab.

Recommended command to get information about the users of a laboratory or group:

% laboinfo -h

Get accounts inactive for more than 2 years (the -v option provides e-mail addresses):

% laboinfo -l <lab code> -b 2 -v
% laboinfo -g <group name> -b 2 -v
% laboinfo -l zz -g <group name> -b 2 -v  (for non-CNRS collaborator to a group)