Preface Ceph. is a widely used distributed-storage solution. The performance of Ceph varies greatly in different configuration environments. Many clusters in production environments are deployed on hard disks. For various types of workloads, performance requirements are also different. We built a Ceph cluster based on the Open-CAS caching framework. We made some adjustments to the. Certain client configurations can be applied at runtime. To check if a configuration option can be applied (taken into affect by a client) at runtime, use the config help command: ceph config help debugclient debugclient - Debug level for client (str, advanced) Default: 0/5 Can update at runtime: true The value takes the form 'N' or 'N/M.
Notice
Ceph Client Keyring
Copying Ceph Configuration File to OpenStack Nodes. The nodes running glance-api, cinder-volume, nova-compute and cinder-backup act as Ceph clients. Each requires the Ceph configuration file. Copy the Ceph configuration file from the monitor node to the OSP nodes. Setting Up Ceph Client Authentication. Getting a traffic report from ceph based on clients/machines. I was wondering if there is a way to get a traffic report on ceph based on clients that are listed on ceph auth ls or by IP addresses of machines that are connected to ceph? Know someone who can answer? Share a link to this question via email, Twitter, or Facebook. Executing ceph-deploy admin will push a Ceph configuration file and the ceph.client.admin.keyring to the /etc/ceph directory of the nodes, so we can use the ceph CLI without having to provide the ceph.client.admin.keyring each time to execute a command. At this point, we can take a peek at our cluster.
This document is for a development version of Ceph.
The Ceph client tools and libraries can be natively used on Windows. This avoidsthe need of having additional layers such as iSCSI gateways or SMB shares,drastically improving the performance.
Prerequisites¶
Supported platforms¶
Windows Server 2019 and Windows Server 2016 are supported. Previous WindowsServer versions, including Windows client versions such as Windows 10, mightwork but haven’t been tested.
Windows Server 2016 does not provide Unix sockets, in which case some commandsmight be unavailable.
Secure boot¶
The WNBD driver hasn’t been signed by Microsoft, which means that Secure Bootmust be disabled.
Dokany¶
In order to mount Ceph filesystems, ceph-dokan requires Dokany to beinstalled. You may fetch the installer as well as the source code from theDokany Github repository: https://github.com/dokan-dev/dokany/releases
The minimum supported Dokany version is 1.3.1. At the time of the writing,Dokany 2.0 is in Beta stage and is unsupported.
Unlike WNBD, Dokany isn’t included in the Ceph MSI installer.
MSI installer¶
Using the MSI installer is the recommended way of installing Ceph on Windows.It can be downloaded from here: https://cloudbase.it/ceph-for-windows/
As mentioned earlier, the Ceph installer does not include Dokany, which hasto be installed separately.
A server reboot is required after uninstalling the driver, otherwise subsequentinstall attempts may fail.
The following project allows building the MSI installer:https://github.com/cloudbase/ceph-windows-installer. It can either use prebuiltCeph and WNBD binaries or compile them from scratch.
Manual installation¶
Ceph Client Windows
The following document describes the build process and manual installation:https://github.com/ceph/ceph/blob/master/README.windows.rst
Ceph Client_cache_size
Configuration¶
Please check the Windows configuration sample to get started.
You’ll also need a keyring file. The General CephFS Prerequisites page provides asimple example, showing how a new CephX user can be created and how its secretkey can be retrieved.
For more details on CephX user management, see the Client Authenticationand User Management.