oxidecomputer / oxidecomputer/crucible
Advertise supported range of block / extent sizes
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
As mentioned in omicron#511, as well as RFD 29, Nexus needs to choose block sizes - and with the Crucible API, it also needs to choose extent sizes.
Currently, there is no feedback from the Crucible API regarding "what sizes are recommended" so these are fabricated up in Nexus-land - we're picking a block size of 4K and an extent size of 1MB.
Although Nexus can still be the ultimate arbiter of choosing block sizes, it would be handy if Crucible advertised a supported range (e.g., are 512 byte blocks supported?) that could be selected by an upper layer.
Contributor guide
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.
Research direction
Start by reading the Crucible API context in this issue and RFD 29, then review the linked omicron#511 discussion for the current block- and extent-size assumptions. Done means Crucible advertises the supported ranges so Nexus or another upper layer can select valid sizes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100