Project

General

Profile

HOWTO » History » Version 48

Loïc Dachary, 05/15/2015 12:44 PM

1 15 Loïc Dachary
h3. Introduction
2 1 Loïc Dachary
3 17 Loïc Dachary
Backporting and the maintenance of a stable release begins when a new "stable Ceph release":http://ceph.com/docs/master/releases 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":http://ceph.com/docs/master/releases is published. This repeats until the "lifetime of the stable release":http://ceph.com/docs/master/releases comes to an end. Backporting is focused on fixing bugs and development on the master branch is expected to add new features but both share the "same workflow":http://ceph.com/docs/master/dev/development-workflow/.
4 16 Loïc Dachary
5 24 Loïc Dachary
h3. Overview of the backports in progress
6
7 37 Loïc Dachary
* *hammer* "backport status":http://tracker.ceph.com/issues/11353 and "issues":http://tracker.ceph.com/projects/ceph/issues?query_id=77 and "pull requests":https://github.com/ceph/ceph/pulls?q=is%3Aopen+is%3Apr+milestone%3Ahammer
8
* *firefly* "backport status":http://tracker.ceph.com/issues/11090 and "issues":http://tracker.ceph.com/projects/ceph/issues?query_id=75 and "pull requests":https://github.com/ceph/ceph/pulls?q=is%3Aopen+is%3Apr+milestone%3Afirefly
9 24 Loïc Dachary
10 32 Loïc Dachary
h3. Leads
11
12 35 Loïc Dachary
* Ceph : Sage Weil
13 32 Loïc Dachary
* rados : Samuel Just
14
* radosgw / rgw : Yehuda Sadeh
15
* CephFS / fs : Gregory Farnum
16
* RBD : Josh Durgin
17 47 Loïc Dachary
18 48 Loïc Dachary
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":http://tracker.ceph.com/projects/calamari
19 32 Loïc Dachary
20 26 Loïc Dachary
h3. HOWTO
21 23 Loïc Dachary
22 1 Loïc Dachary
The following describes in detail and in chronological order, the steps to follow for backporting and maintaining stable releases.
23
24 23 Loïc Dachary
h4. Add a new stable release
25 19 Loïc Dachary
26 1 Loïc Dachary
* [[HOWTO start backporting a stable release]]
27 15 Loïc Dachary
28 23 Loïc Dachary
h4. Add a new point release
29 1 Loïc Dachary
30 19 Loïc Dachary
* [[HOWTO start working on a new point release]]
31 15 Loïc Dachary
32 23 Loïc Dachary
h4. Prepare a new point release
33 9 Loïc Dachary
34 43 Loïc Dachary
# [[HOWTO monitor the automated tests AKA nightlies]]
35 22 Loïc Dachary
# [[HOWTO schedule an issue for backporting]]
36 19 Loïc Dachary
# [[HOWTO update the inventory]]
37 30 Loïc Dachary
# [[HOWTO document user visible changes]]
38 1 Loïc Dachary
# [[HOWTO backport commits]]
39 19 Loïc Dachary
# [[HOWTO populate the integration branch]]
40 1 Loïc Dachary
# [[HOWTO run integration and upgrade tests]]
41 46 Loïc Dachary
# [[HOWTO forensic analysis of integration and upgrade tests]]
42 19 Loïc Dachary
# [[HOWTO describe a test result]] inline or [[HOWTO summarize test results]] in a separate issue
43 25 Loïc Dachary
# [[HOWTO merge commits from the integration branch]]
44 1 Loïc Dachary
# [[HOWTO synchronize pull requests from different repositories]]
45 27 Loïc Dachary
# [[HOWTO resolve issues that are Pending Backport]]
46 34 Loïc Dachary
# [[HOWTO get the Ceph lead to decide if it is time for a point release]]
47 31 Loïc Dachary
# [[HOWTO get the leads to sign-off on a release]]
48 33 Loïc Dachary
# [[HOWTO write the release notes]]
49 15 Loïc Dachary
50 38 Loïc Dachary
h4. Publish a stable release
51
52 39 Loïc Dachary
* 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/ 
53 40 Loïc Dachary
* The jenkins job is http://jenkins.ceph.com/job/ceph/ and requires some setup
54
* The "ceph-jenkins-build":https://github.com/alfredodeza/ceph-jenkins-build/tree/master/ceph ansible setup does a bunch of things like "changing version numbers, creating a tag and pushing to the Jenkins GIT repository":https://github.com/alfredodeza/ceph-jenkins-build/blob/master/ceph/tasks/setup.yml
55
* 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)
56
* for hammer a new repository was created by hand and it is "documented as a script":https://gist.github.com/alfredodeza/b8f8b94ea795f1a7169b
57 38 Loïc Dachary
58 23 Loïc Dachary
h4. Retire a stable release
59 15 Loïc Dachary
60 21 Loïc Dachary
* [[HOWTO retire a stable release]]
61 41 Loïc Dachary
62
h4. Organize the stable releases and backports team
63
64
* [[HOWTO become a new team member]]
65
* [[HOWTO retire from the team]]