The WNBD project provides virtual block devices via a Windows driver. This allows it to connect to a Network Block Device (NBD) server.
The project is still in the development phase, but we will test it and keep an eye on it.
This guide will detail the process of adding OSD nodes to an existing cluster running RedHat Enterprise Storage 4 (Nautilus). The process can be completed without taking the cluster out of production.
ceph osd set norebalance
ceph osd set nobackfill
ceph osd set norecover
ceph status
Make sure that the new ceph node is defined in the /etc/hosts file.
vim /usr/share/ceph-ansible/hosts
[mons]
...
[mgrs]
...
[osds]
ceph-node1
ceph-node2
ceph-node3
ceph-node4
...
ping test before ansible playbook execution
ansible-playbook site-conatiner.yml --limit ceph-node4
ceph osd unset nobackfill
ceph osd unset norecover
ceph osd unset norebalance
ceph osd tree
ceph osd crush tree
ceph osd df
ceph -s
ceph versions
docs.ceph.com/projects/ceph-ansible/en/latest/day-2/osds.html
Limit test how ceph behaves with billions of rados objects.
blocksandfiles.com/2020/09/22/ceph-scales-to-10-billion-objects/
Perhaps someone has already thought about using EC (erasure coding) for ceph pools, so that the overhead for the secure storage of data is not too high. This was already a topic in many of the trainings we have held in recent years.
But what most people forget after creating EC pools is how to get all the information about an existing pool.
ceph osd pool ls
or
ceph osd pool ls detail
don't really give information about the configuration of erasure coding pools. However, there is a small option that lets ceph spill the beans a bit more.
ceph osd pool ls detail --format=json
you might get more information than you want.
But with
ceph osd pool ls detail --format=json | jq '.'
the whole thing looks much more friendly to the eyes.
And here we find more information about the erasure coded pools:
ceph osd pool ls detail --format=json | jq '.' | grep erasure_code_profile
erasure_code_profile": "clyso-costum-profile",
If you want to list all defined profiles, then use
ceph osd erasure-code-profile ls
You can get detailed information about an erasure code profile with:
ceph osd erasure-code-profile get clyso-costum-profile
We had the problem of getting the correct authorizations for the Ceph CSI user on the pools.
We then found the following bug for the version prior to 14.2.12.
https://github.com/ceph/ceph/pull/36413/files#diff-1ad4853f970880c78ea0e52c81e621b4
Was then solved with version 14.2.12.
monclient(hunting): handle_auth_bad_method server allowed_methods [2] but i only support [2]
We see this example again and again with customers who copy their keyring file directly from the output of:
ceph auth ls
In the client.\<name\>.keyring the name is enclosed in square brackets and the key is separated by an equal sign and in the ceph auth ls by a colon.
Rather by chance, I came across the following website with the service for searching for certificates with the history for a domain.
If you are wondering how many and which certificates you have used for a domain, you can use this link.
interesting insights into how dependency on external operating system libraries can affect the operation of Ceph.
ceph tell 'osd.*' injectargs --osd-max-backfills=2 --osd-recovery-max-active=2
Start in small steps, observe the Ceph status, client IOPs and throughput and then continue to increase in small steps.
In the producton with regard to the applications and hardware infrastructure, we recommend setting these settings back to default as soon as possible.