BZ's/RFEs - Needs to be added in the respective guides as NOTE/important Below are the RFE's needs to be added in the guides not in the release notes Bug 1949961 - [RFE] [cephadm] 5.0 - Ceph orch upgrade status do not display a "upgrade success" message in the status command when upgrade is completed without any issues - Under Upgrade section in Installation guide Bug 1910114 - [RFE] [cephadm] Host status is blank in "ceph orch host ls" - Low - Installation guide 1939633 - RFE - 5.0 Cephadm - Need support for cephadm daemon logs redirection to non default files other than fixed files and also to a non default directory or to an external path ---Needs to be documented in admin guide Bug 1926629 - [RFE] Configure the IP address for the monitoring stack components - High When the dashboard is deployed using cephadm, a monitoring stack (node_exporter, prometheus, alertmanager, grafana) can be applied to the cluster, resulting in multiple components deployed according the provided spec definition. However, even though we're able to push a specific json config through cephadm, we need to be able to specify the ip address on the network the component belongs to, or the daemon will bind on *::<port>, which is a problem from a security point of view, preventing them to be deployed in the OpenStack context (both in standalone and HA config). The Ceph Dashboard component already provides (via the mgr) a way to support multiple instances on different ip addresses [1], but this is not true for the other monitoring stack components. This represents a gap compared to ceph-ansible [2][3][4]. Bug 1939354 - RFE - osd_memory_target per node always set to default - it should be based on RAM and OSD Bug 1944769 - RFE: Provision to apply custom images for monitoring services during bootstrap
@Anjana, Since these are not supported in 5.0, we would like to document this as NOTE/important. Once feature is ready, we can document the steps required to enable them.
I have verified looks good. Hence, moving to Verified state