currently `osd pool set size` only modifies min_size when it is above new size,
while it should be recalculated unconditionally.
fixes: https://tracker.ceph.com/issues/44862
Signed-off-by: Deepika Upadhyay <dupadhya@redhat.com>
it's a regression introduced by
6158bcfdef, which dropped the change to
make Sanitizers optional
since we've switched from xenial to bionic. there is no need to disable
this anymore. we ran into an issue caused by the ancient linker shipped
by xenial before.
Fixes: https://tracker.ceph.com/issues/44658
Signed-off-by: Kefu Chai <kchai@redhat.com>
Purpose: Allocate more resoures for the requests in the io qpair,
and the real value will be determined by the inner logic in SPDK NVMe Driver.
But if we do not set it, the default size is 512, and the value is too low.
If there are many big I/Os with high QD submitted, with this setting,
it could improve the performance.
Signed-off-by: Ziye Yang <ziye.yang@intel.com>
This was present, but a no-op.
By default, install cephadm.
Optionally take a list of packages to install instead (e.g., ceph-common).
Signed-off-by: Sage Weil <sage@redhat.com>
There is a potential for an independently scheduled status update to
request the local image name from the bootstrap state machine during its
initialization.
Fixes: https://tracker.ceph.com/issues/44391
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
* refs/pull/33980/head:
cephadm: bootstrap: allow --output-dir
cephadm: do not infer image for bootstrap
cephadm: write output files to /etc/ceph by default
cephadm: verify the output files' containing directory exists
Reviewed-by: Michael Fritch <mfritch@suse.com>
* `ul.simple > li` is also used in front page, where the items are too
sparse now. so we need to restore the default spacing.
* `ul.simple > li > ul > li:last-child` is used to control the spacing
between nested unordered list. we need have more spacing there.
* `div.section > ul > li > p` is added to decrease the spacing of nested
list items.
Signed-off-by: Kefu Chai <kchai@redhat.com>
* refs/pull/33973/head:
mgr/orch,cephadm: elevate --force flag for daemons to interface
cephadm: backup data when we remove stateful daemons (mon, osd, prometheus)
cephadm: do not zap disk after removing an OSD daemon
Reviewed-by: Michael Fritch <mfritch@suse.com>
* use console lexer for highlighting command lines
otherwise they will be rendered as python code
* use bold font instead italic in subsection headers,
they look more formal this way
* fix a typo: delineated
Signed-off-by: Kefu Chai <kchai@redhat.com>
This streamlines the install for most users by putting the config and
keyring files in /etc/ceph, where other ceph CLI commands will find them.
The cost is making isolated installs a bit more painful, by requiring
that users specify a local location for --output-config etc.
Signed-off-by: Sage Weil <sage@redhat.com>
* change the function signature of `call()` to accept a bufferlist,
as MCommand is supposed to carry a bufferlist which can be consumed
by the hook.
* drop the wrapper of `tell()`, instead always use `call()`. simpler
this way.
* promote `tell_result_t` to top level of `crimson::admin` as it is used
as part of the interface between hook and `AdminSocket`
* replace `maybe_parsed_t` with `std::variant<parsed_command_t, tell_result_t>`,
as the latter is able to convey more detailed error information if
something goes wrong.
* osd now handles `MCommand`.
Signed-off-by: Kefu Chai <kchai@redhat.com>
prepare for the tell command, as the payload of MCommand is a
`vector<string>`, and `cmdmap_from_json()` expects a `vector<string>`
Signed-off-by: Kefu Chai <kchai@redhat.com>
* change annotation of `orchestrator.Orchestrator.apply_drivegroups()` so it returns
`Sequence[Completion]`
see
https://mypy.readthedocs.io/en/latest/generics.html#variance-of-generic-types
* to follow the interface defined by `orchestrator.Orchestrator`. change
all its implementations. see `orchestrator/_interface.py`.
Signed-off-by: Kefu Chai <kchai@redhat.com>
This avoids doing permanent damage when removing stateful daemons.
We include OSDs here even though in most cases no precious data lives in
the osd data directory because there might be some important metadata
there--particularly for adopted OSDs from older clusters.
Signed-off-by: Sage Weil <sage@redhat.com>
