OSD expansion testing
Open
- Dominant language
- Python
- Stars
- 307
- Forks
- 151
- Avg merge
- 14d 23h
- Merged PRs (30d)
- 1
Description
The current recovery machinery for CBT marks an OSD or group of OSDs out, then later marks it back in. It would be great is there was a way to mark an OSD or group of OSDs out, destroy them, then add them back in to the cluster.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating CBT's recovery machinery for marking OSDs or OSD groups out and back in, then trace how those operations interact with cluster state. Define the workflow so an OSD or group can be marked out, destroyed, and added back, and verify that the expansion scenario is covered by the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100