Feature #47507
closed
Added by Patrick Donnelly over 3 years ago.
Updated almost 3 years ago.
Description
teuthology currently has no support for verifying Ceph's rook functionality (through the orchestrator) works. We should correct this by setting up a minikube cluster on a single teuthology node, deploy latest Rook release, and deploy the version of Ceph being tested (which we now have containers automatically built for). Then, validate various orchestrator commands function correctly. Stretch goal: verify Ceph works on Rook generally with some workload testing.
Patrick Donnelly wrote:
teuthology currently has no support for verifying Ceph's rook functionality (through the orchestrator) works. We should correct this by setting up a minikube cluster on a single teuthology node, deploy latest Rook release, and deploy the version of Ceph being tested (which we now have containers automatically built for). Then, validate various orchestrator commands function correctly. Stretch goal: verify Ceph works on Rook generally with some workload testing.
Just FYI we are discussing expanding rook's CI here: https://github.com/rook/rook/issues/5924
Specifically we have a tool, rookcheck (https://github.com/SUSE/rookcheck), to perform the testing. At the moment the tool mostly only does the deployment and configuration of rook, and more tests are still needed.
To be useful for this tickets case, rookcheck would need to be expanded to pull in a specific ceph branch before building the container images. This shouldn't be too difficult and I'd be happy to help with it if this is likely to be a useful tool.
- Related to deleted (Feature #47533: Scan for dangling ceph auth entries)
- Status changed from New to In Progress
- Assignee set to Varsha Rao
- Assignee changed from Varsha Rao to Sage Weil
- Pull request ID set to 41286
- Status changed from In Progress to Resolved
Also available in: Atom
PDF