SovereignCloudStack / SovereignCloudStack/cluster-stacks
Investigate cinder-csi PV placement
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
It was reported that sometimes cinder-csi could create persistent volumes in AZs different from existing nodes. Maybe it is connected to #154, or a specific cinder-csi setting needs to be set. Investigate, how cinder-csi PV placement works and if we can do something to prevent wrong PV placement. See e.g. ignore-volume-az option, availability(default nova) storage class parameter or allowedTopologies feature to learn more.
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 with the linked cinder-csi documentation on block storage, supported parameters, and topology, then compare the ignore-volume-az, availability, and allowedTopologies options with the reported placement behavior and issue #154. Document whether an existing setting or storage class configuration can prevent PVs from being placed in an AZ without suitable nodes.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100