Ceph is a distributed object, block, and file storage platform
Go to file
Abhishek Lekshmanan d5844d253e mailmap: Jason Dillaman name normalization
Signed-off-by: Abhishek Lekshmanan <abhishek@suse.com>
2016-03-04 16:09:26 +01:00
admin pybind: move cephfs to Cython 2016-02-29 10:58:52 +01:00
bin
ceph-erasure-code-corpus@c332279082
ceph-object-corpus@47fbf8c6ae
cmake/modules
debian pybind: move cephfs to Cython 2016-02-29 10:58:52 +01:00
doc doc: fix typo, indention etc. 2016-03-01 02:26:18 +08:00
etc
examples
fusetrace
keys
m4
man
mirroring
qa rbd/run_cli_tests.sh: Reflect test failures 2016-02-26 08:01:30 -07:00
rpm
selinux
share
src Merge pull request #7745 from sileht/sileht/rados-cython 2016-03-01 10:40:21 +00:00
systemd
udev
.gitignore
.gitmodule_mirrors
.gitmodules
.mailmap mailmap: Jason Dillaman name normalization 2016-03-04 16:09:26 +01:00
.organizationmap mailmap: Aaron Bassett affiliation 2016-03-04 16:08:16 +01:00
.peoplemap
AUTHORS
CMakeLists.txt
CONTRIBUTING.rst
COPYING
COPYING-GPL2
COPYING-LGPL2.1
ChangeLog
CodingStyle
Doxyfile
INSTALL
Makefile.am
NEWS
PendingReleaseNotes
README
README.aix
README.cmake
README.md
README.solaris
README.xio
SubmittingPatches.rst
autogen.sh
ceph.spec.in pybind: move cephfs to Cython 2016-02-29 10:58:52 +01:00
configure.ac
do_autogen.sh
doc_deps.deb.txt
install-deps.sh
make-debs.sh
make_dist.sh
pom.xml
run-cmake-check.sh
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.rst 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

The list of Debian or RPM packages dependencies can be installed with:

./install-deps.sh

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

Building Ceph

Autotools

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.)

CMake

Prerequisite: CMake 2.8.11

Build instructions:

mkdir build
cd build
cmake [options] /path/to/ceph/src/dir
make

(Note that /path/to/ceph/src/dir can be in the tree and out of the tree)

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