Feature #41239
open
- Subject changed from mgr/orchestrator: support creating OSDs on Persistent volumes to mgr/orchestrator: support creating OSDs on Persistent Volumes
- Project changed from mgr to Orchestrator
- Category deleted (
orchestrator)
- Subject changed from mgr/orchestrator: support creating OSDs on Persistent Volumes to mgr/rook: support creating OSDs on Persistent Volumes
- Category set to mgr/rook
mgr/rook now needs to process proper drive groups.
Some thoughts:
- OSDSpec specifies an existing StorageClass, num OSDs per node, ...?
- mgr/rook triggers osd creation by provisioning PVs from that storageclass...
- add storageclass to OSDSpec (db/wal and/or data)
- OSDSpec: resulting osd crush class
- new dashboard UI required (Dashboard checks available devices)
- % Done changed from 0 to 60
- Parent task set to #52409
- Priority changed from Normal to High
Also available in: Atom
PDF