New HLRN Project and Allocation Management

-- BerndKallies - 06 Jun 2008

On Wednesday, June 25 2008 afternoon a new HLRN Project and Allocation Management System will be set in motion.

Due to a complete design change, the following important policy changes take effect, which are of interest to every HLRN user and every HLRN project administrator:

Personal Project and Allocations

Old policy

  • Every new HLRN user got a so called "Schnupper-Account" (preliminary account).
  • The preliminary account was coupled with a limited allocation of 50 NPL per quarter.
  • This preliminary allocation was given to users which are not member of any project.
  • When a user entered a project, this allocation was taken away from the user.
  • When a user left a project, this allocation was granted again.
  • The maximum time this allocation was given was three quarters.
  • When a user did not enter a project during this time, the account of the user expired.

New policy

  • Every HLRN user will be member of its own personal project, as long as the user exists.
  • The project holds an allocation of 100 NPL per quarter, which is independent of other project memberships of the user.
  • The account of a user expires, when he was not member of any non-personal project for three quarters.

Number of Project Memberships

Old policy

  • Every HLRN user was member of exactly one or no project at a given time.
  • Project memberships were maintained by project administrators.

New policy

  • Every HLRN user is at least member of its own personal project.
  • In addition, every HLRN user may be member of an unlimited number of non-personal projects at a given time.
  • Project memberships of these projects are maintained by project administrators.

Default Project

Every batch job submitted on HLRN machines is accounted.

Every batch job carries an attribute, which states the project from which the job has to be accounted (LoadL: #@account_no, PBS-like: -A).

Old policy

  • A user was able to be member of only one project at the same time.
  • If a batch job did not state a project, the HLRN submit filter pushed the current project of the user into the job.
  • Thus, HLRN users usually did not care about #@account_no.

New policy

  • A user may be member of many projects.
  • If a batch job does not state a project, the HLRN submit filter looks for a default project of the job owner, and pushes this into the job.
  • The default project has to be set by the user itself, if he is member of several projects.
  • To do that, a WWW GUI is provided.
  • Thus, a HLRN user either has to take care about defining his default project correctly, or stating the correct one via #@account_no for every job.

Project Administrators

Every HLRN project has assigned administrators.

Project admins are able to maintain project memberships and to distribute project allocations among project members.

Old policy

  • Every user with a valid HLRN account and which knows the project password, was able to act as project admin for this project.

New policy

  • The role "project admin" for a project is coupled to privileged project members.
  • Every non-personal HLRN project has at least one member, which is enabled to act as project admin for this project.
  • A "project password" for interaction of project admins with the Project and Allocation Management System is not needed, and does not exist.
  • A project password is still needed for interaction with the database for Project Applications to the Scientific Board when submitting or editing project proposals.

Distribution of Project Allocations

The Scientific Board of HLRN reviews project proposals and grants allocations for projects on a quarterly base.

Old policy

  • The distribution of granted project allocations among project members was mandantory, even for projects with only one member.

New policy

  • The distribution of project allocations among project members is optional.
  • By default, project members share a quarterly project allocation on a first-come-first-serve base.
  • A project administrator may change this behaviour by switching to a distributed model for project allocations.
  • A project administrator then has to distribute project allocations among members by means of NPL for a current quarter, and by means of percentages for future quarters.
  • Project administrators are encouraged to use the help function of the new WWW GUI to become familiar with the new concept (currently available in german only).

WWW Portal

The new HLRN Project and Allocation Management System comes with a drastically changed portal for WWW access for project admins and users. The URL is

https://zulassung.hlrn.de/hprvw/

  • The portal is role-based.
  • Every user logs in with his HLRN user name and password.
  • Every user then gains access to GUIs that enable him to
    • view his state regarding project memberships
    • view available allocations and their usages
    • change his default project
  • If the user is a project admin for some project, additional GUIs are accessible that enable him to
    • view the state of his projects
    • add or delete project members
    • distribute project allocations among members

All forms previously used will be switched off.

If they are still accessible, they will have no effect on the HLRN machines.

Initial Database Content

Since the new policies are partially incompatible with the old ones, a one-time initialization of several user and project properties is necessary.

These will be set before June 25. Besides these, the switch to the new system is fully transparent to the user.

History

The new database contains all users, projects, project memberships, allocations, allocation usages, jobs since start of HLRN (since 2002).

It is synchronized with the old database regarding all current actions.

Personal Project

A personal project is created for every existing HLRN user, providing 100 NPL per quarter independent of other project memberships.

The name of the personal project is the name of the user.

The personal allocation is touched, if a user had batch jobs running in the current quarter without being member of a non-personal project.

The personal allocation is not touched otherwise.

Users that are currently locked because they overdrew their preliminary allocation of 50 NPL, are unlocked.

Default Project

The default project of every existing user will be set to the project, to which the user belongs on June 25.

This will be the personal project for every user, which does not belong to some other project.

The default project will be the current project for all other users.

The attribute #@account_no of batch jobs waiting in the queue will be reviewed by HLRN to reflect this change, and will be changed when necessary.

Project Administrators

Every non-personal project will have a project admin assigned.

The initial admin of a project is the HLRN user which applied for the project.

Every HLRN user which is chosen to be a project admin for some project will be informed by e-mail.

Assigned project admins are able to assign other project members to be project admins by using the appropriate WWW GUI.

Distribution of Project Allocations

All existing project allocations will be defined to be shareable among the project members on a first-come-first-serve base.

Existing shares for project allocations from the old database are not retained.

Users that are currently locked because they overdrew the project allocation share assigned to them are unlocked, if the overall project allocation permits.

A project admin may distribute project allocations again on behalf of its own by using the appropriate WWW GUI, if he feels that this is really needed.

Special Project bzz0001

The special project bzz0001 will not exist any longer.

The rules defined for members of this project are translated into rules for the corresponding personal project of the user.

No actions by current members of this project are necessary to retain their state.

When there are Problems

If you have questions or run into trouble, please contact your responsible HLRN consultant, or email to support@hlrn.de.


Created by BerndKallies

 
Norddeutscher Verbund für Hoch- und Höchstleistungsrechnen
Back to top of page