Differences

This shows you the differences between two versions of the page.

--- doku:projects [2023/08/10 12:19] – [Project extensions] goldenberg
+++ doku:projects [2024/02/20 20:26] (current) – [Project expiry] goldenberg
@@ Line 5: / Line 5: @@
 Go to [[https://service.vsc.ac.at|our service page]] and on the left side (Login for project managers), choose your organization. If it is not there, please contact us for an external access.
 Then log in using the credential from your organization.
+**Note:** If your organization is not in our list, go to https://idp.vsc.ac.at/simplesaml/module.php/selfregister/ and choose 'Register new account'.
+After you have done that, please tell us the username you created and we will add it to our system.
+Then you can use "IdP VSC" as organization to log in.
 ==== Request new project ====
@@ Line 115: / Line 119: @@
 To extend some of the resources of an existing resource pool, click on 'request more resources' at the top of that part. On the opened page, set those resource types you want to extend to 'yes' (leave all others on 'no') and enter the value you want to have ADDED to the current amount. You can add an explanatory comment as well. Afterwards click on submit.\\
 The following resource types can be extended:
-  * cpu-contingent in core-h: The amount on additional core hours. Depending on project type and amount, this has to be granted by part or all of the steering committee. For test projects, core-h are only extended for special reasons.
+  * **cpu-contingent in core-h:** The amount on additional core hours. Depending on project type and amount, this has to be granted by part or all of the steering committee. For test projects, core-h are only extended for special reasons.
-  * project end in days: The number of days the project should be extended after the project end date. Depending on the project type, this has to be granted by part of the steering committee. Please note that test projects are only extended for a limited time, and all other projects (except private) are only extended for a year at a time.
+  * **project end in days:** The number of days the project should be extended after the project end date. Depending on the project type, this has to be granted by part of the steering committee. Please note that test projects are only extended for a limited time, and all other projects (except private) are only extended for a year at a time.
-  * \$DATA inodes or \$HOME inodes in # of files: The additional amount of files that can be stored in the respective volume.
+  * **\$DATA inodes or \$HOME inodes in # of files:** The additional amount of files that can be stored in the respective volume.
-  * \$DATA size or \$HOME size in GB: the maximum size of the respective volume. HOME will only be extended for exceptional reasons and is otherwise fixed.
+  * **\$DATA size or \$HOME size in GB:** the maximum size of the respective volume. \$HOME will only be extended for exceptional reasons and is otherwise fixed.
+==== Changes done by the VSC team ====
+Some changes in the project can only be done by the VSC team. Please contact us if that is needed.\\
+These changes are for example the project manager, project name, project group memberships (access to certain software or volumes for the entire project)\\
+The VSC team can also add secretaries to a project - these are persons that have similar rights as the project manager. In contrast to the manager, several secretaries are possible.
+===== Project lifecycle =====
+During the runtime of a project, you will or might get various reminder or warning mails:
+==== core hours ====
+There will be a first warning mail when the core hours in your project are **90% used up**. Please note that the mail is sent at a fixed time of the day, which means in the time between crossing the 90% threshold and the mail being sent, the use might already be higher.
+When the core-h are used up to **100%**, there will be another mail. This will also result in your project being set to idle priority. This means only the idle queues on the cluster are available. These queues have a low priority and only allow jobs to run, when no one else needs the respective nodes. Which in turn greatly impacts the chance for running jobs.
+It is then highly recommended to request an extension. Funded and internal projects can always extend as long as they are running, external projects need an appropriate quote. In testprojects, core-h are only extended in special circumstances. Note that private projects do not count core-h at all.
+==== number of files ====
+When the number of files (which equals the number of inodes) in either \$HOME or \$DATA reaches **90% of the allowed quota**, a warning mail is sent. As with core-h, the actual value can be higher as the mail is sent some time after the threshold is reached.
+Another mail is sent upon reaching **100%** - at that point, no more files can be created in the affected volume, preventing further work or sometimes even login. In that case, delete any files not needed and if that is not sufficient, request an extension. Any type of project can get an extension in files.
+**Note:** the volumes \$HOME and \$FILE are handled independently, so mails can be received for both.
+==== volume size ====
+When the size of the data in either \$HOME or \$DATA reaches **90% of the allowed quota**, a warning mail is sent. As with core-h, the actual value can be higher as the mail is sent some time after the threshold is reached.
+Another mail is sent upon reaching **100%** - at that point, no more files can be created in the affected volume, preventing further work or sometimes even login. In that case, delete any files not needed and if that is not sufficient, request an extension. Any type of project can get an extension in size on \$DATA up to 100TB. Higher values are possible after discussion with us.
+\$HOME cannot be extended, except for very special circumstances, such as more than 20 users in a project. Therefore, put all research data in $DATA.
+**Note:** the volumes \$HOME and \$FILE are handled independently, so mails can be received for both.
+==== Project expiry ====
+**Expiry:** About a month before a project expires, you are sent a notification mail about said expiry. Another mail is sent on the day of expiry. As soon as a project is expired, it is still possible to work normally, including job submission. However, new user can no longer be created.
+**Job submission disabled:** One month after project expiry, a mail is sent about job submissions being disabled. From that point on, jobs can no longer be submitted to the clusters. Jobs that are running at that time are not broken off.
+**Backup relevant project data:** Two month after project expiry, a mail is sent to warn you to backup any data from your project that you want to keep. The mail says data retention is only guaranteed until three months after project expiry. For details about data see the next paragraph.
+**Login disabled:** Three month after job submission, a mail is sent informing about login being disabled. At that point, all user logins to the clusters belonging to that project are disabled. So far, all data belonging to a project was kept indefinitely after the project ran out - but this can not be guaranteed as total storage space might run out. It is therefore highly recommended to back up all relevant data before that point.
+If the project shall continue, an extension can be requested. That can even be done after the project has run out. Testprojects can only be extended for short times (30 - 60 days usually), other projects for a maximum of one year at a time.
+**Auto-extension:** If a project (that is neither test nor private) has a large amount of core-h left available, it is automatically extended once for 6 month.