Chapter 1. Upgrading a Red Hat Ceph Storage cluster from RHCS 4 to RHCS 5 As a storage administrator, you can upgrade a Red Hat Ceph Storage cluster from Red Hat Ceph Storage 4 to Red Hat Ceph Storage 5. The upgrade process includes the following tasks: Upgrade the host OS version on the storage cluster from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8, if your storage cluster is still running Red Hat Enterprise Linux 7. Upgrade the host OS version on the Ceph Ansible administration node from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8, if the node is still running Red Hat Enterprise Linux 7. Use Ansible playbooks to upgrade a Red Hat Ceph Storage 4 storage cluster to Red Hat Ceph Storage 5. Note If you are upgrading from Red Hat Ceph Storage 4.3 on Red Hat Enterprise Linux 7.9 to Red Hat Ceph Storage 5.2 on Red Hat Enterprise Linux 9, first upgrade the host OS from Red Hat Enterprise Linux 7.9 to Red Hat Enterprise Linux 8.x, upgrade Red Hat Ceph Storage, and then upgrade to Red Hat Enterprise Linux 9.x. Important If your Red Hat Ceph Storage 4 cluster is already running Red Hat Enterprise Linux 8, see Upgrading a Red Hat Ceph Storage running Red Hat Enterprise Linux 8 from RHCS4 to RHCS 5 . Important leapp does not support upgrades for encrypted OSDs or OSDs that have encrypted partitions. If your OSDs are encrypted and you are upgrading the host OS, disable dmcrypt in ceph-ansible before upgrading the OS. For more information about using leapp , see Upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 and Upgrading from Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 . Important ceph-ansible is currently not supported with Red Hat Ceph Storage 5. This means that once you have migrated your storage cluster to Red Hat Ceph Storage 5, you must use cephadm and cephadm-ansible to perform subsequent updates. Important While upgrading from Red Hat Ceph Storage 4 to Red Hat Ceph Storage 5, do not set bluestore_fsck_quick_fix_on_mount parameter to true or do not run the ceph-bluestore-tool --path PATH_TO_OSD --command quick-fix|repair commands as it might lead to improperly formatted OMAP keys and cause data corruption. Warning Upgrading to Red Hat Ceph Storage 5.2 from Red Hat Ceph Storage 5.0 on Ceph Object Gateway storage clusters (single-site or multi-site) is supported but you must set the ceph config set mgr mgr/cephadm/no_five_one_rgw true --force option prior to upgrading your storage cluster. Upgrading to Red Hat Ceph Storage 5.2 from Red Hat Ceph Storage 5.1 on Ceph Object Gateway storage clusters (single-site or multi-site) is not supported due to a known issue. For more information, see the knowledge base article Support Restrictions for upgrades for RADOS Gateway (RGW) on Red Hat Red Hat Ceph Storage 5.2 . Note Follow the knowledge base article How to upgrade from Red Hat Ceph Storage 4.2z4 to 5.0z4 with the upgrade procedure if you are planning to upgrade to Red Hat Ceph Storage 5.0z4. Important The option bluefs_buffered_io is set to True by default for Red Hat Ceph Storage. This option enables BlueFS to perform buffered reads in some cases, and enables the kernel page cache to act as a secondary cache for reads like RocksDB block reads. For example, if the RocksDB block cache is not large enough to hold all blocks during the OMAP iteration, it may be possible to read them from the page cache instead of the disk. This can dramatically improve performance when osd_memory_target is too small to hold all entries in the block cache. Currently, enabling bluefs_buffered_io and disabling the system level swap prevents performance degradation. For more information about viewing the current setting for bluefs_buffered_io , see the Viewing the bluefs_buffered_io setting section in the Red Hat Ceph Storage Administration Guide . Note Upon upgrading a cluster from Red Hat Ceph Storage 4 to Red Hat Ceph Storage 5, you need to upgrade ceph-common packages on all client nodes. To upgrade ceph-common packages, run the command yum update ceph-common on all clients post upgrade of other daemons. Red Hat Ceph Storage 5 supports only containerized daemons. It does not support non-containerized storage clusters. If you are upgrading a non-containerized storage cluster from Red Hat Ceph Storage 4 to Red Hat Ceph Storage 5, the upgrade process includes the conversion to a containerized deployment. 1.1. Prerequisites A running Red Hat Ceph Storage 4 cluster. A valid customer subscription. Root-level access to the Ansible administration node. Root-level access to all nodes in the storage cluster. The Ansible user account for use with the Ansible application. Red Hat Ceph Storage tools and Ansible repositories are enabled. Important You can manually upgrade the Ceph File System (CephFS) Metadata Server (MDS) software on a Red Hat Ceph Storage cluster and the Red Hat Enterprise Linux operating system to a new major release at the same time. The underlying XFS filesystem must be formatted with ftype=1 or with d_type support. Run the command xfs_info /var to ensure the ftype is set to 1 . If the value of ftype is not 1 , attach a new disk or create a volume. On top of this new device, create a new XFS filesystem and mount it on /var/lib/containers . Starting with Red Hat Enterprise Linux 8, mkfs.xfs enables ftype=1 by default. 1.2. Compatibility considerations between RHCS and podman versions podman and Red Hat Ceph Storage have different end-of-life strategies that might make it challenging to find compatible versions. If you plan to upgrade from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 as part of the Ceph upgrade process, make sure that the version of podman is compatible with Red Hat Ceph Storage 5. Red Hat recommends to use the podman version shipped with the corresponding Red Hat Enterprise Linux version for Red Hat Ceph Storage 5. See the Red Hat Ceph Storage: Supported configurations knowledge base article for more details. See the Contacting Red Hat support for service section in the Red Hat Ceph Storage Troubleshooting Guide for additional assistance. Important Red Hat Ceph Storage 5 is compatible with podman versions 2.0.0 and later, except for version 2.2.1. Version 2.2.1 is not compatible with Red Hat Ceph Storage 5. The following table shows version compatibility between Red Hat Ceph Storage 5 and versions of podman . Ceph Podman 1.9 2.0 2.1 2.2 3.0 5.0 (Pacific) false true true false true 1.3. Preparing for an upgrade As a storage administrator, you can upgrade your Ceph storage cluster to Red Hat Ceph Storage 5. However, some components of your storage cluster must be running specific software versions before an upgrade can take place. The following list shows the minimum software versions that must be installed on your storage cluster before you can upgrade to Red Hat Ceph Storage 5. Red Hat Ceph Storage 4.3 or later. Ansible 2.9. Ceph-ansible shipped with the latest version of Red Hat Ceph Storage. Red Hat Enterprise Linux 8.4 EUS or later. FileStore OSDs must be migrated to BlueStore. For more information about converting OSDs from FileStore to BlueStore, refer to BlueStore . There is no direct upgrade path from Red Hat Ceph Storage versions earlier than Red Hat Ceph Storage 4.3. If you are upgrading from Red Hat Ceph Storage 3, you must first upgrade to Red Hat Ceph Storage 4.3 or later, and then upgrade to Red Hat Ceph Storage 5. Important You can only upgrade to the latest version of Red Hat Ceph Storage 5. For example, if version 5.1 is available, you cannot upgrade from 4 to 5.0; you must go directly to 5.1. Important The new deployment of Red Hat Ceph Storage-4.3.z1 on Red Hat Enterprise Linux-8.7 (or higher) or Upgrade of Red Hat Ceph Storage-4.3.z1 to 5.X with host OS as Red Hat Enterprise Linux-8.7(or higher) fails at TASK [ceph-mgr : wait for all mgr to be up] . The behavior of podman released with Red Hat Enterprise Linux 8.7 had changed with respect to SELinux relabeling. Due to this, depending on their startup order, some Ceph containers would fail to start as they would not have access to the files they needed. As a workaround, refer to the knowledge base RHCS 4.3 installation fails while executing the command `ceph mgr dump` . To upgrade your storage cluster to Red Hat Ceph Storage 5, Red Hat recommends that your cluster be running Red Hat Ceph Storage 4.3 or later. Refer to the Knowledgebase article What are the Red Hat Ceph Storage Releases? . This article contains download links to the most recent versions of the Ceph packages and ceph-ansible. The upgrade process uses Ansible playbooks to upgrade an Red Hat Ceph Storage 4 storage cluster to Red Hat Ceph Storage 5. If your Red Hat Ceph Storage 4 cluster is a non-containerized cluster, the upgrade process includes a step to transform the cluster into a containerized version. Red Hat Ceph Storage 5 does not run on non-containerized clusters. If you have a mirroring or multisite configuration, upgrade one cluster at a time. Make sure that each upgraded cluster is running properly before upgrading another cluster. Important leapp does not support upgrades for encrypted OSDs or OSDs that have encrypted partitions. If your OSDs are encrypted and you are upgrading the host OS, disable dmcrypt in ceph-ansible before upgrading the OS. For more information about using leapp , refer to Upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 . Important Perform the first three steps in this procedure only if the storage cluster is not already running the latest version of Red Hat Ceph Storage 4. The latest version of Red Hat Ceph Storage 4 should be 4.3 or later. Prerequisites A running Red Hat Ceph Storage 4 cluster. Sudo-level access to all nodes in the storage cluster. A valid customer subscription. Root-level access to the Ansible administration node. The Ansible user account for use with the Ansible application. Red Hat Ceph Storage tools and Ansible repositories are enabled. Procedure Enable the Ceph and Ansible repositories on the Ansible administration node: Example Update Ansible: Example If the storage cluster you want to upgrade contains Ceph Block Device images that use the exclusive-lock feature, ensure that all Ceph Block Device users have permissions to create a denylist for clients: Syntax If the storage cluster was originally installed using Cockpit, create a symbolic link in the /usr/share/ceph-ansible directory to the inventory file where Cockpit created it, at /usr/share/ansible-runner-service/inventory/hosts : Change to the /usr/share/ceph-ansible directory: Create the symbolic link: To upgrade the cluster using ceph-ansible , create the symbolic link in the etc/ansible/hosts directory to the hosts inventory file: If the storage cluster was originally installed using Cockpit, copy the Cockpit-generated SSH keys to the Ansible user's ~/.ssh directory: Copy the keys: Syntax Replace ANSIBLE_USERNAME with the user name for Ansible. The usual default user name is admin . Example Set the appropriate owner, group, and permissions on the key files: Syntax Replace ANSIBLE_USERNAME with the username for Ansible. The usual default user name is admin . Example Additional Resources What are the Red Hat Ceph Storage Releases? For more information about converting from FileStore to BlueStore, refer to BlueStore . 1.4. Backing up the files before the host OS upgrade Note Perform the procedure in this section only if you are upgrading the host OS. If you are not upgrading the host OS, skip this section. Before you can perform the upgrade procedure, you must make backup copies of the files that you customized for your storage cluster, including keyring files and the yml files for your configuration as the ceph.conf file gets overridden when you execute any playbook. Prerequisites A running Red Hat Ceph Storage 4 cluster. A valid customer subscription. Root-level access to the Ansible administration node. The Ansible user account for use with the Ansible application. Red Hat Ceph Storage Tools and Ansible repositories are enabled. Procedure Make a backup copy of the /etc/ceph and /var/lib/ceph folders. Make a backup copy of the ceph.client.admin.keyring file. Make backup copies of the ceph.conf files from each node. Make backup copies of the /etc/ganesha/ folder on each node. If the storage cluster has RBD mirroring defined, then make backup copies of the /etc/ceph folder and the group_vars/rbdmirrors.yml file. 1.5. Converting to a containerized deployment This procedure is required for non-containerized clusters. If your storage cluster is a non-containerized cluster, this procedure transforms the cluster into a containerized version. Red Hat Ceph Storage 5 supports container-based deployments only. A cluster needs to be containerized before upgrading to RHCS 5.x. If your Red Hat Ceph Storage 4 storage cluster is already containerized, skip this section. Important This procedure stops and restarts a daemon. If the playbook stops executing during this procedure, be sure to analyze the state of the cluster before restarting. Prerequisites A running Red Hat Ceph Storage non-containerized 4 cluster. Root-level access to all nodes in the storage cluster. A valid customer subscription. Root-level access to the Ansible administration node. The Ansible user account for use with the Ansible application. Procedure If you are running a multisite setup, set rgw_multisite: false in all.yml . Ensure the group_vars/all.yml has the following default values for the configuration parameters: Note These values differ if you use a local registry and a custom image name. Optional: For two-way RBD mirroring configured using the command-line interface in a bare-metal storage cluster, the cluster does not migrate RBD mirroring. For such a configuration, follow the below steps before migrating the non-containerized storage cluster to a containerized deployment: Create a user on the Ceph client node: Syntax Example Change the username in the auth file in /etc/ceph directory: Example Import the auth file to add relevant permissions: Syntax Example Check the service name of the RBD mirror node: Example Add the rbd-mirror node to the /etc/ansible/hosts file: Example If you are using daemons that are not containerized, convert them to containerized format: Syntax The -vvvv option collects verbose logs of the conversion process. Example Once the playbook completes successfully, edit the value of rgw_multisite: true in the all.yml file and ensure the value of containerized_deployment is true . Note Ensure to remove the ceph-iscsi , libtcmu , and tcmu-runner packages from the admin node. 1.6. Updating the host operating system Red Hat Ceph Storage 5 is supported on Red Hat Enterprise Linux 8.4 EUS, 8.5, 8.6, 9.0, and 9.1. This procedure enables you to install Red Hat Ceph Storage 5 and Red Hat Enterprise Linux 8 on the nodes in the storage cluster. If you are already running Red Hat Enterprise Linux 8 on your storage cluster, skip this procedure. You must manually upgrade all nodes in the cluster to run the most recent versions of Red Hat Enterprise Linux and Red Hat Ceph Storage. Prerequisites A running Red Hat Ceph Storage 4 storage cluster. Sudo-level access to all nodes in the storage cluster. A valid customer subscription. Root-level access to the Ansible administration node. The Ansible user account for use with the Ansible application. Red Hat Ceph Storage tools and Ansible repositories are enabled. Procedure Use the docker-to-podman playbook to convert docker to podman: Example Additional Resources Upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 . Upgrading from Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 . 1.6.1. Manually upgrading Ceph Monitor nodes and their operating systems As a system administrator, you can manually upgrade the Ceph Monitor software on a Red Hat Ceph Storage cluster node and the Red Hat Enterprise Linux operating system to a new major release at the same time. Important Perform the procedure on only one Monitor node at a time. To prevent cluster access issues, ensure that the current upgraded Monitor node has returned to normal operation before proceeding to the node. Prerequisites A running Red Hat Ceph Storage cluster. The nodes are running Red Hat Enterprise Linux 7.9. The nodes are using Red Hat Ceph Storage version 4.3 or later. Access to the installation source is available for Red Hat Enterprise Linux 8.4 EUS or later. Important If you are upgrading from Red Hat Ceph Storage 4.3 on Red Hat Enterprise Linux 7.9 to Red Hat Ceph Storage 5 on Red Hat Enterprise Linux 9, first upgrade the host OS from Red Hat Enterprise Linux 7.9 to Red Hat Enterprise Linux 8.x, upgrade Red Hat Ceph Storage, and then upgrade to Red Hat Enterprise Linux 9.x. Procedure Stop the monitor service: Syntax Replace MONITOR_ID with the Monitor node's ID number. If using Red Hat Ceph Storage 4, disable the Red Hat Ceph Storage 4 repositories. Disable the tools repository: Disable the mon repository: After upgrading a storage cluster using the leapp utility, many of the Ceph packages are removed. Make a note of the Ceph packages prior to upgrade: Example Install the leapp utility. For Red Hat Enterprise Linux 8, see Upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 . For Red Hat Enterprise Linux 9, see Upgrading from Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 . Run through the leapp preupgrade checks. See Assessing upgradability from the command line . After upgrading to Red Hat Enterprise Linux 8.6, install the Ceph-Ansible packages and run the Ansible playbook: Install Ceph-Ansible which installs all the Ceph packages: As the ansible user, run the Ansible playbook on all the upgraded nodes: Bare-metal deployments: Container deployments: After upgrading to Red Hat Enterprise Linux 9.x, copy the podman-auth.json file from the other node to the upgraded node in /etc/ceph/` and then restart each service. Set PermitRootLogin yes in /etc/ssh/sshd_config . Restart the OpenSSH SSH daemon: Remove the iSCSI module from the Linux kernel: Reboot the node. Enable the repositories for Red Hat Ceph Storage 5: Enable the tools repository: Red Hat Enterprise Linux 8 Red Hat Enterprise Linux 9 Restore the ceph-client-admin.keyring and ceph.conf files from a Monitor node which has not been upgraded yet or from a node that has already had those files restored. Restart the Ceph Monitor services: Example Verify that the monitor and manager services came back up and that the monitor is in quorum. Syntax On the mon: line under services: , ensure that the node is listed as in quorum and not as out of quorum . Example Repeat the above steps on all Monitor nodes until they have all been upgraded. Additional Resources See Updating the host operating system for more information. See Upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 for more information. See Upgrading from Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 for more information. 1.6.2. Upgrading the OSD nodes As a system administrator, you can manually upgrade the Ceph OSD software on a Red Hat Ceph Storage cluster node and the Red Hat Enterprise Linux operating system to a new major release at the same time. Important Perform this procedure for each OSD node in the Ceph cluster, but typically only for one OSD node at a time. A maximum of one failure domain's worth of OSD nodes may be performed in parallel. For example, if per-rack replication is in use, one entire rack's OSD nodes can be upgraded in parallel. To prevent data access issues, ensure that the OSDs of the current OSD node have returned to normal operation and that all of the cluster PGs are in the active+clean state before proceeding to the OSD. Important If you are upgrading from Red Hat Ceph Storage 4.3 on Red Hat Enterprise Linux 7.9 to Red Hat Ceph Storage 5.2 on Red Hat Enterprise Linux 9, first upgrade the host OS from Red Hat Enterprise Linux 7.9 to Red Hat Enterprise Linux 8.x, upgrade Red Hat Ceph Storage, and then upgrade to Red Hat Enterprise Linux 9.x. Prerequisites A running Red Hat Ceph Storage cluster. The nodes are running Red Hat Enterprise Linux 7.9. The nodes are using Red Hat Ceph Storage version 4.3 or later. Access to the installation source for Red Hat Enterprise Linux 8.4 EUS or later. FileStore OSDs must be migrated to BlueStore. Procedure If you have FileStore OSDs that have not been migrated to BlueStore, run the filestore-to-bluestore playbook. For more information about converting OSDs from FileStore to BlueStore, refer to BlueStore . Set the OSD noout flag to prevent OSDs from getting marked down during the migration: Syntax Set the OSD nobackfill , norecover , norrebalance , noscrub and nodeep-scrub flags to avoid unnecessary load on the cluster and to avoid any data reshuffling when the node goes down for migration: Syntax Gracefully shut down all the OSD processes on the node: Syntax If using Red Hat Ceph Storage 4, disable the Red Hat Ceph Storage 4 repositories. Disable the tools repository: Syntax Disable the osd repository: Syntax Install the leapp utility. See Upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 . Run through the leapp preupgrade checks. See Assessing upgradability from the command line . Set PermitRootLogin yes in /etc/ssh/sshd_config . Restart the OpenSSH SSH daemon: Syntax Remove the iSCSI module from the Linux kernel: Syntax Perform the upgrade by following Performing the upgrade from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 and Performing the upgrade from Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 Enable the tools repository: Red Hat Enterprise Linux 8 Red Hat Enterprise Linux 9 Restore the ceph.conf file. Unset the noout , nobackfill , norecover , norebalance , noscrub and nodeep-scrub flags: Syntax Verify that the OSDs are up and in , and that they are in the active+clean state. Syntax On the osd: line under services: , ensure that all OSDs are up and in : Example Repeat this procedure on all OSD nodes until they have all been upgraded. Additional Resources Refer to BlueStore for more information about converting OSDs from FileStore to BlueStore. For more information about the leapp utility, see Upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 . For more information about converting docker to podman, see Updating the host operating system . 1.6.3. Upgrading the Ceph Object Gateway nodes As a system administrator, you can manually upgrade the Ceph Object Gateway (RGW) software on a Red Hat Ceph Storage cluster node and the Red Hat Enterprise Linux operating system to a new major release at the same time. Important Perform this procedure for each RGW node in the Ceph cluster, but only for one RGW node at a time. To prevent client access issues, ensure that the current upgraded RGW has returned to normal operation before proceeding to upgrade the node. Note Upon upgrading, ensure that the radosgw-admin tool and the Ceph Object Gateway storage cluster have the same version. When the storage cluster is upgraded, it is very important to upgrade the radosgw-admin tool at the same time. The use of mismatched versions is not supported. Prerequisites A running Red Hat Ceph Storage cluster. The nodes are running Red Hat Enterprise Linux 7.9. The nodes are using Red Hat Ceph Storage version 4.3 or later. Access to the installation source for Red Hat Enterprise Linux 8.4 EUS, 8.5, 8.6, 9.0, and 9.1. Procedure Stop the Ceph Object Gateway service: Syntax Disable the Red Hat Ceph Storage 4 tools repository: Install the leapp utility. For Red Hat Enterprise Linux 8, see Upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 . For Red Hat Enterprise Linux 9, see Upgrading from Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 . Run through the leapp preupgrade checks: For Red Hat Enterprise Linux 8, see Assessing upgradability from the command line . For Red Hat Enterprise Linux 9, see Assessing upgradability from the command line . Set PermitRootLogin yes in /etc/ssh/sshd_config . If the buckets are created or have the num_shards = 0 , manually reshard the buckets, before planning an upgrade to Red Hat Ceph Storage 5.3: Warning Upgrade to Red Hat Ceph Storage 5.3 from older releases when bucket_index_max_shards is 0 can result in the loss of the Ceph Object Gateway bucket's metadata leading to the bucket's unavailability while trying to access it. Hence, ensure bucket_index_max_shards is set to 11 shards. If not, modify this configuration at the zonegroup level. Syntax Example Restart the OpenSSH SSH daemon: Remove the iSCSI module from the Linux kernel: Perform the upgrade by following Performing the upgrade from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 . Enable the tools repository: Red Hat Enterprise Linux 8 Red Hat Enterprise Linux 9 Restore the ceph-client-admin.keyring and ceph.conf files. Verify that the daemon is active: Syntax View the rgw: line under services: to make sure that the RGW daemon is active. Example Repeat the above steps on all Ceph Object Gateway nodes until they have all been upgraded. Additional Resources See Upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 for more information about the leapp utility. See Upgrading from Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 for more information about the leapp utility. 1.6.4. Upgrading the CephFS Metadata Server nodes As a storage administrator, you can manually upgrade the Ceph File System (CephFS) Metadata Server (MDS) software on a Red Hat Ceph Storage cluster and the Red Hat Enterprise Linux operating system to a new major release at the same time. Important Before you upgrade the storage cluster, reduce the number of active MDS ranks to one per file system. This eliminates any possible version conflicts between multiple MDS. In addition, take all standby nodes offline before upgrading. This is because the MDS cluster does not possess built-in versioning or file system flags. Without these features, multiple MDS might communicate using different versions of the MDS software, and could cause assertions or other faults to occur. Prerequisites A running Red Hat Ceph Storage cluster. The nodes are running Red Hat Enterprise Linux 7.9. The nodes are using Red Hat Ceph Storage version 4.3 or later. Access to the installation source for Red Hat Enterprise Linux 8.4 EUS, 8.5, 8.6, 9.0, and 9.1. Root-level access to all nodes in the storage cluster. Procedure Reduce the number of active MDS ranks to 1: Syntax Example Wait for the cluster to stop all of the MDS ranks. When all of the MDS have stopped, only rank 0 should be active. The rest should be in standby mode. Check the status of the file system: Use systemctl to take all standby MDS offline: Confirm that only one MDS is online, and that it has rank 0 for the file system: Disable the Red Hat Ceph Storage 4 tools repository: Install the leapp utility. For Red Hat Enterprise Linux 8, see Upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 . For Red Hat Enterprise Linux 9, see Upgrading from Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 . Run through the leapp preupgrade checks: For Red Hat Enterprise Linux 8, see Assessing upgradability from the command line . For Red Hat Enterprise Linux 9, see Assessing upgradability from the command line . Edit /etc/ssh/sshd_config and set PermitRootLogin to yes . Restart the OpenSSH SSH daemon: Remove the iSCSI module from the Linux kernel: Perform the upgrade: For Red Hat Enterprise Linux 8, see Performing the upgrade from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 . For Red Hat Enterprise Linux 9, see Performing the upgrade from Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 . Enable the tools repository: Red Hat Enterprise Linux 8 Red Hat Enterprise Linux 9 Restore the ceph-client-admin.keyring and ceph.conf files. Verify that the daemon is active: Follow the same processes for the standby daemons. When you have finished restarting all of the MDS in standby, restore the value of max_mds for your cluster: Syntax Example Additional Resources See Upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 for more information about the leapp utility. 1.6.5. Manually upgrading the Ceph Dashboard node and its operating system As a system administrator, you can manually upgrade the Ceph Dashboard software on a Red Hat Ceph Storage cluster node and the Red Hat Enterprise Linux operating system to a new major release at the same time. Prerequisites A running Red Hat Ceph Storage cluster. The node is running Red Hat Enterprise Linux 7.9. The node is running Red Hat Ceph Storage version 4.3 or later. Access is available to the installation source for Red Hat Enterprise Linux 8.4 EUS, 8.5, 8.6, 9.0, or 9.1. Procedure Disable the Red Hat Ceph Storage 4 tools repository: Install the leapp utility. For Red Hat Enterprise Linux 8, see Upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 . For Red Hat Enterprise Linux 9, see Upgrading from Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 . Run through the leapp preupgrade checks: For Red Hat Enterprise Linux 8, see Assessing upgradability from the command line . For Red Hat Enterprise Linux 9, see Assessing upgradability from the command line . Set PermitRootLogin yes in /etc/ssh/sshd_config . Restart the OpenSSH SSH daemon: Remove the iSCSI module from the Linux kernel: Perform the upgrade: For Red Hat Enterprise Linux 8, see Performing the upgrade from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 . For Red Hat Enterprise Linux 9, see Performing the upgrade from Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 . Enable the tools repository for Red Hat Ceph Storage 5: Red Hat Enterprise Linux 8 Red Hat Enterprise Linux 9 Additional Resources See Upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 for more information. 1.6.6. Manually upgrading Ceph Ansible nodes and reconfiguring settings Manually upgrade the Ceph Ansible software on a Red Hat Ceph Storage cluster node and the Red Hat Enterprise Linux operating system to a new major release at the same time. Important Before upgrading the host OS on the Ceph Ansible nodes, back up the group_vars and hosts files. Use the created backups before reconfiguring the Ceph Ansible nodes. Prerequisites A running Red Hat Ceph Storage cluster. The node is running Red Hat Enterprise Linux 7.9. The node is running Red Hat Ceph Storage version 4.2z2 or later. Access is available to the installation source for Red Hat Enterprise Linux 8.4 EUS or Red Hat Enterprise Linux 8.5. Procedure Disable the tools repository for Red Hat Ceph Storage 4 for Red Hat Enterprise Linux 8: Install the leapp utility. For Red Hat Enterprise Linux 8, see Upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 . For Red Hat Enterprise Linux 9, see Upgrading from Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 . Run through the leapp preupgrade checks: For Red Hat Enterprise Linux 8, see Assessing upgradability from the command line . For Red Hat Enterprise Linux 9, see Assessing upgradability from the command line . Edit /etc/ssh/sshd_config and set PermitRootLogin to yes . Restart the OpenSSH SSH daemon: Remove the iSCSI module from the Linux kernel: Perform the upgrade: For Red Hat Enterprise Linux 8, see Upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 . For Red Hat Enterprise Linux 9, see Upgrading from Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 . Enable the tools repository for Red Hat Ceph Storage 5: Red Hat Enterprise Linux 8 Red Hat Enterprise Linux 9 Restore the ceph-client-admin.keyring and ceph.conf files. Additional Resources See Updating the host operating system for more information. See Upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 for more information. 1.7. Restoring the backup files After you have completed the host OS upgrade on each node in your storage cluster, restore all the files that you backed up earlier to each node so that your upgraded node uses your preserved settings. Repeat this process on each host in your storage cluster after the OS upgrade process for that host is complete. Prerequisites A running Red Hat Ceph Storage cluster. Root-level access to all nodes in the storage cluster. Procedure Restore the files that you backed up before the host OS upgrade to the host. Restore the /etc/ceph folders and their contents to all of the hosts, including the ceph.client.admin.keyring and ceph.conf files. Restore the /etc/ganesha/ folder to each node. Check to make sure that the ownership for each of the backed-up files has not changed after the operating system upgrade. The file owner should be ceph . If the file owner has been changed to root , use the following command on each file to change the ownership back to ceph : Example If you upgraded from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 and the storage cluster had RBD mirroring defined, restore the /etc/ceph folder from the backup copy. Restore the group_vars/rbdmirrors.yml file that you backed up earlier. Change the ownership of the folders on all nodes: Example 1.8. Backing up the files before the RHCS upgrade Before you run the rolling_update.yml playbook to upgrade Red Hat Ceph Storage 4 to Red Hat Ceph Storage 5, make backup copies of all the yml files. Prerequisites A Red Hat Ceph Storage 4 cluster running RHCS 4.3 or later. A valid customer subscription. Root-level access to the Ansible administration node. The Ansible user account for use with the Ansible application. Red Hat Ceph Storage tools and Ansible repositories are enabled. Procedure Make backup copies of all the yml files. Example 1.9. The upgrade process As a storage administrator, you use Ansible playbooks to upgrade an Red Hat Ceph Storage 4 storage cluster to Red Hat Ceph Storage 5. The rolling_update.yml Ansible playbook performs upgrades for deployments of Red Hat Ceph Storage. The ceph-ansible upgrades the Ceph nodes in the following order: Ceph Monitor Ceph Manager Ceph OSD nodes MDS nodes Ceph Object Gateway (RGW) nodes Ceph RBD-mirror node Ceph NFS nodes Ceph iSCSI gateway node Ceph client nodes Ceph-crash daemons Node-exporter on all nodes Ceph Dashboard Important After the storage cluster is upgraded from Red Hat Ceph Storage 4 to Red Hat Ceph Storage 5, the Grafana UI shows two dashboards. This is because the port for Prometheus in Red Hat Ceph Storage 4 is 9092 while for Red Hat Ceph Storage 5 is 9095. You can remove the grafana. The cephadm redeploys the service and the daemons and removes the old dashboard on the Grafana UI. Note Red Hat Ceph Storage 5 supports only containerized deployments. ceph-ansible is currently not supported with Red Hat Ceph Storage 5. This means that once you have migrated your storage cluster to Red Hat Ceph Storage 5, you must use cephadm to perform subsequent updates. Important To deploy multi-site Ceph Object Gateway with single realm and multiple realms, edit the all.yml file. For more information, see the Configuring multi-site Ceph Object Gateways in the Red Hat Ceph Storage 4 Installation Guide. Note Red Hat Ceph Storage 5 also includes a health check function that returns a DAEMON_OLD_VERSION warning if it detects that any of the daemons in the storage cluster are running multiple versions of Red Hat Ceph Storage. The warning is triggered when the daemons continue to run multiple versions of Red Hat Ceph Storage beyond the time value set in the mon_warn_older_version_delay option. By default, the mon_warn_older_version_delay option is set to one week. This setting allows most upgrades to proceed without falsely seeing the warning. If the upgrade process is paused for an extended time period, you can mute the health warning: After the upgrade has finished, unmute the health warning: Prerequisites A running Red Hat Ceph Storage cluster. Root-level access to all hosts in the storage cluster. A valid customer subscription. Root-level access to the Ansible administration node. The latest versions of Ansible and ceph-ansible available with Red Hat Ceph Storage 5. The ansible user account for use with the Ansible application. The nodes of the storage cluster is upgraded to Red Hat Enterprise Linux 8.4 EUS or later. Important The Ansible inventory file must be present in the ceph-ansible directory. Procedure Enable the Ceph and Ansible repositories on the Ansible administration node: Red Hat Enterprise Linux 8 Red Hat Enterprise Linux 9 On the Ansible administration node, ensure that the latest versions of the ansible and ceph-ansible packages are installed. Syntax Navigate to the /usr/share/ceph-ansible/ directory: Example If upgrading from Red Hat Ceph Storage 4 to Red Hat Ceph Storage 5, make copies of the group_vars/osds.yml.sample and group_vars/clients.yml.sample files, and rename them to group_vars/osds.yml , and group_vars/clients.yml respectively. Example If upgrading from Red Hat Ceph Storage 4 to Red Hat Ceph Storage 5, edit the group_vars/all.yml file to add Red Hat Ceph Storage 5 details. Once you have done the above two steps, copy the settings from the old yaml files to the new yaml files. Do not change the values of ceph_rhcs_version , ceph_docker_image , and grafana_container_image as the values for these configuration parameters are for Red Hat Ceph Storage 5. This ensures that all the settings related to your cluster are present in the current yaml file. Example Note Ensure the Red Hat Ceph Storage 5 container images are set to the default values. Edit the group_vars/osds.yml file. Add and set the following options: Syntax Open the group_vars/all.yml file and verify the following values are present from the old all.yml file. The fetch_directory option is set with the same value from the old all.yml file: Syntax Replace FULL_DIRECTORY_PATH with a writable location, such as the Ansible user's home directory. If the cluster you want to upgrade contains any Ceph Object Gateway nodes, add the radosgw_interface option: Replace INTERFACE with the interface to which the Ceph Object Gateway nodes listen. If your current setup has SSL certificates configured, edit the following: Syntax Uncomment the upgrade_ceph_packages option and set it to True : Syntax If the storage cluster has more than one Ceph Object Gateway instance per node, then uncomment the radosgw_num_instances setting and set it to the number of instances per node in the cluster: Syntax Example If the storage cluster has Ceph Object Gateway multi-site defined, check the multisite settings in all.yml to make sure that they contain the same values as they did in the old all.yml file. If the buckets are created or have the num_shards = 0 , manually reshard the buckets, before planning an upgrade to Red Hat Ceph Storage 5.3: Warning Upgrade to Red Hat Ceph Storage 5.3 from older releases when bucket_index_max_shards is 0 can result in the loss of the Ceph Object Gateway bucket's metadata leading to the bucket's unavailability while trying to access it. Hence, ensure bucket_index_max_shards is set to 11 shards. If not, modify this configuration at the zonegroup level. Syntax Example Log in as ansible-user on the Ansible administration node. Use the --extra-vars option to update the infrastructure-playbooks/rolling_update.yml playbook and to change the health_osd_check_retries and health_osd_check_delay values to 50 and 30 , respectively: Example For each OSD node, these values cause ceph-ansible to check the storage cluster health every 30 seconds, up to 50 times. This means that ceph-ansible waits up to 25 minutes for each OSD. Adjust the health_osd_check_retries option value up or down, based on the used storage capacity of the storage cluster. For example, if you are using 218 TB out of 436 TB, or 50% of the storage capacity, then set the health_osd_check_retries option to 50 . /etc/ansible/hosts is the default location for the Ansible inventory file. Run the rolling_update.yml playbook to convert the storage cluster from Red Hat Ceph Storage 4 to Red Hat Ceph Storage 5: Syntax The -vvvv option collects verbose logs of the upgrade process. Example Important Using the --limit Ansible option with the rolling_update.yml playbook is not supported. Review the Ansible playbook log output to verify the status of the upgrade. Verification List all running containers: Example Check the health status of the cluster. Replace MONITOR_ID with the name of the Ceph Monitor container found in the step: Syntax Example Verify the Ceph cluster daemon versions to confirm the upgrade of all daemons. Replace MONITOR_ID with the name of the Ceph Monitor container found in the step: Syntax Example 1.10. Converting the storage cluster to using cephadm After you have upgraded the storage cluster to Red Hat Ceph Storage 5, run the cephadm-adopt playbook to convert the storage cluster daemons to run cephadm . The cephadm-adopt playbook adopts the Ceph services, installs all cephadm dependencies, enables the cephadm Orchestrator backend, generates and configures the ssh key on all hosts, and adds the hosts to the Orchestrator configuration. Note After you run the cephadm-adopt playbook, remove the ceph-ansible package. The cluster daemons no longer work with ceph-ansible . You must use cephadm to manage the cluster daemons. Prerequisites A running Red Hat Ceph Storage cluster. Root-level access to all nodes in the storage cluster. Procedure Log in to the ceph-ansible node and change directory to /usr/share/ceph-ansible . Edit the all.yml file. Syntax Example Run the cephadm-adopt playbook: Syntax Example Set the minimum compat client parameter to luminous : Example Run the following command to enable applications to run on the NFS-Ganesha pool. POOL_NAME is nfs-ganesha , and APPLICATION_NAME is the name of the application you want to enable, such as cephfs , rbd , or rgw . Syntax Example Important The cephadm-adopt playbook does not bring up rbd-mirroring after migrating the storage cluster from Red Hat Ceph Storage 4 to Red Hat Ceph Storage 5. To work around this issue, add the peers manually: Syntax Example Remove Grafana after upgrade: Log in to the Cephadm shell: Example Fetch the name of Grafana in your storage cluster: Example Remove Grafana: Syntax Example Wait a few minutes and check the latest log: Example cephadm redeploys the Grafana service and the daemon. Additional Resources For more information about using leapp to upgrade Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8, see Upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 . For more information about using leapp to upgrade Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9, see Upgrading from Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 . For more information about converting from FileStore to BlueStore, refer to BlueStore . For more information about storage peers, see Viewing information about peers . 1.11. Installing cephadm-ansible on an upgraded storage cluster cephadm-ansible is a collection of Ansible playbooks to simplify workflows that are not covered by cephadm . After installation, the playbooks are located in /usr/share/cephadm-ansible/ . Note Before adding new nodes or new clients to your upgraded storage cluster, run the cephadm-preflight.yml playbook. Prerequisites Root-level access to the Ansible administration node. A valid Red Hat subscription with the appropriate entitlements. An active Red Hat Network (RHN) or service account to access the Red Hat Registry. Procedure Uninstall ansible and the older ceph-ansible packages: Syntax Disable Ansible repository and enable Ceph repository on the Ansible administration node: Red Hat Enterprise Linux 8 Red Hat Enterprise Linux 9 Install the cephadm-ansible package, which installs the ansible-core as a dependency: Syntax Additional Resources Running the preflight playbook Adding hosts Adding Monitor service Adding Manager service Adding OSDs For more information about configuring clients and services, see Red Hat Ceph Storage Operations Guide . For more information about the cephadm-ansible playbooks, see The cephadm-ansible playbooks .

Commands:
subscription-manager repos --enable=rhceph-4-tools-for-rhel-8-x86_64-rpms --enable=ansible-2.9-for-rhel-8-x86_64-rpms
dnf update ansible ceph-ansible
ceph auth caps client. ID mon 'profile rbd' osd 'profile rbd pool= POOL_NAME_1 , profile rbd pool= POOL_NAME_2 '
cd /usr/share/ceph-ansible
ln -s /usr/share/ansible-runner-service/inventory/hosts hosts
ln -s /etc/ansible/hosts hosts
cp /usr/share/ansible-runner-service/env/ssh_key.pub /home/ ANSIBLE_USERNAME /.ssh/id_rsa.pub cp /usr/share/ansible-runner-service/env/ssh_key /home/ ANSIBLE_USERNAME /.ssh/id_rsa
cp /usr/share/ansible-runner-service/env/ssh_key.pub /home/admin/.ssh/id_rsa.pub cp /usr/share/ansible-runner-service/env/ssh_key /home/admin/.ssh/id_rsa
chown ANSIBLE_USERNAME : ANSIBLE_USERNAME /home/ ANSIBLE_USERNAME /.ssh/id_rsa.pub chown ANSIBLE_USERNAME : ANSIBLE_USERNAME /home/ ANSIBLE_USERNAME /.ssh/id_rsa chmod 644 /home/ ANSIBLE_USERNAME /.ssh/id_rsa.pub chmod 600 /home/ ANSIBLE_USERNAME /.ssh/id_rsa
chown admin:admin /home/admin/.ssh/id_rsa.pub chown admin:admin /home/admin/.ssh/id_rsa chmod 644 /home/admin/.ssh/id_rsa.pub chmod 600 /home/admin/.ssh/id_rsa
ceph_docker_image_tag: "latest" ceph_docker_registry: "registry.redhat.io" ceph_docker_image: rhceph/rhceph-4-rhel8 containerized_deployment: true
ceph auth get client.PRIMARY_CLUSTER_NAME -o /etc/ceph/ceph.PRIMARY_CLUSTER_NAME.keyring
ceph auth get client.rbd-mirror.site-a -o /etc/ceph/ceph.client.rbd-mirror.site-a.keyring
[client.rbd-mirror.rbd-client-site-a] key = AQCbKbVg+E7POBAA7COSZCodvOrg2LWIFc9+3g== caps mds = "allow *" caps mgr = "allow *" caps mon = "allow *" caps osd = "allow *"
ceph auth import -i PATH_TO_KEYRING
ceph auth import -i /etc/ceph/ceph.client.rbd-mirror.rbd-client-site-a.keyring
systemctl list-units --all systemctl stop ceph-rbd-mirror@rbd-client-site-a.service systemctl disable ceph-rbd-mirror@rbd-client-site-a.service systemctl reset-failed ceph-rbd-mirror@rbd-client-site-a.service systemctl start ceph-rbd-mirror@rbd-mirror.rbd-client-site-a.service systemctl enable ceph-rbd-mirror@rbd-mirror.rbd-client-site-a.service systemctl status ceph-rbd-mirror@rbd-mirror.rbd-client-site-a.service
[rbdmirrors] ceph.client.rbd-mirror.rbd-client-site-a
ansible-playbook -vvvv -i INVENTORY_FILE infrastructure-playbooks/switch-from-non-containerized-to-containerized-ceph-daemons.yml
[ceph-admin@admin ceph-ansible]USD ansible-playbook -vvvv -i hosts infrastructure-playbooks/switch-from-non-containerized-to-containerized-ceph-daemons.yml
[ceph-admin@admin ceph-ansible]USD ansible-playbook -vvvv -i hosts infrastructure-playbooks/ docker-to-podman.yml
systemctl stop ceph-mon@ MONITOR_ID
subscription-manager repos --disable=rhel-7-server-rhceph-4-tools-rpms
subscription-manager repos --disable=rhel-7-server-rhceph-4-mon-rpms
rpm -qa | grep ceph python-ceph-argparse-14.2.22-128.el7cp.x86_64 ceph-selinux-14.2.22-128.el7cp.x86_64 python-cephfs-14.2.22-128.el7cp.x86_64 ceph-base-14.2.22-128.el7cp.x86_64 ceph-mon-14.2.22-128.el7cp.x86_64 ceph-mgr-diskprediction-local-14.2.22-128.el7cp.noarch ceph-ansible-4.0.70.18-1.el7cp.noarch libcephfs2-14.2.22-128.el7cp.x86_64 ceph-common-14.2.22-128.el7cp.x86_64 ceph-osd-14.2.22-128.el7cp.x86_64 ceph-mgr-14.2.22-128.el7cp.x86_64
dnf install ceph-ansible
[user@admin ceph-ansible]USD ansible-playbook -vvvv -i INVENTORY site.yml --limit osds|rgws|clients|mdss|nfss|iscsigw -i hosts
[ansible@admin ceph-ansible]USD ansible-playbook -vvvv -i INVENTORY site-container.yml --limit osds|rgws|clients|mdss|nfss|iscsigw -i hosts
systemctl restart _SERVICE NAME_
systemctl restart sshd.service
modprobe -r iscsi
subscription-manager repos --enable=rhceph-5-tools-for-rhel-8-x86_64-rpms
subscription-manager repos --enable=rhceph-5-tools-for-rhel-9-x86_64-rpms
systemctl restart ceph-mon@host01.service systemctl status ceph-mon@host01.service
ceph -s
ceph -s mon: 3 daemons, quorum node0,node1,node2 (age 2h) mgr: node0(active, since 2h), standbys: node1, node2
ceph osd set noout
ceph osd set nobackfill ceph osd set norecover ceph osd set norebalance ceph osd set noscrub ceph osd set nodeep-scrub
systemctl stop ceph-osd.target
subscription-manager repos --disable=rhel-7-server-rhceph-4-tools-rpms
subscription-manager repos --disable=rhel-7-server-rhceph-4-osd-rpms
systemctl restart sshd.service
modprobe -r iscsi
subscription-manager repos --enable=rhceph-5-tools-for-rhel-8-x86_64-rpms
subscription-manager repos --enable=rhceph-5-tools-for-rhel-9-x86_64-rpms
ceph osd unset noout ceph osd unset nobackfill ceph osd unset norecover ceph osd unset norebalance ceph osd unset noscrub ceph osd unset nodeep-scrub
ceph -s
ceph -s osd: 3 osds: 3 up (since 8s), 3 in (since 3M)
systemctl stop ceph-radosgw.target
subscription-manager repos --disable=rhel-7-server-rhceph-4-tools-rpms
radosgw-admin bucket reshard --num-shards 11 --bucket BUCKET_NAME
radosgw-admin bucket reshard --num-shards 11 --bucket mybucket
systemctl restart sshd.service
modprobe -r iscsi
subscription-manager repos --enable=rhceph-5-tools-for-rhel-8-x86_64-rpms
subscription-manager repos --enable=rhceph-5-tools-for-rhel-9-x86_64-rpms
ceph -s
rgw: 1 daemon active (node4.rgw0)
ceph fs set FILE_SYSTEM_NAME max_mds 1
ceph fs set fs1 max_mds 1
ceph status
systemctl stop ceph-mds.target
ceph status
subscription-manager repos --disable=rhel-7-server-rhceph-4-tools-rpms
systemctl restart sshd.service
modprobe -r iscsi
subscription-manager repos --enable=rhceph-5-tools-for-rhel-8-x86_64-rpms
subscription-manager repos --enable=rhceph-5-tools-for-rhel-9-x86_64-rpms
ceph -s
ceph fs set FILE_SYSTEM_NAME max_mds ORIGINAL_VALUE
ceph fs set fs1 max_mds 5
subscription-manager repos --disable=rhel-7-server-rhceph-4-tools-rpms
systemctl restart sshd.service
modprobe -r iscsi
subscription-manager repos --enable=rhceph-5-tools-for-rhel-8-x86_64-rpms
subscription-manager repos --enable=rhceph-5-tools-for-rhel-9-x86_64-rpms
subscription-manager repos --disable=rhceph-4-tools-for-rhel-8-x86_64-rpms subscription-manager repos --disable=ansible-2.9-for-rhel-8-x86_64-rpms
systemctl restart sshd.service
modprobe -r iscsi
subscription-manager repos --enable=rhceph-5-tools-for-rhel-8-x86_64-rpms
subscription-manager repos --enable=rhceph-5-tools-for-rhel-9-x86_64-rpms
chown ceph: ceph.client.rbd-mirror.node1.keyring
chown -R /etc/ceph chown -R /var/log/ceph chown -R /var/lib/ceph
cp group_vars/all.yml group_vars/all_old.yml cp group_vars/osds.yml group_vars/osds_old.yml cp group_vars/mdss.yml group_vars/mdss_old.yml cp group_vars/rgws.yml group_vars/rgws_old.yml cp group_vars/clients.yml group_vars/clients_old.yml
ceph health mute DAEMON_OLD_VERSION --sticky
ceph health unmute DAEMON_OLD_VERSION
subscription-manager repos --enable=rhceph-5-tools-for-rhel-8-x86_64-rpms --enable=ansible-2.9-for-rhel-8-x86_64-rpms
subscription-manager repos --enable=rhceph-5-tools-for-rhel-9-x86_64-rpms
dnf update ansible ceph-ansible
cd /usr/share/ceph-ansible
cp group_vars/osds.yml.sample group_vars/osds.yml cp group_vars/mdss.yml.sample group_vars/mdss.yml cp group_vars/rgws.yml.sample group_vars/rgws.yml cp group_vars/clients.yml.sample group_vars/clients.yml
fetch_directory: ~/ceph-ansible-keys monitor_interface: eth0 public_network: 192.168.0.0/24 ceph_docker_registry_auth: true ceph_docker_registry_username: SERVICE_ACCOUNT_USER_NAME ceph_docker_registry_password: TOKEN dashboard_admin_user: DASHBOARD_ADMIN_USERNAME dashboard_admin_password: DASHBOARD_ADMIN_PASSWORD grafana_admin_user: GRAFANA_ADMIN_USER grafana_admin_password: GRAFANA_ADMIN_PASSWORD radosgw_interface: eth0 ceph_docker_image: "rhceph/rhceph-5-rhel8" ceph_docker_image_tag: "latest" ceph_docker_registry: "registry.redhat.io" node_exporter_container_image: registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.6 grafana_container_image: registry.redhat.io/rhceph/rhceph-5-dashboard-rhel8:5 prometheus_container_image: registry.redhat.io/openshift4/ose-prometheus:v4.6 alertmanager_container_image: registry.redhat.io/openshift4/ose-prometheus-alertmanager:v4.6
nb_retry_wait_osd_up: 50 delay_wait_osd_up: 30
fetch_directory: FULL_DIRECTORY_PATH
radosgw_interface: INTERFACE
radosgw_frontend_ssl_certificate: /etc/pki/ca-trust/extracted/ CERTIFICATE_NAME radosgw_frontend_port: 443
upgrade_ceph_packages: True
radosgw_num_instances : NUMBER_OF_INSTANCES_PER_NODE
radosgw_num_instances : 2
radosgw-admin bucket reshard --num-shards 11 --bucket BUCKET_NAME
radosgw-admin bucket reshard --num-shards 11 --bucket mybucket
ansible-playbook -i hosts infrastructure-playbooks/rolling_update.yml --extra-vars "health_osd_check_retries=50 health_osd_check_delay=30"
ansible-playbook -vvvv infrastructure-playbooks/rolling_update.yml -i INVENTORY_FILE
[ceph-admin@admin ceph-ansible]USD ansible-playbook -vvvv infrastructure-playbooks/rolling_update.yml -i hosts
podman ps
exec ceph-mon- MONITOR_ID ceph -s
podman exec ceph-mon-mon01 ceph -s
exec ceph-mon- MONITOR_ID ceph --cluster ceph versions
podman exec ceph-mon-mon01 ceph --cluster ceph versions
ceph_origin: custom/rhcs ceph_custom_repositories: - name: NAME state: present description: DESCRIPTION gpgcheck: 'no' baseurl: BASE_URL file: FILE_NAME priority: '2' enabled: 1
ceph_origin: custom ceph_custom_repositories: - name: ceph_custom state: present description: Ceph custom repo gpgcheck: 'no' baseurl: https://example.ceph.redhat.com file: cephbuild priority: '2' enabled: 1 - name: ceph_custom_1 state: present description: Ceph custom repo 1 gpgcheck: 'no' baseurl: https://example.ceph.redhat.com file: cephbuild_1 priority: '2' enabled: 1
ansible-playbook infrastructure-playbooks/cephadm-adopt.yml -i INVENTORY_FILE
[ceph-admin@admin ceph-ansible]USD ansible-playbook infrastructure-playbooks/cephadm-adopt.yml -i hosts
ceph osd set-require-min-compat-client luminous
ceph osd pool application enable POOL_NAME APPLICATION_NAME
ceph osd pool application enable nfs-ganesha rgw
rbd mirror pool peer add POOL_NAME CLIENT_NAME @ CLUSTER_NAME
rbd --cluster site-a mirror pool peer add image-pool client.rbd-mirror-peer@site-b
cephadm shell
ceph orch ps --daemon_type grafana
ceph orch daemon rm GRAFANA_DAEMON_NAME
ceph orch daemon rm grafana.host01 Removed grafana.host01 from host 'host01'
ceph log last cephadm
dnf remove ansible ceph-ansible
subscription-manager repos --enable=rhel-8-for-x86_64-baseos-rpms --enable=rhel-8-for-x86_64-appstream-rpms --enable=rhceph-5-tools-for-rhel-8-x86_64-rpms --disable=ansible-2.9-for-rhel-8-x86_64-rpms
subscription-manager repos --enable=rhel-9-for-x86_64-baseos-rpms --enable=rhel-9-for-x86_64-appstream-rpms --enable=rhceph-5-tools-for-rhel-9-x86_64-rpms --disable=ansible-2.9-for-rhel-9-x86_64-rpms
dnf install cephadm-ansible