-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
Not Selected
-
False
-
False
-
-
-
0
-
0
-
0% To Do, 50% In Progress, 50% Done
Description
Testing and any documentation to enable RHOSO support for the Ceph-9 release (RHCS9) as an external ceph cluster to enable customers on the latest RHCS major release.
- RHCS 9 GA was Oct 22 2025
- https://productpages.redhat.com/ceph-9-0/schedule/tasks/
Goals:
- Produce Internal doc on the process for bumping major release version
- Update upstream/pre-testing to validate ceph9
- upstream: change upstream operator CI, and devstack-plugin-ceph to upstream T (aka ceph 9)
- downstream: change at least 1 job to use ceph 9
- Provide any required RHOSO documentation for RHCS9 support
Documentation Considerations
- We may have known limitations (needs downstream ceph ga bits first and verify state), but we may need to allow support without Manila/CephFS initially
- Need to confirm there are not other needs for RHOSO documentation with RCHS9 and that it doesn't impact existing coverage of Ceph configuration or features like adoption.
- Greenfield support note
- RGW + TLS notes
- Ganesha limitation (possible)
Accept Criteria
- Enable Official support for
RHCS-9 - MVP is RBD block support
- Upstream and downstream test coverage is sufficient for regression coverage with the new release
Testing considerations:
- Current testing matrix integration:
- rhoso 18 greenfield: gamma 7, delta (ganesha+rgw) 8, epsilon (cinder) 7
- rhoso 18 adoption: gamma 7
- Component level : cinder+glance at 7
- considerations:
- bump delta to 9
- gamma greenfield to 8
- epsilon greenfield to 8
Open Questions
- If Manila or RGW not ready, do we release like last time with what's ready and follow up?
- Yes - would need to create a seperate initiative to cover as needed
- Do we have any dependencies on the Production RA for CI or ceph client changes?
- No, we keep client at 7 and we plan the update to 9 for 19
- Do we need a support enablement EPIC for RHCS9 specifically?
- Do we want to make the DOC epic more generic and capture any future needs there too?
- we can make the doc epic more generic and have stories for RGW, known issues and potential limitations