Ceph is a distributed object, block, and file storage platform
Go to file
Sage Weil 7522650939 debian: chown -R ceph:ceph /var/log/ceph
The number of log files is generally bounded; safe to chown these.

Allow ceph group members to write to this dir.

Signed-off-by: Sage Weil <sage@redhat.com>
2015-08-26 20:34:14 -04:00
admin
bin
ceph-erasure-code-corpus@dc409e0b20
ceph-object-corpus@20351c6bae test/mon: add test for "mon add" 2015-08-11 10:21:18 +08:00
cmake/modules
debian debian: chown -R ceph:ceph /var/log/ceph 2015-08-26 20:34:14 -04:00
doc Merge pull request #5660 from badone/doc_snaps_typo 2015-08-25 11:54:29 -04:00
etc/sysconfig/SuSEfirewall2.d/services
examples
fusetrace
keys
m4
man
qa osd: always load erasure plugins from the configured directory 2015-08-21 16:03:30 -04:00
rpm
selinux
share
src Merge pull request #5625 from liewegas/wip-memcpy 2015-08-26 14:11:49 -04:00
systemd
udev
.gitignore
.gitmodule_mirrors
.gitmodules
.mailmap
.organizationmap
.peoplemap
AUTHORS
autogen.sh
ceph.spec.in ceph.spec.in: remove obsolete SUSE-specific code 2015-08-26 16:34:44 +02:00
ChangeLog
CMakeLists.txt moved to use boost uuid implementation, based on commit 4fe89a7b14 2015-08-19 06:46:17 -04:00
CodingStyle
configure.ac uuid: use boost::random:random_device 2015-08-24 14:51:47 -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 doc/release-notes: v9.0.3 2015-08-24 09:36:08 -04: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