Over the past cycle, the Ceph engineering team has migrated Ceph Charms from individual repositories on Opendev to a combined single repository on Github. While this is a major restructure in terms of project administration, this will not impact our users consuming Ceph charms from Charmhub. The decision was made after multiple thorough discussions weighing in the advantages and disadvatages of both platforms and this post is aimed at informing our direct and indirect users about the same.
Why ?
Apart from bringing the best of Ceph to Ubuntu packages, the Ceph engineering team is also responsible for updating and maintaining projects like the Ceph charms which is how most of our users consume Ceph on Ubuntu. Having a single repository for all the Ceph charms helps against duplication (or decuplication, as we own around ten Ceph charms) of efforts and in-turn allows us to ship crucial patches to our users faster. The move to Github also helps us consume the best of CI tools and streamline our testing.
FAQ
-
What will happen to the pending pull requests on Opendev? Ans: We have stopped accepting pull requests on the Opendev repositories and they do not trigger artefact builds. Individual contributors are requested to move their patches to a Github pull request on the relevant release branch.
-
Did the move to a monorepo dissolve the contribution history of each project? Ans: No, we performed a branch-wise migration for all the Ceph charms unifying all the individual project git histories into the monorepo.
-
Are users and stakeholders expected to report issues / bugs on Github now? Ans: Since we had a rich history of bugs reported and resolved under Launchpad, we decided to retain that for now. Should that change we will announce this separately.
-
Where are the charms being built and published from? Ans: We have a new Launchpad project (ceph-charms) to organise recipes that build and publish Ceph charms for all releases and relevant architectures.