Ceph is a distributed object, block, and file storage platform
Go to file
Yann Dupont bb09b20e53 mailmap: Alfredo Deza affiliation : Fix Typo.
Signed-off-by: Yann Dupont <yann@objoo.org>
2014-12-27 01:11:31 +01:00
admin
ceph-erasure-code-corpus@f1f95a1de9
ceph-object-corpus@bb3cee6b85
debian Merge pull request #3207 from ceph/wip-cot-rename 2014-12-19 01:12:10 +01:00
doc doc: Instead of using admin socket, use 'ceph daemon' command. 2014-12-19 15:51:49 +01:00
examples
fusetrace
keys
m4
man Merge pull request #3193 from nilamdyuti/wip-doc-ceph-disk 2014-12-19 15:36:39 +01:00
qa Merge pull request #3199 from ceph/wip-qa-empty-xattr 2014-12-19 17:03:25 +00:00
rpm
share
src Merge remote-tracking branch 'gh/wip-fs-quota' 2014-12-19 07:45:02 -08:00
systemd
udev
.gitignore
.gitmodule_mirrors
.gitmodules .gitmodules: update ceph-object-corpus auth repo to github 2014-12-18 14:09:21 -08:00
.mailmap mailmap: Sandon Van Ness name normalization 2014-12-15 11:22:46 +05:30
.organizationmap mailmap: Christos Stavrakakis affiliation 2014-12-27 01:11:31 +01:00
.peoplemap mailmap: Alfredo Deza affiliation : Fix Typo. 2014-12-27 01:11:31 +01:00
AUTHORS
CONTRIBUTING.rst
COPYING
COPYING-LGPL2.1
ChangeLog
CodingStyle
Doxyfile
INSTALL
Makefile.am
NEWS
PendingReleaseNotes
README
README.md
SubmittingPatches
autogen.sh
ceph.spec.in Merge pull request #3207 from ceph/wip-cot-rename 2014-12-19 01:12:10 +01:00
configure.ac
do_autogen.sh
doc_deps.deb.txt
install-deps.sh
pom.xml
run-make-check.sh

README.md

============================================ 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 packages dependencies can be installed with:

./install-deps.sh

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 packages dependencies can be installed with:

     ./install-deps.sh

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