Creating and Managing Projects at VSC

This website guides users through creating and managing projects on the VSC service platform. It starts with logging into the service page, followed by steps to request a new project, detailing the types of projects available, and adding necessary project details. The tutorial includes instructions on selecting appropriate resource pools, uploading required files, and the review process. It also covers adding users, managing project changes and extensions, and outlines the notification system for project lifecycle events, ensuring users are aware of their project's status and necessary actions to maintain smooth operation.

Navigate to our service page.

Select your organization from the list under 'Login for Project Managers' on the left side.

Log in using your organization's credentials.

• Note: If your organization is not listed, visit https://idp.vsc.ac.at/simplesaml/module.php/selfregister/ to register. After registering, inform us of your username, and we will add it to our system. You may then use “IdP VSC” as your organization for login.

Click 'Request Project' in the left menu bar.

Select the appropriate project type as listed below.

Provide a project title (it need not match any official title).

Specify the institute, subunit, or department for which the project is conducted.

The 'Parent Project' field should remain at default unless:

• You are initiating a new parent project for a new collaboration or a large project with multiple sub-parts → select 'create new parent project'.
• You are part of an existing parent project → select from the dropdown list.

Indicate whether the project involves Personal Data in accordance with GDPR.

Click 'Create'.

Test: For short-term test runs, with a limit of 90 days and 100,000 CPU core hours. Not billed or accounted.

Funded: Projects from organizations which have free access to VSC resources, if they are funded by agencies such as FWF, FFG, ERC, or federal states.

Internal: Projects funded through internal budgets, requiring peer review.

External: Projects from organizations without free VSC access, categorized as:

• External-Scientific: For scientific research with reduced core-hour rates.
• External-Commercial: For applied research or commercial purposes.

Application: Projects applying for funding, which reserve VSC resources in advance.

Private: Projects involving privately purchased hardware integrated into VSC systems.

Following project creation, you will receive a unique project ID and a dedicated project page.

Your affiliation and role as the project manager will be automatically assigned.

You will receive an email outlining the next steps.

On the project page, select 'Request Resources from a Resource Pool':

• VSC-4: Our older cluster featuring Intel nodes (48 cores, 96GB/384GB/768GB RAM). Recommended if Intel architecture is preferred.
• VSC-5: Our newer cluster with AMD nodes (128 cores, 512GB/1TB/2TB RAM), some Intel nodes(96 cores, 384GB RAM), and A40/A100 GPU nodes. Ideal for GPU use, AMD architecture, or if no specific requirements.
• LEONARDO-B: GPU Booster Module of the European Pre-Exascale cluster LEONARDO. Can only be requested if there is a specific call.

Click 'Request New Project Part' and input the required details:

• The start date is pre-set to the current date but may be adjusted if necessary.
• Specify the anticipated number of cores used in parallel (for feasibility assessment).
• List the software to be utilized.
• Use the comment section for any additional pertinent information.
• At the bottom, retain default settings unless specific adjustments are required. Resource types are explained here.

Click 'Submit Query' to create a project part for the selected resource pool.

CPU Contingent: Estimated CPU core hours required. Extendable during the project. Fixed at 100,000 hours for test projects. Not accounted for private projects.

Project End: Duration of the project in days from the start date. Extendable even post-expiration. Default is 366 days; test projects are limited to 90 days.

$DATA Inodes: Number of inodes in the DATA storage volume. Default is 1 million, extendable.

$DATA Size: Size of the DATA storage volume in GB. Default is 10TB, extendable up to 100TB. Larger sizes require discussion.

$HOME Inodes: Number of inodes in the HOME storage volume. Default is 1 million, extendable.

$HOME Size: Size of the HOME storage volume in GB. Default is 100GB, only extended for very specific exceptions.

If applicable, upload the necessary documents in the 'Files' section:

• Project description (2-4 pages). [every project type except test and private]
• Proof of funding for funded projects.
• Reviewer list (minimum of 3) for internal projects.
• Quota or contract for core hours for external projects.
• GDPR data handling contract if Personal Data is involved.

You will receive a confirmation email for each uploaded file.

Once all required files are uploaded (or if no files are needed), click the red bar at the top of the project part to request a technical review.

The VSC team will review the project to ensure feasibility and resolve any administrative or technical issues.

The VSC team will also create the necessary file directories for the project.

Internal projects will be sent to the listed reviewers.

Feedback from reviewers will be incorporated into the project evaluation.

Projects of types funded, internal (post-peer review), external, and application will be reviewed by the SC.

• For core-hour requests below 5 million, only the SC members of the requesting organization review the project.
• For requests above 5 million core-hours, the entire SC reviews the project.

Test and private projects are only subject to technical review.

You will receive an email notification once the project is approved.

Once the project is granted, create cluster user accounts as follows:

• Enter the user's first and last name, email address, and phone number (must be capable of receiving text messages).
  • If no SMS capable number can be provided, contact us for an alternative yubikey authorisation.
• Enter a unique username (only small letters and numbers or underscore are allowed) and a secure password (minimum of 10 characters, including one lowercase letter, one uppercase letter, one digit, and one special character).

Assign the user to the relevant resource pools.

The user will receive an email with instructions (password not included).

Users may now log into the cluster and commence work on the project.

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.

To extend the project to additional parts of the system, select 'Request More Resources' at the top of the project part.

Specify which resource types you wish to extend and provide additional values if needed. Submit your request for approval.

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.

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.

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.

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. Not possible for HOME.

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.