Hey Kefu,

As you've mentioned, ceph-volume initial support for Crimson-OSD/SeaStore was merged [1].
This was part of the work to bring Cephadm support to Crimson [2].
Refactoring the common ceph-volume code into a shared base class sounds like the right approach to me.
It should help with the future improvements needed to fully support SeaStore in ceph-volume.
I'll defer to the ceph-vol team for additional opinions.
We can also discuss this further in the Crimson weekly meeting or in the #crimson Slack channel.
Thank you for your latest valuable contributions to the Crimson Project :)

Matan

[1] https://github.com/ceph/ceph/pull/64323
[2] https://tracker.ceph.com/issues/71946

On Fri, Oct 10, 2025 at 7:16 AM kefu chai <tchaikov@gmail.com> wrote:
+ 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
_______________________________________________
Dev mailing list -- dev@ceph.io
To unsubscribe send an email to dev-leave@ceph.io