Declaring formatters for all classes that supply
either fmt_print() or alt_fmt_print() member functions
(both must adhere to a specific signature).
Signed-off-by: Ronen Friedman <rfriedma@redhat.com>
Improve the portion of README.md that directs the reader to update the
submodules. Previously, the text assumed that the reader knew that they
should cd into the ceph directory. Now the text is explicit about the
necessity of this action.
Signed-off-by: Zac Dover <zac.dover@proton.me>
* Don't call cephadm a script, it could be misleading
* Use the current release in the example for copy-pasters
* Improve grammar (I think)
Signed-off-by: John Mulligan <jmulligan@redhat.com>
First off, these instructions are wrong because the file has been
renamed to cephadm.py, and will not succeed as written. Amusingly, due
to curl's default behavior (and my lack of access to a time machine) the
initial command will seem to have succeeded until the user discovers
that HTML delivered as part of the body of a 404 response is not an
executable script.
Furthermore, in preparation for Reef we updated the documentation in the
cephadm subsection to use the results of a build, rather than source
files, because reef now contains a "compiled" cephadm. Currently, the
contents of the compilation is essentially the same-old cephadm script
but that will no longer be the case in the very near future (see
7c6a2cad96). We missed this general
section of the Ceph docs that repeats the instructions to copy a raw
python file out of the Ceph tree on GitHub. Update the section to
contain a simplified version of the instruction found in
doc/cephadm/install.rst.
Signed-off-by: John Mulligan <jmulligan@redhat.com>
```
Error: Request failed due to following response errors:
- Could not resolve to a ProjectV2 with the number 2.
```
On further investigation, it looks like it could be a permission issue.
I followed the recommendation in their documentation to fix it: https://github.com/actions/add-to-project#creating-a-pat-and-adding-it-to-your-repository
Signed-off-by: Nizamudeen A <nia@redhat.com>
* refs/pull/52547/head:
qa: add test cases for vanilla ops commands
mds: dump locks when printing mutation ops
common/TrackedOp: support overriding the _dump method
mds: remove op field obsoleted by more usable "reqid"
mds: dump metareq_t instead of full op
mds: add lock type to formatter dump of SimpleLock
mds: mark print methods const
mds: drop MDRequestImpl::msg_lock
mds: lock TrackedOp when dumping
mds: avoid recursive locks dumping state
common/TrackedOp: fix race updating description with proper lock
common/Formatter: add support for dumping null
common/Formatter: refactor generating xml name
Reviewed-by: Xiubo Li <xiubli@redhat.com>
Reviewed-by: Venky Shankar <vshankar@redhat.com>
cmake: ensure fmt lib is at least 8.1.1
Reviewed-by: Kefu Chai <tchaikov@gmail.com>
Reviewed-by: Ken Dreyer <kdreyer@redhat.com>
Reviewed-by: Ronen Friedman <rfriedma@redhat.com>
crimson/os/seastore: OP_CLONE in seastore
Reviewed-by: Yingxin Cheng <yingxin.cheng@intel.com>
Reviewed-by: Samuel Just <sjust@redhat.com>
Reviewed-by: Chunmei Liu <chunmei.liu@intel.com>
There are a few more issues that need to be addressed in order to
run this test on Windows:
* aligned_free (compat.h wrapper) needs to be used after allocating
memory using posix_memalign, "free" causes a crash on Windows
* long (4B) can't store x64 pointers on Windows, we'll use
uintptr_t instead.
* use O_BINARY when opening files, otherwise certain characters
get translated (e.g. LF to CRLF).
Signed-off-by: Lucian Petrut <lpetrut@cloudbasesolutions.com>
Right now, the librbd tests are skipped on Windows.
This change enables the functional tests, which can run with
just a few modifications.
We'll continue skipping the unit tests however, which require
too much OSD code that hasn't been ported (e.g. cls, libosd, etc).
Signed-off-by: Lucian Petrut <lpetrut@cloudbasesolutions.com>
With these changes, every call to log compaction will try to expand its
runway in case of insufficient log space. async compaction will ignore
the `log_forbidden_to_expand` atomic since we know it should't be
harmful. In any other case, expansion of log will wait until compaction
is completed.
in order to ensure op_file_update_inc fits on disk we increase the size
of logs as previously used in _maybe_extend_log. This means we too bring
back _maybe_extend_log with a different usage.
_maybe_extend_log increases the size of the log if the runway is less
than the min runway and if the current transaction is too big to fit.
Fixes: https://tracker.ceph.com/issues/58759
Signed-off-by: Pere Diaz Bou <pere-altea@hotmail.com>
