7 am – 12 am Tuesday July 3rd, storage systems for the pegasus compute cluster, apollo, and visx will undergo hardware maintenance.
During this maintenance period, pegasus batch execution and login nodes will be unavailable – as will the gateway (gw.ccs.miami.edu), apollo, and visx systems.
Due to financial decisions made at the Miller School of Medicine (MSOM), open access on both Pegasus and Bigfoot will no longer be available to MSOM faculty, staff, and students effective October 31, 2017.
Read the full contents for details about how this will affect your CCS account.
CCS Advanced Computing invites you to connect with the Advanced Computing community on Slack: http://umadvancedcomputing.slack.com
The Advanced Computing community Slack channels provide a place for user discussions, information sharing, and informal announcements about CCS resources and developments. All users with an @miami.edu or @umiami.edu email address can create a Slack account in UM Advanced Computing.
CCS Advanced Computing resources are open to all University of Miami employees and students at the RSMAS and CG campuses. Use of CCS resources is governed by University of Miami Acceptable Use Policies in addition to CCS AC policies, terms, and conditions. CCS Account Registration CCS Project Request CCS Software Request
- To qualify for a CCS account, you must be affiliated with the University of Miami. All CCS accounts must be linked with a valid corresponding University of Miami account.
- Suspended accounts cannot submit jobs to the Pegasus cluster. Suspended accounts will be disabled after 90 days.
- Disabled accounts cannot log into the Pegasus cluster.
- Disabled account data will be deleted after 30 days.
- All users of the Pegasus supercomputer are required to have a CCS account.
- All SSH sessions are closed automatically after 30 minutes of inactivity.
- No backups are performed on Pegasus file systems.
- CCS does not alter user files.
- Jobs running on the Pegasus cluster may be terminated for:
- using excessive resources or exceeding 30 minutes of CPU time on Pegasus login nodes
- failing to reserve appropriate LSF resources
- backgrounding LSF processes with the & operator
- running on inappropriate LSF queues
- running from data on
The CCS account responsible for those jobs may be suspended.
- Pegasus users with disabled CCS accounts must submit a request to firstname.lastname@example.org for temporary account reactivation.
- Active Pegasus users are allocated a logical home directory area
/nethome/username, limited to 250GB.
- Active projects can be allocated scratch directories:
/scratch/projects/projectID, intended for compiles and run-time input & output files. Disk allocations on Pegasus are only for data currently being processed. Files on
/scratchare subject to purging after 21 days.
- Data for running jobs must be staged exclusively in the
/scratchfile system. CCS accounts staging job data in the
/nethomefilesystem may be suspended.
- Prior to joining a project, users share the default Pegasus scratch allocation:
- Both home and scratch are available on all nodes in the Pegasus cluster.
- Accounts exceeding the 250GB home limit will be suspended. Once usage is under 250GB, the account will be enabled in one business day.
Projects & Resources
- Pegasus cluster resources are assigned and managed on a project basis for collaborative work.
- Any faculty member or PI can request a new project & resource allocation.
- Project allocations are granted by fiscal year. Running priority drops for projects exceeding their allocations.
- The allocations committee requires start and end dates for all project requests with large resource requirements.
More information about projects: Projects
- Users are free to install software in their home directories on Pegasus. See our Installing Software documentation for reference.
- Pegasus software requests are reviewed quarterly. Global software packages are considered only when a minimum of 20 users require them.
More information about software: Software on Pegasus