Body
Quest and Kellogg Linux Cluster Downtime, March 22 - 31.
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, March 22, and ending approximately at 5 P.M. on Monday, March 31. 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
The RHEL8 Pilot Environment is available for use now.
Starting Tuesday, December 10, seventy of the latest Intel Emerald Rapids CPU nodes (128 cores and 512GB of RAM) will be available to the RHEL8 Pilot, significantly increasing the compute capacity of this environment. With this expansion, the pilot environment will consist of twenty-four NVIDIA H100 GPU nodes (totaling ninety-six H100 cards) and 140 CPU nodes totaling 12,600 cores. Quest users are encouraged to test their workflows in RHEL8 Pilot environment to prepare for Quest moving completely to RHEL8 in March 2025. Detailed instructions are available on how to submit jobs for the new Operating System in the Knowledge Base article, RHEL8 Pilot Environment.
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
------------------------------------
====================================