Created attachment 1669940 [details] OCP console options Description of problem (please be detailed as possible and provide log snippests): There are 2 ways how to create backing store via UI: * In OCP go to Operators -> Installed Operators, click on OpenShift Container Storage, go to Backing Store tab and click on Create Backing Store. * In MCG console go to Resources and click on Add Cloud Resource. In MCG console user needs to first select or create a connection that is used by backing store. In OCP console user creates backing store directly. Type of backing store can be specified in MCG as a connection service (there are available AWS S3, Azure Blob, Google Cloud, S3 V2 Compatible service, S3 V4 Compatible Service, Pure FlashBlade service, IBM COS service). In OCP user can specify type of backing store as Provider (there are available AWS S3, Azure Blob, Google cloud storage, S3 Compatible, PVC). Version of all relevant components (if applicable): OCP: 4.3.0-0.nightly-2020-03-12-085147 OCS: 4.3-30.07d83470.ocs_4.3 Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? yes Can this issue reproduce from the UI? yes Steps to Reproduce: 1. Check available types of backing store in backing store create process as described in Description of problem section of this bz. Actual results: There are different options to create a backing store, e.g. PVC based backing store can be created only via OCP console. This can confuse users. Expected results: It should be possible to create the same backing stores via MCG and OCP. Additional info:
Created attachment 1669941 [details] MCG console options
@filip why is that an issue? The NooBaa UI provides more features and more granularity.
It is confusing for users. I found about this when I needed to create PVC based backing store on VMWare without using AWS but I couldn't find the option in MCG console. I found it in OCP. Maybe this can be solved by marking Backing store tab in OCS Operator accessed from OCP as Internal and add missing options to MCG console. Although, I am not sure if backing stores from these two sources are the same and if they are handled by OCP the same way and if user would lose some functionality.
They are the same. Since you used the NooBaa UI, I'm sure you saw many more capabilities (for example on buckets) which are currently not externalized. It was decided that these options would be considered "advanced" (at least for now until we see customers who actually need them) and as such will only be avail via the UI. We won't open an issue for each right? If you think there is a capability that should be externalized, I suggest opening an RFE on that and have the PM answer on it.
See my comment above, they are the same with higher resolution in the noobaa UI (connection can be re-used for several resources). This was the UX decision for providing the OCP config and the 2nd the UX for the NooBaa Ui, They were not the same nor should they be.
I am ok with MCG console to have more options for Backing stores than OCP console. In the time of creation of this BZ I was confused because of PVC based backing store available from OCP console but not being part of MCG console.
Got you :) So I'm closing this one