ceph
Add a warning cosbench will be deprecated
This change adds a warning into the cosbench benchmark class to indicate that cosbench support will be deprecated in a later PR and to use the v0.3 release tag if you want to continue using cosbench with CBT.
A similar statement has been added to the README.md.
PR - https://github.com/ceph/ceph/pull/60169 implements deprecation of Cosbench from Teuthology as part of the main Ceph release.
Quincy and newer releases do not run any cosbench tests. Teuthology/QA is only run for Quincy and newer releases. Release tag v0.3 was created as a checkpoint to indicate this is the last version of CBT to support cosbench. Once this PR is merged (after the release tag v0.3 was created), then cosbench may be removed in a future PR. This PR is a warning to indicate this may happen.
Following the process for running unit tests:
- run tools/serialise_benchmark.py
- run python -m pytest -p no:cacheprovider tests/
- applied change.
- re-run python -m pytest -p no:cacheprovider tests/
@lee-j-sanders I'm afraid you might have shoot yourself on the foot: you either misread or ignored the documentation of the unit test generator: https://github.com/ceph/cbt/blob/master/docs/AutomaticUnitTestGeneration.md section https://github.com/ceph/cbt/blob/master/docs/AutomaticUnitTestGeneration.md#workflow-recommeded
Why do you need to generate a new unit test baseline .json on step 1) before doing changes? Does that make sense to you?
I am not sure if this PR is complete, do you need to specify somewhere the current version, and from which point you remove the actual CBT code that uses cosbench? I saw the PR for ceph/qa, I think might be helpful to link those somehown since are clearly dependent? Cheers
PR https://github.com/ceph/ceph/pull/60169 on the ceph release implements the change to remove cosbench from Teuthology. There are QA tests using the cosbench CBT infrastructure I removed from PR60169.
@perezjosibm Since ceph-ci only runs on releases Quincy and newer (as per the release page here: https://docs.ceph.com/en/latest/releases/) and Quincy and newer does not run any cosbench tests as part of the QA suite. Removal of cosbench from CBT will not affect the main Ceph release.
Pacific and early uses cosbench, but no teuthology tests are run on this release. Therefore I don't believe there is any need to put a dependency link in.
@lee-j-sanders I'm afraid you might have shoot yourself on the foot: you either misread or ignored the documentation of the unit test generator: https://github.com/ceph/cbt/blob/master/docs/AutomaticUnitTestGeneration.md section https://github.com/ceph/cbt/blob/master/docs/AutomaticUnitTestGeneration.md#workflow-recommeded
Why do you need to generate a new unit test baseline .json on step 1) before doing changes? Does that make sense to you?
I mis-read your documentation and didn't realise that the baseline.json was already created so I didn't need to regenerate the baselne.
I've re-run the tests here without running the baseline and confirmed that the test passes:
@perezjosibm Thanks for the review, please see my replies above, no modifications made, please re-review, thanks
@perezjosibm are you happy with the changes now? Thanks! @markhpc can you review please thanks!