Replace the 'ceph [mon] sync force' commands and just use the asok
sync_force command instead. This is a low-level command that nobody should
reasonsbly using except in an emergency, so do not bother with trying to
maintain compatibility; it's a bit rediculous that we had 3 variations of
this to being with!
Signed-off-by: Sage Weil <sage@redhat.com>
`ceph {set,unset} full` does not take effect since mimic, and monitor
does not support this command since Octopus. so let's document this
change.
Signed-off-by: Kefu Chai <kchai@redhat.com>
'del' & 'list' & 'put' are deprecated. It's preferred to
using 'rm' & 'ls' & 'set' for ceph config-key
Signed-off-by: Changcheng Liu <changcheng.liu@intel.com>
When creating/fetching key it's nice to have the ability to change the
ownership of the created file.
This commit adds the '--setuser' and 'setgroup' which respectively apply
the desired owner and group to a file user when '--output' is passed.
Closes: https://tracker.ceph.com/issues/38370
Signed-off-by: Sébastien Han <seb@redhat.com>
Referenced purge subcommand info via ceph osd command label.
Fixes: https://tracker.ceph.com/issues/36605
Signed-off-by: James McClune <jmcclune@mcclunetechnologies.net>
Add the summary and syntax for all the subcommands under the subcommand
"ceph osd pool application" to ceph the manual page.
Signed-off-by: Rishabh Dave <ridave@redhat.com>
mon,osd: do not use crush_device_class file to initalize class for new osds
Reviewed-by: Alfredo Deza <adeza@redhat.com>
Reviewed-by: Kefu Chai <kchai@redhat.com>
Reviewed-by: Andrew Schoen <aschoen@redhat.com>
If provided, set the OSD device_class at OSD creation time. This is
simpler than writing a file that the OSD has to read in and use to
set its initial device class, and also avoids a bit of sticky state
at the OSD that will make it keep trying to reset its device class on
startup if it ever gets cleared.
Note that we now ignore json input fields we don't understand, so remove
a test case.
Signed-off-by: Sage Weil <sage@redhat.com>
Since kraken, Ceph enforces a 1:1 correspondence between CRUSH ruleset and
CRUSH rule, so effectively ruleset and rule are the same thing, although
the term "ruleset" still survives - notably in the CRUSH rule itself, where it
effectively denotes the number of the rule.
This commit updates the documentation to more faithfully reflect the current
state of the code.
Fixes: http://tracker.ceph.com/issues/20559
Signed-off-by: Nathan Cutler <ncutler@suse.com>
Though "ls" command is explained and it's usage shown in the man page,
it is not mentioned in the subcommands list of "ceph osd" in the
beginning.
Signed-off-by: Rishabh Dave <ridave@redhat.com>
`ceph rmfailed` refers to its argument as "who" and `ceph repaired` refers to its argument as "rank". We should make these commands and others consistent by standardizing the argument as "role".
Fixes: http://tracker.ceph.com/issues/21393
Signed-off-by: Jos Collin <jcollin@redhat.com>
An osd is safe to destroy if
- we have osd_stat for it
- osd_stat indicates no pgs stored
- all pgs are known
- no pgs map to it
An osd is ok ot stop if
- we have pg stats
- no pgs will drop below min_size
Signed-off-by: Sage Weil <sage@redhat.com>
* 8/ceph.rst: `rm` subcommand removes osd from osdmap, not the cluster.
the latter is more ambiguous in different contexts.
* rados/operations/add-or-rm-osds.rst: add a subsection of "Replacing an
OSD". update the subsection of "Removing the OSD" with "ceph osd
purge" command
* release-notes.rst: link from it to the new subsection in add-or-rm-osds.rst
Signed-off-by: Kefu Chai <kchai@redhat.com>
With the introduction of `osd new`, we are now deprecating `osd create`
with the intent of removing it in a future release.
Signed-off-by: Joao Eduardo Luis <joao@suse.de>
