Ceph is a distributed object, block, and file storage platform
Go to file
2012-04-26 21:53:36 -07:00
admin
ceph-object-corpus@17d4afca1c ceph-object-corpus: prune archive 2012-04-18 15:13:38 -07:00
debian obsync: section 8 -> 1 2012-04-19 12:47:50 -07:00
doc obsync: section 8 -> 1 2012-04-19 12:47:50 -07:00
fusetrace
keys
m4
man obsync: section 8 -> 1 2012-04-19 12:47:50 -07:00
qa qa: drop rgw.py from test_python.sh workunit 2012-04-18 21:27:49 -07:00
src Merge branch 'next' 2012-04-26 21:53:36 -07:00
udev
wireshark
.gitignore
.gitmodules
AUTHORS
autogen.sh
ceph.spec.in obsync: section 8 -> 1 2012-04-19 12:47:50 -07:00
ChangeLog
CodingStyle
configure.ac
COPYING
COPYING-LGPL2.1
do_autogen.sh
Doxyfile
GenerateDocs.txt
INSTALL
Makefile.am
NEWS
README
RELEASE_CHECKLIST
SubmittingPatches

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

Please see http://ceph.newdream.net/ 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.


Building Ceph
-------------

To prepare the source tree for the first time in case it has been git cloned,

$ git submodule update --init

To build the server daemons, and FUSE client,

$ ./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 and avoid libfcgi-dev
$ ./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 dpkg-dev
$ dpkg-checkbuilddeps        # make sure we have all dependencies
$ dpkg-buildpackage

For RPM-based systems (Redhat, Suse, etc.),

$ rpmbuild