Ceph is a distributed object, block, and file storage platform
Go to file
Sage Weil 8a674da76e osdmaptool: allow OSDMap encode
Signed-off-by: Sage Weil <sage@redhat.com>
2014-12-12 11:08:40 -08:00
admin
ceph-object-corpus@bb3cee6b85
debian 0.87 2014-10-29 11:03:55 -07:00
doc doc: include 'fs new' stuff in cephfs quickstart 2014-10-29 11:02:19 +00:00
examples
fusetrace
keys
m4
man
qa qa/workunits/cephtool/test.sh: ceph, not ./ceph 2014-11-10 14:12:11 -08:00
rpm
share
src osdmaptool: allow OSDMap encode 2014-12-12 11:08:40 -08:00
systemd
udev
.gitignore
.gitmodule_mirrors build: add ceph-erasure-code-corpus to gitmodule_mirrors 2014-10-08 21:22:02 +02:00
.gitmodules .gitmodules: ignoring changes in rocksdb submodule 2014-10-24 11:14:03 -07:00
.mailmap mailmap: Jiantao He name normalization 2014-10-20 14:07:00 -07:00
.organizationmap mailmap: Federico Gimenez affiliation 2014-10-25 16:50:50 -07:00
.peoplemap mailmap: Ilya Dryomov transition from Inktank to Red Hat 2014-10-19 17:40:15 -07:00
AUTHORS
autogen.sh
ceph.spec.in rpm: 95-ceph-osd-alt.rules is not needed for centos7 / rhel7 2014-10-13 08:16:40 -07:00
ChangeLog
CodingStyle
configure.ac v0.87 2014-10-29 13:50:24 -07:00
CONTRIBUTING.rst
COPYING
COPYING-LGPL2.1
deps.deb.txt
deps.rpm.txt
do_autogen.sh Default configure with nss instead of cryptopp 2014-10-21 08:44:43 +02:00
doc_deps.deb.txt
Doxyfile
INSTALL
Makefile.am Makefile.am: make sure everything was build before make check 2014-10-08 20:19:07 +02:00
NEWS
PendingReleaseNotes
pom.xml
README
README.md
SubmittingPatches

============================================ Ceph - a scalable distributed storage system

Please see http://ceph.com/ for current info.

Contributing Code

Most of Ceph is licensed under the LGPL version 2.1. Some miscellaneous code is under BSD-style license or is public domain. The documentation is licensed under Creative Commons Attribution-ShareAlike (CC BY-SA). There are a handful of headers included here that are licensed under the GPL. Please see the file COPYING for a full inventory of licenses by file.

Code contributions must include a valid "Signed-off-by" acknowledging the license for the modified or contributed file. Please see the file SubmittingPatches for details on what that means and on how to generate and submit patches.

We do not require assignment of copyright to contribute code; code is contributed under the terms of the applicable license.

Build Prerequisites

debian-based

The list of debian package dependencies can be found in deps.deb.txt:

sudo apt-get install `cat deps.deb.txt`

Note: libsnappy-dev and libleveldb-dev are not available upstream for natty, oneiric, and squeeze. Backports for Ceph can be found at ceph.com/debian-leveldb.

rpm-based

The list of RPM package dependencies can be found in deps.rpm.txt:

sudo yum install `cat deps.rpm.txt`

Building Ceph

Developers, please refer to the Developer Guide for more information, otherwise, you can build the server daemons, and FUSE client, by executing the following:

./autogen.sh
./configure
make

(Note that the FUSE client will only be built if libfuse is present.)

Dependencies

The configure script will complain about any missing dependencies as it goes. You can also refer to debian/control or ceph.spec.in for the package build dependencies on those platforms. In many cases, dependencies can be avoided with --with-foo or --without-bar switches. For example,

./configure --with-nss         # use libnss instead of libcrypto++
./configure --without-radosgw  # do not build radosgw
./configure --without-tcmalloc # avoid google-perftools dependency

Building packages

You can build packages for Debian or Debian-derived (e.g., Ubuntu) systems with

sudo apt-get install dpkg-dev
dpkg-checkbuilddeps        # make sure we have all dependencies
dpkg-buildpackage

For RPM-based systems (Red Hat, SUSE, etc.),

rpmbuild

Building the Documentation

Prerequisites

The list of package dependencies for building the documentation can be found in doc_deps.deb.txt:

sudo apt-get install `cat doc_deps.deb.txt`

Building the Documentation

To build the documentation, ensure that you are in the top-level `/ceph directory, and execute the build script. For example:

admin/build-doc