Ceph » Stable releases

Introduction¶

Backporting and the maintenance of a stable release begins when a new stable Ceph release is published. Commits from the master branch are cherry-picked to the stable branch and run through integration and upgrade tests. After a few weeks a point release is published. This repeats until the the stable release is retired. Backporting is focused on fixing bugs and development on the master branch is expected to add new features but both share the same workflow.

Overview of the backports in progress¶

• hammer backport status and backports and pending issues and pull requests
• firefly backport status and backports pending issues and pull requests

Leads¶

• Ceph : Sage Weil
• rados : Samuel Just
• radosgw / rgw : Yehuda Sadeh
• CephFS / fs : Gregory Farnum
• RBD : Josh Durgin

Note: It may be useful to know the leads of other projects which have a different lifecycle but depend on Ceph. For instance Gregory Meno is the lead of Calamari

HOWTO¶

The following describes in detail and in chronological order, the steps to follow for backporting and maintaining stable releases.

Add a new stable release¶

• HOWTO start backporting a stable release

Add a new point release¶

• HOWTO start working on a new point release

Prepare a new point release¶

1. HOWTO monitor the automated tests AKA nightlies
2. HOWTO schedule an issue for backporting
3. HOWTO document user visible changes
4. HOWTO backport commits
5. HOWTO populate the integration branch
6. HOWTO run integration and upgrade tests
7. HOWTO forensic analysis of integration and upgrade tests
8. HOWTO describe a test result inline or HOWTO summarize test results in a separate issue
9. HOWTO merge commits from the integration branch
10. HOWTO synchronize pull requests from different repositories
11. HOWTO resolve issues that are Pending Backport
12. HOWTO get the Ceph lead to decide if it is time for a point release
13. HOWTO get the leads to sign-off on a release
14. HOWTO write the release notes

Publish a stable release¶

• Study https://github.com/ceph/ceph-build/ and http://jenkins.ceph.com/ to figure out how it is used to update http://ceph.com/debian-hammer/ and http://ceph.com/rpm-hammer/
• The jenkins job is http://jenkins.ceph.com/job/ceph/ and requires some setup
• The ceph-jenkins-build ansible setup does a bunch of things like changing version numbers, creating a tag and pushing to the Jenkins GIT repository
• once that tag is created that can be used to trigger a build in the jenkins ui when the build is completed you are required to run a bunch of scripts in the jenkins server they sign and re-index the repositories and then synchronize them with ceph/(rpm|debian)-$release. Those scripts need to be edited by hand depending on the type of release and where you are pushing them to (e.g. testing vs firefly vs hammer)
• for hammer a new repository was created by hand and it is documented as a script

Retire a stable release¶

• HOWTO retire a stable release

Recurring duties expected from backporters¶

• HOWTO triage incoming backport pull requests
• HOWTO triage incoming Pending backport issues

Backporters currently performing these duties (remove yourself when on vacation etc.):

• Loic Dachary : weekly
• Nathan Cutler : weekly

Organize the stable releases and backports team¶

• HOWTO become a new team member
• HOWTO retire from the team