mirror of
https://github.com/ceph/ceph
synced 2024-12-27 14:03:25 +00:00
Ceph is a distributed object, block, and file storage platform
25a9bd3251
Otherwise, a high enough 'count' value will trigger all sorts of timeouts on the OSD; a low enough 'size' value will have the same effect for a high enough value of 'count' (even the default value may have ill effects on the osd's behaviour). Limiting these values do not fix how 'osd bench' should behave, but avoid someone from inadvertently bork an OSD. Four options have been added and the user may adjust them if he so desires to play with the OSD's fate: - 'osd_bench_small_size_max_iops' [default: 100] defines the amount of expected IOPS for a small block size (i.e., <1MB). - 'osd_bench_large_size_max_throughput' [default: 100<<20] defines the expected throughput in B/s. We assume 100MB/s. - 'osd_bench_max_block_size' [default: 64 << 20] caps the block size allowed. We have defined 64 MB. - 'osd_bench_duration' [default: 30] caps the expected duration. This values is used when calculating the maximum allowed 'count', and is not enforced as the maximum duration of the operation. If other IO is undergoing, or 'osd bench' is somehow slowed down, 'osd bench' may go over this duration. Adjusting this option does however allow the user to specify higher 'count' values for (e.g.) a small block size, as the operation is assumed to perform the operation over a longer time span. These options attempt to avoid combinations of dangerous parameters. For instance, we limit the block size to 64 MB (by default) so that there is no temptation to specify a large enough block size, along with a very small 'count', such that the end result is similar to specifying a big count with a sane block size. Fixes: 7248 Signed-off-by: Joao Eduardo Luis <joao.luis@inktank.com> |
||
|---|---|---|
| admin | ||
| ceph-object-corpus@d9870cdfd8 | ||
| debian | ||
| doc | ||
| examples/librados | ||
| fusetrace | ||
| keys | ||
| m4 | ||
| man | ||
| qa | ||
| share | ||
| src | ||
| udev | ||
| wireshark | ||
| .gitignore | ||
| .gitmodules | ||
| .mailmap | ||
| .organizationmap | ||
| AUTHORS | ||
| autogen.sh | ||
| ceph.spec.in | ||
| ChangeLog | ||
| CodingStyle | ||
| configure.ac | ||
| COPYING | ||
| COPYING-LGPL2.1 | ||
| do_autogen.sh | ||
| Doxyfile | ||
| INSTALL | ||
| Makefile.am | ||
| NEWS | ||
| PendingReleaseNotes | ||
| README | ||
| 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.
Building Ceph
=============
To prepare the source tree after it has been git cloned,
$ git submodule update --init
To build the server daemons, and FUSE client, execute 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 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 install dpkg-dev
$ dpkg-checkbuilddeps # make sure we have all dependencies
$ dpkg-buildpackage
For RPM-based systems (Redhat, Suse, etc.),
$ rpmbuild
Building the Documentation
==========================
Prerequisites
-------------
To build the documentation, you must install the following:
- python-dev
- python-pip
- python-virtualenv
- doxygen
- ditaa
- libxml2-dev
- libxslt-dev
- dot
- graphviz
For example:
sudo apt-get install python-dev python-pip python-virtualenv doxygen ditaa libxml2-dev libxslt-dev dot graphviz
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
Build Prerequisites
===================
debian-based
------------
To build the source code, you must install the following:
- automake
- autoconf
- pkg-config
- gcc
- g++
- make
- libboost-dev
- libedit-dev
- libssl-dev
- libtool
- libfcgi
- libfcgi-dev
- libfuse-dev
- linux-kernel-headers
- libcrypto++-dev
- libaio-dev
- libgoogle-perftools-dev
- libkeyutils-dev
- uuid-dev
- libblkid-dev
- libatomic-ops-dev
- libboost-program-options-dev
- libboost-thread-dev
- libexpat1-dev
- libleveldb-dev
- libsnappy-dev
- libcurl4-gnutls-dev
- python-argparse
- python-flask
For example:
$ apt-get install automake autoconf pkg-config gcc g++ make libboost-dev libedit-dev libssl-dev libtool libfcgi libfcgi-dev libfuse-dev linux-kernel-headers libcrypto++-dev libaio-dev libgoogle-perftools-dev libkeyutils-dev uuid-dev libblkid-dev libatomic-ops-dev libboost-program-options-dev libboost-thread-dev libexpat1-dev libleveldb-dev libsnappy-dev libcurl4-gnutls-dev python-argparse python-flask
rpm-based
---------
These are the rpm packages needed to install in an rpm-based OS:
autoconf
automake
gcc
gcc-c++
make
libtool
python-argparse
python-flask
libuuid-devel
libblkid-devel
keyutils-libs-devel
cryptopp-devel
nss-devel
fcgi-devel
expat-devel
libcurl-devel
fuse-devel
gperftools-devel
libedit-devel
libatomic_ops-devel
snappy-devel
leveldb-devel
libaio-devel
boost-devel
For example:
$ yum install autoconf automake gcc gcc-c++ make libtool python-argparse python-flask libuuid-devel libblkid-devel keyutils-libs-devel cryptopp-devel nss-devel fcgi-devel expat-devel libcurl-devel fuse-devel gperftools-devel libedit-devel libatomic_ops-devel snappy-devel leveldb-devel libaio-devel boost-devel