Managing Project Changes and Extensions¶
Project Changes¶
Personal Data Usage: Update GDPR status as needed.
Backup Status: Toggle backup settings for the $DATA volume. $HOME
is always backed up.
File Uploads: Add additional files (deletion or editing of existing files is not possible).
User Accounts: Manage user accounts as necessary.
Resource Pools and Extensions: Modify resource pools and request additional resources.
Additional Resource Pools¶
To extend the project to additional parts of the system, under 'Request resources from new resource pool' select the pool from the dropdown list and click 'request'
Project Extensions¶
At the top of each project part is a button 'request more resources' - click there to request additional resources for project runtime, core-h, or storage space. Activate the box on each desired resource (do not just use all without needing them) and change the amount if needed. Please also add a comment why the extension is needed. Then click on 'send request'.
Changes Performed by the VSC Team¶
Contact the VSC team for changes such as project manager, project name, and project group memberships.
The VSC team can also add secretaries to the project, who have similar rights to the project manager.
Project Lifecycle Notifications¶
Core Hours¶
90% Usage: A warning email will be sent.
100% Usage: Another email will be sent, and the project will be set to idle priority, affecting job scheduling.
Extension: Request an extension as necessary. Testprojects only get more core-h in special circumstances.
Number of Files (independent for $DATA and $HOME)¶
90% Quota: A warning email will be sent.
100% Quota: A notification will be sent, preventing the creation of new files.
Extension: Request additional file storage if needed.
Volume Size (independent for $DATA and $HOME)¶
90% Quota: A warning email will be sent.
100% Quota: A notification will be sent, preventing further file creation.
Extension: Request an extension for the $DATA volume size if
necessary. This is not possible for $HOME.
Project Expiry¶
One Month Before Expiry: A notification email will be sent.
Day of Expiry: Another email will be sent. The project remains functional, but new users cannot be added.
One Month After Expiry: A notification will inform you that job submissions are disabled. Currently running jobs will finish.
Two Months After Expiry: A reminder email will prompt you to back up any data you wish to retain.
Three Months After Expiry: User logins will be disabled. It is crucial to back up all relevant data before this deadline.
Extension: Request an extension if required, even post-expiry. Test projects can only be extended for short periods (30-60 days), while other projects may be extended up to one year.
Auto-Extension: Projects with significant remaining core hours will be automatically extended for six months to ensure uninterrupted access.
For further assistance, please contact us via the service page.