Skip to content

Conversation

anoopcs9
Copy link
Collaborator

  • Use Samba v4.23 for ceph20.
  • Switch to Storage SIG ceph tentacle packages for ceph20 on CentOS.
  • Generalize a switch case for CentOS based package selection.

xhernandez
xhernandez previously approved these changes Sep 16, 2025
@anoopcs9 anoopcs9 force-pushed the install-pkg-script-updates branch from 56b349a to b02c885 Compare September 16, 2025 06:57
@mergify mergify bot dismissed xhernandez’s stale review September 16, 2025 06:57

Pull request has been modified.

@anoopcs9
Copy link
Collaborator Author

Forgot to remove the shellcheck waiver (diff).

@phlogistonjohn
Copy link
Collaborator

phlogistonjohn commented Sep 16, 2025

  • Switch to Storage SIG ceph tentacle packages for ceph20 on CentOS.

I'm not in favor of this. We ship as part of ceph when the smb mgr module is used. The ceph containers are built using the packages that appear in shaman/chacra. We should use the same set of packages to be as close to ceph upstream as possible.

@anoopcs9
Copy link
Collaborator Author

  • Switch to Storage SIG ceph tentacle packages for ceph20 on CentOS.

I'm not in favor of this. We ship as part of ceph when the smb mgr module is used. The ceph containers are built using the packages that appear in shaman/chacra. We should use the same set of packages to be as close to ceph upstream as possible.

Can you elaborate on where and how much we expect to deviate with distro packages? Starting with v20.2.2 (or even now with 20.1.0) ceph20 will have the exact same version from Storage SIG.

@anoopcs9 anoopcs9 marked this pull request as ready for review September 16, 2025 17:42
@phlogistonjohn
Copy link
Collaborator

I don't know how much they differ and that's part of the issue. I do know how the RPMs produced by the ceph CI work and where all that is managed. My main point is that the images we build specifically to be consumed by ceph users should hew as closely to what the ceph images have - and that implies the packages produced by ceph directly not the storage sig IMO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants