Setup: Build tarballs containing all Calamari , Ceph-Deploy and Ceph Dumpling packages plus setup script and PGP key
The tarball should have the following structure:
ceph-repo ice_setup.py local-repo
ceph-repo is the repository that contains the packages and structure to serve them for other hosts. It should contain Ceph packages just like
http://ceph.com/rpm-dumpling/el6/ for the case of CentOS.
The one difference is that we would also need the GPG key in the top level. Below is the example 'ceph-repo' directory for a CentOS install:
ls -l ceph-repo/ total 16 drwxr-xr-x 3 vagrant vagrant 4096 Jan 13 19:50 noarch -rw-r--r-- 1 vagrant vagrant 1752 Jan 13 19:50 release.asc drwxr-xr-x 3 vagrant vagrant 4096 Jan 13 19:50 SRPMS drwxr-xr-x 3 vagrant vagrant 4096 Jan 13 19:50 x86_64
The structure for the 'local-repo' should be the same, including the GPG key as well. That directory should have only the Calamari and ceph-deploy packages.
The structure within these directories will change depending on the distro (e.g. in Debian the directories would be: conf, db. dists, pool)
and should only have packages for a given distro, so that the overall tarball is leaner.
#6 Updated by Dan Mick over 7 years ago
- Subject changed from Setup: Build tarball containing all Calamari , Ceph-Deploy and Ceph Dumpling packages plus setup script and PGP key to Setup: Build tarballs containing all Calamari , Ceph-Deploy and Ceph Dumpling packages plus setup script and PGP key
- Ceph package repos are at locations documented on http://ceph.com/docs
- Calamari release package repos are at locations documented in http://download.inktank.com/calamari-install, except that currently Calamari 1.1 candidate packages use "packages-staging/<branch>" in place of "packages" in the above paths (for instance, packages-staging/master).
I guess we should build a script that can contact the servers and download the packages so that we can rebuild these (four, I suppose, wheezy, precise, centos64, and rhel64) tarballs at will.