mayadata-io / mayadata-io/cstorpoolauto
logic: associating blockdevices with storage
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
This is the current logic that is followed by default openebs operators to create CStor Pools.
err = blockdevice.
BuilderForAPIObject(bdObj).
BlockDevice.
ValidateBlockDevice(
blockdevice.CheckIfBDIsActive(),
blockdevice.CheckIfBDIsNonFsType(),
blockdevice.CheckIfBDBelongsToNode(poolValidator.nodeName))
However, cstorpoolauto does not make check for presence of file on the device. This issue should have the details if filesystem should be considered at all to select a device.
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.
Research direction
Start by reviewing the shown BlockDevice validation chain and the cstorpoolauto logic that associates devices with storage. Determine whether filesystem presence should affect device selection and what behavior is expected. Done means the decision is documented with corresponding validation and test requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100