Not a review, just a note that chacra will have to be updated before CI builds will work

Did some investigation into chacra. We have some technical debt to resolve there to allow deploying on modern releases; it would probably be good to do that along with the update for tentacle at the same time. I don't know if we have any Python developers with any relevant expertise at this point; I can probably personally muddle along, but it's not scoped yet.

@dmick do we need to delay merging this until ceph/ceph#61321 is merged?

not sure. I haven't tried to consider interdependencies and would have to spend some time on it. I hope you're hearing me about chacra tho.

not sure. I haven't tried to consider interdependencies and would have to spend some time on it. I hope you're hearing me about chacra tho.

I hear you but I'm not sure what needs done from your comment.

ceph/ceph#61321 is merged.

@dmick, @batrick: fine to to rebase and merge?

@dmick, @batrick: fine to to rebase and merge?

I'm waiting for @dmick to decide next steps before rebasing again.

@dmick: what's the step on this?

Not sure what Patrick is referring to, but one thing I know that needs to be done, still, is to update the chacra configuration to allow for tentacle as a release name

Not sure what Patrick is referring to, but one thing I know that needs to be done, still, is to update the chacra configuration to allow for tentacle as a release name

I was referring to: #2315 (comment)

Should I rebase and then we can merge?

just noting that windows builds on main are all failing with ERROR: Unknown release for version '20.0.0' until this merges

It's also reflected by https://tracker.ceph.com/issues/70215.
@batrick, @cbodley: are we ready to merge after the rebase?

It's also reflected by https://tracker.ceph.com/issues/70215. @batrick, @cbodley: are we ready to merge after the rebase?

I guess? At least let's just merge and rip the band-aid off. Fix whatever gets broken.

I performed the configuration steps at https://docs.ceph.com/en/latest/dev/release-process/#new-major-releases (built the ceph-release package for tentacle with the jenkins job, and updated chacra to include tentacle as a known release, albeit manually because I didn't want to get caught up in ansible/OS upgrade issues). I'll put the change back to the chacra ansible anyway and it's an ongoing task to update the chacra hosts.

I also believe that having the separate version of ceph-release automagically included in the package repo is the wrong way to solve this particular problem and will be pondering a better less-magical solution.