8 There are multiple build environments, debian based packages are built via pbuilder for multiple distributions. The build hosts are listed in the ``deb_hosts`` file, and the list of distributions are in ``deb_dist``. All distributions are build on each of the build hosts. Currently there is 1 64 bit and 1 32 bit build host.
10 The RPM based packages are built natively, so one distribution per build host. The list of hosts is found in ``rpm_hosts``.
12 Prior to building, it's necessary to update the pbuilder seed tarballs::
14 ./update_all_pbuilders.sh
16 2. Setup keyring for signing packages
17 =====================================
21 export GNUPGHOME=<path to keyring dir>
23 # verify it's accessible
26 The release key should be present::
28 pub 4096R/17ED316D 2012-05-20
29 uid Ceph Release Key <sage@newdream.net>
35 Clone the ceph and ceph-build source trees::
37 git clone http://github.com/ceph/ceph.git
38 git clone http://github.com/ceph/ceph-build.git
40 In the ceph source directory, checkout next branch (for point releases use the {codename} branch)::
44 Checkout the submodules::
46 git submodule update --force --init --recursive
48 4. Update Build version numbers
49 ================================
51 Substitute the ceph release number where indicated below by the string ``0.xx``.
53 Edit configure.ac and update the version number. Example diff::
55 -AC_INIT([ceph], [0.54], [ceph-devel@vger.kernel.org])
56 +AC_INIT([ceph], [0.55], [ceph-devel@vger.kernel.org])
58 Update the version number in the debian change log::
60 DEBEMAIL user@host dch -v 0.xx-1
68 ../ceph-build/tag-release v0.xx
74 The actual configure options used to build packages are in the
75 ``ceph.spec.in`` and ``debian/rules`` files. At this point we just
76 need to create a Makefile.::
81 6. Run the release scripts
82 ==========================
84 This creates tarballs and copies them, with other needed files to
85 the build hosts listed in deb_hosts and rpm_hosts, runs a local build
86 script, then rsyncs the results back to the specified release directory.::
88 ../ceph-build/do_release.sh /tmp/release
94 Copy the rpms to the destination repo::
97 ../ceph-build/push_to_rpm_repo.sh /tmp/release /tmp/rpm-repo 0.xx
99 Next add any additional rpms to the repo that are needed such as leveldb and
100 and ceph-deploy. See RPM Backports section
102 Finally, sign the rpms and build the repo indexes::
104 ../ceph-build/sign_and_index_rpm_repo.sh /tmp/release /tmp/rpm-repo 0.xx
107 8. Create Debian repo
108 =====================
110 The key-id used below is the id of the ceph release key from step 2::
112 mkdir /tmp/debian-repo
113 ../ceph-build/gen_reprepro_conf.sh /tmp/debian-repo key-id
114 ../ceph-build/push_to_deb_repo.sh /tmp/release /tmp/debian-repo 0.xx main
117 Next add any addition debian packages that are needed such as leveldb and
118 ceph-deploy. See the Debian Backports section below.
120 Debian packages are signed when added to the repo, so no further action is
124 9. Push repos to ceph.org
125 ==========================
127 For a development release::
129 rcp ceph-0.xx.tar.bz2 ceph-0.xx.tar.gz \
130 ceph_site@ceph.com:ceph.com/downloads/.
131 rsync -av /tmp/rpm-repo/0.xx/ ceph_site@ceph.com:ceph.com/rpm-testing
132 rsync -av /tmp/debian-repo/ ceph_site@ceph.com:ceph.com/debian-testing
134 For a stable release, replace {CODENAME} with the release codename (e.g., ``argonaut`` or ``bobtail``)::
136 rcp ceph-0.xx.tar.bz2 \
137 ceph_site@ceph.com:ceph.com/downloads/ceph-0.xx.tar.bz2
138 rcp ceph-0.xx.tar.gz \
139 ceph_site@ceph.com:ceph.com/downloads/ceph-0.xx.tar.gz
140 rsync -av /tmp/rpm-repo/0.xx/ ceph_site@ceph.com:ceph.com/rpm-{CODENAME}
141 rsync -auv /tmp/debian-repo/ ceph_site@ceph.com:ceph.com/debian-{CODENAME}
149 For point releases just push the version number update to the
150 branch and the new tag::
152 git push origin {codename}
153 git push origin v0.xx
155 Development and Stable releases
156 -------------------------------
158 For a development release, update tags for ``ceph.git``::
160 git push origin v0.xx
161 git push origin HEAD:last
164 git push origin master
165 git push origin HEAD:next
167 Similarly, for a development release, for both ``teuthology.git`` and ``ceph-qa-suite.git``::
170 git reset --hard origin/master
171 git branch -f last origin/next
172 git push -f origin last
173 git push -f origin master:next