Ceph is a distributed object, block, and file storage platform
Go to file
Joao Eduardo Luis b9e6696c09 mon: PaxosService: have wait_for_* functions requiring an op
Basically, so we can mark the op accordinly; we'll leave context-only
functions to maintain compatibility with other users of these functions
that do not use them for op-related callbacks.

Signed-off-by: Joao Eduardo Luis <joao@suse.de>
2015-07-16 18:06:07 +01:00
admin
bin
ceph-erasure-code-corpus@4957a9a0fb
ceph-object-corpus@7bd9bbe235
cmake/modules
debian Merge remote-tracking branch 'gh/next' 2015-07-16 12:03:58 -04:00
doc Merge pull request #5188 from athanatos/wip-11687 2015-07-16 11:03:18 -04:00
etc/sysconfig/SuSEfirewall2.d/services
examples
fusetrace
keys
m4
man automake: Fix out-of-tree build. 2015-07-16 10:32:34 +02:00
qa Merge remote-tracking branch 'gh/next' 2015-07-16 12:03:58 -04:00
rpm
share
src mon: PaxosService: have wait_for_* functions requiring an op 2015-07-16 18:06:07 +01:00
systemd
udev
.gitignore
.gitmodule_mirrors
.gitmodules
.mailmap
.organizationmap
.peoplemap
AUTHORS
autogen.sh
ceph.spec.in packaging: package libcls_cephfs.so 2015-07-16 14:21:03 +08:00
ChangeLog
CMakeLists.txt
CodingStyle
configure.ac Merge remote-tracking branch 'gh/next' 2015-07-16 12:03:58 -04:00
CONTRIBUTING.rst
COPYING
COPYING-GPL2
COPYING-LGPL2.1
do_autogen.sh
doc_deps.deb.txt
Doxyfile
INSTALL
install-deps.sh
make_dist.sh
make-debs.sh
Makefile.am
NEWS
PendingReleaseNotes mon: Monitor: use 'ceph mon metadata' instead of 'ceph mon_metadata' 2015-07-16 15:54:03 +01:00
pom.xml
README
README.cmake
README.md
README.xio
run-make-check.sh
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

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

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