mgr/dashboard_v2: Add RBD create functionality to the Python backend
Reviewed-by: Ricardo Dias <rdias@suse.com>
Reviewed-by: Sebastian Wagner <sebastian.wagner@suse.com>
Reviewed-by: John Spray <john.spray@redhat.com>
Reviewed-by: Ricardo Marques <rimarques@suse.com>
Librados C API functions that operate on OMAP accept key values that
are NUL-terminated. This makes them unsuitable for operation on keys
that have NULs embedded in them (like those produced by librbd).
This commit adds new API functions:
- rados_omap_get_next2
- rados_write_op_omap_cmp2
- rados_write_op_omap_set2
- rados_write_op_omap_rm_keys2
- rados_read_op_omap_cmp2
- rados_read_op_omap_get_vals_by_keys2
that accept or provide actual key length in bytes and therefore are not
limiting key values to first NUL encountered.
Signed-off-by: Piotr Dałek <piotr.dalek@corp.ovh.com>
This commit adds a basic RBD create functionality to the REST API. It enables
the POST request of the http://<host>:<port>/api/rbd API endpoint.
The commit adds also related tests.
Signed-off-by: Tatjana Dehler <tdehler@suse.com>
ceph config show mgr.x doesn't work
root cause is mgr daemon's mgrc has no chance
to process MSG_MGR_MAP in the mgr daemon's
ms_dispatch.
fix is let this message pass through for mgrc
Signed-off-by: Gu Zhongyan <guzhongyan@360.cn>
Signed-off-by: yupeng chen chenyupeng-it@360.cn
* refs/pull/20700/head:
client: use either dentry_invalidate_cb or remount_cb to invalidate kernel dcache
Reviewed-by: Patrick Donnelly <pdonnell@redhat.com>
Reviewed-by: Zheng Yan <zyan@redhat.com>
* refs/pull/20719/head:
client: add new ceph_mount_perms_set function
Reviewed-by: John Spray <john.spray@redhat.com>
Reviewed-by: Patrick Donnelly <pdonnell@redhat.com>
Reviewed-by: Zheng Yan <zyan@redhat.com>
* refs/pull/20881/head:
messages/MClientRequest: fix a typo so we don't output 'setfilelockrule' in logs
Reviewed-by: Patrick Donnelly <pdonnell@redhat.com>
Back in commit 7469f26a33c072169d6ed929352eda06562ffe3f when the COPYING
file was added to the repository and the project was "licensed," the
license file was
GNU LESSER GENERAL PUBLIC LICENSE
Version 2.1, February 1999
However, the license was abbreviated as LGPL2 in various places (pretty
much everywhere, actually), due to my own ignorance/carelessness. (I was
distinguishing it from shiny new version 3, released 6 months earlier.)
Version 2 of LGPL is the "Library General Public License," published in
June 1991: https://www.gnu.org/licenses/old-licenses/lgpl-2.0.html
Note that this ambiguity persists for most of the project's lifetime. For
example, the original debian/copyright in 8adc9dac1d61f34ce85e3cbad1478e3e6ffe2b8e
said "LGPL2" bug in 4545f8b929cc562a1231c0ceb067e9d8e58a0de7 (2009, a year
later) it is changed to LGPL2.1 to satisfy Debian's lintian checks. (It's
remained LGPL2.1 ever since.)
"Correct" the record by changing LGPL2 references to LGPL2.1.
Signed-off-by: Sage Weil <sage@redhat.com>
The license applicable to the files under doc/ was originally declared (in the
top-level file COPYING) to be "Creative Commons Attribution-ShareAlike (CC
BY-SA)" by ed0653b493a3f919a3abc37a0aa9b5aa29ae0b0e
This license declaration omitted a version number.
Some time later ef7418421b3748c712019c8aedd02b8005c1e1ea was merged, mentioning
CC-BY-SA-1.0 as one of the Ceph source code licenses. Although the purpose of that
commit was only to summarize the canonical license information from COPYING, it
unintentionally became the only place in the source code where the doc license
version was specified.
In March 2018, the Debian project warned that CC-BY-SA-1.0 does not meet its
criteria for inclusion in the "free" section of the Debian distribution. (For
that, at least version 3.0 must be used.)
This new commit removes the doc license ambiguity by setting it to CC-BY-SA-3.0
in all places where the license is mentioned.
The exact spelling of the license name is taken from https://spdx.org/licenses/
Fixes: http://tracker.ceph.com/issues/23336
Signed-off-by: Nathan Cutler <ncutler@suse.com>
Trim 'ceph-fuse -V' output to print the FUSE library version and exit.
Fixes: http://tracker.ceph.com/issues/23248
Signed-off-by: Jos Collin <jcollin@redhat.com>
The ssl task located in a python file called `ssl.py` will generate
python module loading conflicts with the `ssl` system module, when
running QA tests using vstart_runner.py.
Signed-off-by: Ricardo Dias <rdias@suse.com>
They are not suited to be used with Ceph and should not be selected
as a address to bind on.
Fixes: http://tracker.ceph.com/issues/21813
Signed-off-by: Wido den Hollander <wido@42on.com>
Fixes the error that would inject an extra argument to vagrant when the
environment variable is not present
Signed-off-by: Alfredo Deza <adeza@redhat.com>
Add the description of --thick-provision option for the rbd command.
Signed-off-by: Hitoshi Kamei <hitoshi.kamei.xm@hitachi.com>
Cc: Mitsuo Hayasaka <mitsuo.hayasaka.hu@hitachi.com>
Add the help output of thick provision option to
the help.t of the rbd command.
Signed-off-by: Hitoshi Kamei <hitoshi.kamei.xm@hitachi.com>
Cc: Mitsuo Hayasaka <mitsuo.hayasaka.hu@hitachi.com>
Add the qa code for thick provision option, if applied.
The qa code creates and checks 64 MB thick-provision image
for small image test, and it also creates and checks 4 GB
thick-provision image for large image test.
Signed-off-by: Hitoshi Kamei <hitoshi.kamei.xm@hitachi.com>
Cc: Mitsuo Hayasaka <mitsuo.hayasaka.hu@hitachi.com>
Add the thick provision option to the rdb command, if applied.
The rbd command with the option actually writes zero data to
new rbd image, and sets the value of rbd_discard_on_zero_write_same
to false before opening the images.
Signed-off-by: Hitoshi Kamei <hitoshi.kamei.xm@hitachi.com>
Cc: Mitsuo Hayasaka <mitsuo.hayasaka.hu@hitachi.com>
