Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
We need to rename this bug "The console UI displays incoherent OSD journal size" to "The console UI displays incoherent OSD journal size in some cases" and the HTML text below it does not display properly in Chrome until I click on it (it showed blank at first).
Here's my comments: (1) Where do we list limitations, i.e. no support for RGW during installation, import, monitoring, etc.? Same for CephFS. (2) In the "Red Hat Storage Console supports the installation of Red Hat Ceph Storage 2.0 in a completely graphical manner, as well as the import of existing (or upgraded) Ceph 2.0 clusters. Other important features include:” paragraph, it would be worth adding some core competencies that RHSC2 offers that no other product does, i.e.: automatic expansion of a cluster whenever disks or nodes are added to a cluster managed by RHSC2 automatic placement group (PG) optimization in provisioning operations (3) "...the console supports importing clusters which have been set up with journals and OSDs colocated on the same physical disk. This mode is supported by the ceph-ansible project but not by Red Hat Storage Console 2.0.” My interpretation of this is that we are trying to say we don’t support journals and OSD’s collocated on the same physical disk but we will let you import it, though it may not report inaccurate journal size information in such scenarios and it may also lead to unexpected behavior during active management, e.g. future expansion as once the cluster is managed by RHSC2, any time disks or nodes are added to the cluster, it will be partitioned differently from how it was originally intended — which is probably unexpected and unintended behavior by the user with potentially “surprising" consequences. Can we expand to it causing some unexpected and unintended behavior and also perhaps maybe some text to say it's a discouraged action as well since it's unsupported? (4) "providerName": "ldapauthprovider" (BZ#1350977) — should not be bolded (as it appears we list the issue in bold text and details including resolution/workaround in plain text) (5) "Red Hat Storage Console 2.0 unable to configure multiple networks during cluster creation Let’s use the same terms used in the UI, i.e. cluster network and public network (vs. access network), or at the very least mention that the public network is also another term for access network.
Re #3 above, whenever new disks or new nodes are added to the cluster, RHSC2 would want be able to have a colocated scenarios (OSD and journal on the same disk anymore), so this may be an undesirable consequence that may differ from user's expectations in addition to inaccurate capacity reporting, etc.
Just a couple notes on 2 of the following bullets: => Automatic cluster expansion when new storage disks are added to the hosts of a cluster. => Automatic Placement Group (PG) optimization in provisioning operations. You'll want to remove the period (.) at the end of each bullet. The "Automatic cluster expansion when new storage disks are added to the hosts of a cluster" statement might be better worded as "Automatic cluster expansion occurs when new storage disks are added or when a new host is added to an existing cluster"
Just reviewed the latest updated release notes at https://access.qa.redhat.com/documentation/en/red-hat-storage-console/2.0/single/release-notes, and they look good to go.
Yes the notes look great as Ju said. Let's ship it!