mayadata-io / mayadata-io/d-operators
proposal(ndm): reserve blockdevices before their discovery
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Problem Statement: As a developer, I want to reserve NDM exposed BlockDevice resource for use by the operators that are initiated the creation of this BlockDevice.
Possible Solution: In order to achieve this, NDM should reserve the BlockDevice even before this BlockDevice gets discovered. NDM might introduce a new CR called BlockDeviceReserve that will have necessary details of the BlockDevice that is supposed to be discovered in the future. NDM on its part when discovers a BlockDevice can run through additional logic that tries to map the BlockDeviceReserve against this newly discovered BlockDevice. If a match is found, it should mark this BlockDevice as reserved by associating this BlockDevice with BlockDeviceReserve's UID. Operators can then claim the BlockDevice via BlockDeviceClaim with the latter having the BlockDeviceReserve UID.
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
No files or tests are named. Start by locating the NDM controller, BlockDevice discovery handling, and existing BlockDeviceClaim definitions, then determine how a future BlockDeviceReserve would be represented and matched. Done means a reserve can identify a future BlockDevice and an operator can claim it through the reserve UID.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100