uabrc / uabrc/uabrc.github.io

Boilerplate for adding storage FY24 Q1-Q3

Open
#658 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

style: article/section 📝 system: cheaha 🖧 system: storage 🛢
Dominant language
Python
Stars
24
Forks
15
Avg merge
10d 3h
Merged PRs (30d)
1

Description

What would you like to see added?

Boilerplate for adding storage FY24 Q1-Q3

Two options are available for expanding project storage. Storage purchased may be allocated to one or both options.

  1. Storage on LTS. Choose this if you want a place to put unchanging or rarely changing data, and old data that is rarely accessed, used, or processed. This is commonly used for large genomics datasets that don't change. Data on LTS can be copied onto Cheaha temporarily for processing, and we can show you how.

  2. Storage accessible on Cheaha. Choose this if you want a place to put data that changes more frequently or is frequently accessed, used, or processed. This option does not add to /data/project storage on GPFS, and is instead accessible through our CephFS storage. CephFS is side-by-side with /data/project at a different path on Cheaha. Note that CephFS data transfers are not as fast as GPFS, so if your workflow requires high IO performance, please be cautious about where to place your most-frequently accessed data. We can help with understanding how GPFS and CephFS interact with your workflow.

In both cases, here are the facts about purchasing storage:

  • New storage is purchased in whole storage nodes.
  • Each storage node has 133 TB of usable capacity.
  • Storage nodes are purchased at vendor cost; no markups added.
  • Purchased nodes are installed with existing nodes and maintained at the same service level for the duration of the vendor’s service contract, typically 5 years, the industry standard.
  • Actual cost varies depending on vendor quotes at the time of request.
  • Once an order has been placed, if there is enough system storage available, we can increase your allocation(s) regardless of hardware lead time.

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.

Research direction

No file, test, or documentation entry point is named. Start by locating the storage documentation section in this repository and compare its current structure with the requested FY24 Q1-Q3 boilerplate; done when the supplied storage options and purchasing facts are represented there.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.