mayadata-io / mayadata-io/cstorpoolauto
bug: filter blockdevices that do not have any filesystem on them
Open
Nobody has claimed this yet.
bug
cspc controller
- Dominant language
- Go
- Stars
- 8
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Following is an example of BlockDevice that is fit to be considered to participate in building a CStor Pool, since it does not have any filesystem.
spec:
capacity:
logicalSectorSize: 512
physicalSectorSize: 0
storage: 107374182400
details:
compliance: ""
deviceType: ""
firmwareRevision: ""
model: PersistentDisk
serial: pvc-c1919d99-3295-11ea-a90b-42010a800016
vendor: Google
devlinks:
- kind: by-id
links:
- /dev/disk/by-id/scsi-0Google_PersistentDisk_pvc-c1919d99-3295-11ea-a90b-42010a800016
- /dev/disk/by-id/google-pvc-c1919d99-3295-11ea-a90b-42010a800016
- kind: by-path
links:
- /dev/disk/by-path/virtio-pci-0000:00:03.0-scsi-0:0:30:0
filesystem: {}
nodeAttributes:
nodeName: gke-amitd-dao-d-default-pool-fcc50975-fvsb
partitioned: "No"
path: /dev/sde
status:
claimState: Unclaimed
state: Active
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 locating the BlockDevice filtering or CStor Pool eligibility entry point and inspect how the empty filesystem field is handled. Done means BlockDevices with a filesystem are excluded from pool-building candidates; check whether the repository has relevant tests and add or run coverage for this example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100