ceph.conf per ceph cluster
- Dominant language
- Go
- Stars
- 1.6k
- Forks
- 617
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 43
Description
# Describe the feature you'd like to have #
Having a different ceph.conf per ceph cluster or clusterID cephcsi is managing.
# What is the value to the end user? (why is it a priority?) #
This helps users to have a configuration specific to the ceph cluster and need not worry about all the clusters.
How would the end user gain value from having this feature?
This helps users to have a configuration specific to the ceph cluster and need not worry about all the clusters.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how cephcsi identifies a cluster or clusterID and how its ceph.conf configuration is currently selected. Define the configuration scope needed for each Ceph cluster, then verify that settings for one cluster do not affect the others.
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
- 20/100