+ Guillaume Abrioux Hi Guillaume, I noticed you've already added Crimson-OSD support to ceph-volume -- great work! I should have checked in earlier about my parallel work on this. I've been focusing on adding support for Seastore's secondary devices (for tiering) and raw device support for Crimson. Given these additional requirements, I'm proposing we maintain separate backend classes while refactoring common code into a shared base class. Benefits of this approach: - Clear separation of concerns - Easier maintenance - Lower risk Does this align with your thinking? Happy to discuss further. Thanks, On Thu, Oct 9, 2025 at 8:42 PM kefu chai <tchaikov@gmail.com> wrote:
Hi folks,
I wanted to reach out regarding ceph-volume support for Crimson.
As you know, Crimson-OSD (backed by Seastore) and classic OSD (backed by BlueStore) have different disk layouts and configuration requirements. Since ceph-volume was designed primarily for BlueStore and FileStore, Crimson will require dedicated design considerations.
I started working on adding Crimson support to ceph-volume this week, but before proceeding further, I'd like to gather input on our approach and ensure alignment with the team's vision for Crimson integration.
Would appreciate hearing your thoughts and any guidance you can share.
cheers,
-- Regards Kefu Chai
-- Regards Kefu Chai