Quest and Kellogg Linux Cluster Downtime, December 14 - 18.
Quest, including the Quest Analytics Nodes, the Genomics Compute Cluster (GCC), the Kellogg Linux Cluster (KLC), and Quest OnDemand, will be unavailable for scheduled maintenance starting at 8 A.M. on Saturday, December 14, and ending approximately at 5 P.M. on Wednesday, December 18. During the maintenance window, you will not be able to login to Quest, Quest Analytics Nodes, the GCC, KLC, or Quest OnDemand submit new jobs, run jobs, or access files stored on Quest in any way including Globus. For details on this maintenance, please see the Status of University IT Services page.
Quest RHEL8 Pilot Environment - November 18.
Starting November 18, all Quest users are invited to test and run their workflows in a RHEL8 pilot environment to prepare for Quest moving completely to RHEL8 in March 2025. We invite researchers to provide us with feedback during the pilot by contacting the Research Computing and Data Services team at quest-help@northwestern.edu. The pilot environment will consist of 24 H100 GPU nodes and seventy-two CPU nodes, and it will expand with additional nodes through March 2025. Details on how to access this pilot environment will be published in a KB article on November 18.
How to check allocation resources, expiration dates, and project members.
Allocation Resource Management
Add People to an Allocation
Use the Join an Existing Allocation form. The Allocation Manager for the allocation will be notified. Individuals added to an allocation will have access to the /projects/<allocationID> directory, but they will have their own home directory.
Renew an Existing Allocation or Create a New Allocation
Use the appropriate Research Allocation Original or Renewal Request form for your allocation type (I or II).
List Allocation Members
Display all current members of the allocation:
module load utilities
grouplist <allocationID>
Check Allocation Resources
You can find out your allocations by using groups command on Quest. The output of this command will include your NetID and the IDs of allocations that you belong.
To check the storage use of /projects/<allocationID> and allocation expiration:
checkproject <allocationID>
Example Output
$ checkproject <allocationID>
====================================
Reporting for project <allocationID>
------------------------------------
1 GB in 4623 files (0% of 1000 GB quota)
Allocation Type: Allocation I
Expiration Date: 2022-12-01
Status: ACTIVE
Compute and storage allocation - when status is ACTIVE, this allocation has compute node access and can submit jobs
------------------------------------
====================================