Create explanatory model for new storage platforms
Open
@iam4tune is already working on this.
Since Jul 18, 2025.
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?
The new storage platforms will have three parts. My current mental model is memory and storage in a computer, but we need to translate this for non-technical audiences.
- What we call "GPFS" or "Cheaha Storage"
- Has a component with the technical name GPFS. We can think of this as a cache that stores the most frequently used data.
- Has a component with the technical name Ceph Pool. We can think of this as the system RAM.
- Data is moved into the cache when it is used, and moved back to RAM when it has not been used recently, and something else takes its place.
- Data coming from "RAM" to "cache" may take some time, causing a small amount of latency the first time the data is accessed. In most cases this shouldn't be an issue.
- Transfers happen automatically.
- We won't be doing manual transfers.
- Data must be in the cache to be processed on Cheaha.
- What we call "Long-Term Storage" or "LTS".
- We can think of this as a hard drive. Data has to be moved from the hard drive into cache to be processed.
- Transfers are not automatic and must be initiated by researchers intentionally.
- Transfers can be partially automated as part of a processing pipeline or workflow.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.