uabrc / uabrc/uabrc.github.io

Overall expectations of our services for researchers

Open
#963 1 comment 0 reactions 1 assignee View on GitHub

@wwarriner is already working on this.

Since Apr 16, 2025.

style: article/section 📝 system: identity-mgmt 🆔
Dominant language
Python
Stars
24
Forks
15
Avg merge
10d 3h
Merged PRs (30d)
1

Description

  • All RC services and platforms are centrally funded by UAB at 5x8 support (5 days per week, 8 hours per day).
  • Like all engineering and business ventures, IT groups must find an appropriate operating point for their purposes. The operating point involves a tradeoff among service quality, availability (uptime), and cost. Research Computing trades in availability for higher service quality and reduced cost. Increasing availability would mean less storage and fewer compute resources.
  • Across our four major services (Cheaha, Cloud.rc, LTS, GitLab) we average about 98% availability at less than 8% of the cost of comparable commercial cloud offerings. For comparison, NSF guidelines for "Advanced Computing System" awards require 95% availability.
  • On top of our low cost, we offer full-time facilitation, light consultation, and flexible problem solving at no additional charge.
  • If you need a higher level of service availability, we are willing to explore commercial cloud offerings with you. Please be mindful that our funding does not cover payments to commercial cloud vendors.

Summarizing: We offer abundant resources with 98% service availability at a fraction of the cost of commercial cloud. If you need higher availability, please contact us.

Source for NSF: https://www.nsf.gov/funding/opportunities/advanced-computing-systems-services-adapting-rapid-evolution/nsf24-583/solicitation, section V.A.2.c "Resource Reliability and Usability".

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.