Users can now purge the dashboard and monitoring stack only

Previously, users could not purge only the Ceph Manager Dashboard and Monitoring stack components such as Alertmanager, Prometheus, Grafana, and node-exporter separately.

Purging the storage cluster with osd_auto_discovery: true now purges the cluster and removes the Ceph OSDs

Previously, purging the storage cluster deployed with osd_auto_discovery: true would not purge the Ceph OSDs. With this release, the purge playbook works as expected and removes the Ceph OSDs when the storage cluster is deployed with osd_auto_discovery: true scenario.

The Alertmanager configuration is customizable

With this release, you can customize the Alertmanager configuration using the alertmanager_conf_overrides parameter in the /group_vars/all.yml file.

The Red Hat Ceph Storage Dashboard deployment is supported on a dedicated network

Previously, ceph-ansible stated the address that should be used for deploying the dashboard was on the same subnet as the public_network.

Setting the global NFS options in the configuration file is supported

Previously, ceph-ansible would not allow overriding any parameter in the configuration file.

ceph-ansible checks for the Ceph Monitor quorum before starting the upgrade

Previously, when the storage cluster was in a HEALTH ERR or HEALTH WARN state due to one of the Ceph monitors being down, the rolling_upgrade.yml playbook would run. However, the upgrade would fail and the quorum was lost resulting in I/O down or a cluster failure.

The systemd target units for containerized deployments are now supported

Previously, there was no way to stop all Ceph daemons on a node in a containerized deployment.

ceph-ansible now checks the relevant release version during an upgrade before executing the playbook

With this release, during a storage cluster upgrade, ceph-ansible first checks for the relevant release version and the playbook fails with an error message if a wrong Ceph version is provided.

A new Grafana Dashboard to display graphs for Ceph Object Gateway multi-site setup

With this release, a new Grafana dashboard is now available and displays graphs for Ceph Object Gateway multisite sync performance including two-way replication throughput, polling latency, and unsuccessful replications.

Use max_concurrent_clones option to configure the number of clone threads

Previously, the number of concurrent clones was not configurable and the default was 4.

Syntax

ceph config set mgr mgr/volumes/max_concurrent_clones VALUE

The role name and the role session information is displayed in the ops log for S3 operations

With this release, you get information such as the role name and the role session in the ops log for all the S3 operations that use temporary credentials returned by AssumeRole* operations for debugging and auditing purposes.

Data sync logging experienced delays in processing

Previously, data sync logging could be subject to delays in processing large backlogs of log entries.

Mapping RBD images to NBD images

The rbd-nbd utility maps RADOS Block Device (RBD) images to Network Block Devices (NBD) and enables Ceph clients to access volumes and images in Kubernetes environments. To use rbd-nbd, install the rbd-nbd package. For details, see the rbd-nbd(7) manual page.

Object Gateway archive site

With this release an archive site is supported as a Technology Preview. The archive site allows you to have a history of versions of S3 objects that can only be eliminated through the gateways associated with the archive zone. Including an archive zone in a multizone configuration allows you to have the flexibility of an S3 object history in only one zone while saving the space that the replicas of the versions S3 objects would consume in the rest of the zones.

Alertmanager does not log errors when self-signed or untrusted certificates are used

Previously, when using untrusted CA certificates, Alertmanager generated many errors in the logs.

Use a fully-qualified domain name (FQDN) when HTTPS is enabled in a multi-site configuration

Previously, in a multi-site Ceph configuration, ceph-ansible would not differentiate between HTTP and HTTPS and set the zone endpoints with the IP address instead of the host name when HTTPS was enabled.

Add the --pid-limits parameter as -1 for podman and 0 for docker in the systemd file to start the container

Previously, the number of processes allowed to run in containers, 2048 for podman and 4096 for docker, were not sufficient to start some containers which needed to start more processes than these limits.

ceph-ansible pulls the monitoring container images in a dedicated task behind the proxy

Previously, ceph-ansible would not pull the monitoring container images such as Alertmanager, Prometheus, node-exporter, and Grafana in a dedicated task and would pull images when the systemd service was started.

The ceph-ansible playbook creates the radosgw system user and works as expected

Previously, the ceph-ansible playbook failed to create the radosgw system user and failed to deploy the dashboard when rgw_instances was set at the host_vars or group_vars level in a multi-site deployment. This variable is not set on Ceph Monitor nodes and given that this where the tasks are delegated, it failed.

The Ansible playbook does not fail when used with --limit option

Previously, the dashboard_server_addr parameter was unset when the Ansible playbook was run with the --limit option and the playbook would fail if the play target did not match the Ceph Manager hosts in a non-collocated scenario.

The “Client Connection” panel is replaced with “MGRs” on the Grafana dashboard

Previously, the “Client Connection” panel displayed the Ceph File System information and was not meaningful.

The Red Hat Ceph Storage Dashboard displays the values for disk IOPS

Previously, the Red Hat Ceph Storage Dashboard would not display the Ceph OSD disk performance in the Hosts tab.

The add-osd.yml playbook does not fail anymore while creating new OSDs

Previously, the add-osd.yml playbook would fail when new OSDs were added using ceph-ansible. This was due to the ceph-volume lvm batch limitation which does not allow addition of new OSDs in a non-interactive mode.

The rgw_bucket_quota_soft_threshold parameter is disabled

Previously, the Ceph Object Gateway fetched utilization information from the bucket index if the cached utilization reached rgw_bucket_quota_soft_threshold causing high operations on the bucket index and slower requests.

The radosgw-admin datalog trim command does not crash while trimming a marker

Previously, the radosgw-admin datalog trim command would crash when trimming a marker in the current generation from radosgw-admin due to a logic error.

The cluster health changes are no longer committed to persistent storage

Previously, rapid changes to the health of the storage cluster caused excessive logging to the ceph.audit.log.

Disk AVG utilization panel shows N/A on the Red Hat Ceph Storage Dashboard

The Red Hat Ceph Storage Dashboard displays a value of N/A on the Overall host performance AVG disk utilization panel thereby showing incorrect Grafana queries.

Lifecycle processing stuck in “PROCESSING” state for a given bucket

If a Ceph Object Gateway server is unexpectedly restarted when the lifecycle processing is in progress for a given bucket, that bucket does not resume processing lifecycle work for at least two scheduling cycles and is stuck in “PROCESSING” state. This is an expected behavior as it is intended to avoid multiple Ceph Object gateway instances or threads from processing the same bucket simultaneously, especially when the debugging is in progress in production. For future releases, the lifecycle processing shall restart on the following day, when debugging is not enabled.