If I continue with the OpenShift Container Storage by creating a Storage Cluster, I have to setup 3 storage nodes.
This is the documentation I follow: https://docs.okd.io/latest/machine_management/creating_machinesets/creating-machineset-aws.html
to create a storage cluster but also with that, I have (new) issues, what I have post here: https://stackoverflow.com/questions/61538606/how-add-extra-blockdevices-to-machineset-in-okd4-4
Every step lead me in new struggles, so I have decided to focus on ROOK now, the opensource version.
Thanks for all your help!
On 2020-04-29 15:38, Nikolas Philips wrote:Hi Ruben,I guess that means, that the CRD ObjectBucket and ObjectBucketClaim are already present (probably through either OCS or NooBaa) - so don't install the lib-bucket-provisioner additionally I guess. FYI: lib-bucket-provisioner ist only a CustomResourceDefinition (CRD, it's like a Schema for Custom Resource Types) - these are always cluster scoped - so it actually doesn't matter in which namespace you install them.What happens when you try to initialize the CustomResources "OCS Initialization" and "Storage Cluster"?Best Regards,Nikolas
Am Mi., 29. Apr. 2020 um 09:49 Uhr schrieb <okd tuxland nl>:
Sure, this is the error:
Operator conflicts existInstalling Operator in selected namespace would cause conflicts with another Operator providing these APIs:
This happens when I try to install lib-bucket-provisioner in the same namespace (openshift-storage) as the Storage Operator ( like the picture in chapter 1.1.1. Installing Red Hat OpenShift Container Storage Operator Hub)
NooBaa Operator is already installed by the Storage Operator:
oc get pods
NAME READY STATUS RESTARTS AGE
noobaa-operator-6c5d6b6656-cjlfm 1/1 Running 0 7m17s
ocs-operator-54f984d56c-2wj8f 1/1 Running 0 7m17s
rook-ceph-operator-586b58dc49-lbnjb 1/1 Running 0 7m17s
On 2020-04-28 20:53, Nikolas Philips wrote:Hi Ruben,When I install lib-bucket-provisioner myself via the OperatorHub (in the same namespace) I get an API conflict.Could you please share the error?I think you need to install the NooBaa Operator too - lib-bucket-provisioner is only a CRD (like a generic API to create S3 buckets and NooBaa is provider)
Just to be sure, this operator works for OKD 4.4 too?I don't know if OCS works for 4.4 - but I'm running Rook Ceph 1.2 on OKD 4.4 - I don't know about NooBaa but I'm pretty sure it should be runnable.do you mean the prerequisites of Rook Ceph?Yes, exactly.Best Regards,Nikolas
Am Di., 28. Apr. 2020 um 16:11 Uhr schrieb <okd tuxland nl>:
The storage operator is installed but lib-bucket-provider not.
According to the documentation: Documentation: Verify that the lib-bucket-provisioner and OpenShift Container Storage Operator show the Status as
I assume it is supposed to be installed with the storage operator. When I install lib-bucket-provisioner myself via the OperatorHub (in the same namespace) I get an API conflict.
Just to be sure, this operator works for OKD 4.4 too?
Question about your comment:This adds the required CatalogSource and Subscription - then the OCS Operator can be selected from the OperatorHub UI. Under the hood, OCS uses Rook Ceph (File/Block Storage) and NooBaa (S3) - you probably should be aware of the corresponding prerequisites (like for Rook Ceph you require separate disks attached to your VMs etc.)Do you mean local storage as described here: https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.3/html/deploying_openshift_container_storage/deploying-openshift-container-storage#installing-openshift-container-storage-using-local-storage-devices_rhocs
or do you mean the prerequisites of Rook Ceph?Thanks for your help!
On 2020-04-27 23:04, Nikolas Philips wrote:Hi Ruben,it looks like as you need to apply the following YAML file:This adds the required CatalogSource and Subscription - then the OCS Operator can be selected from the OperatorHub UI. Under the hood, OCS uses Rook Ceph (File/Block Storage) and NooBaa (S3) - you probably should be aware of the corresponding prerequisites (like for Rook Ceph you require separate disks attached to your VMs etc.)Best Regards,Nikolas
Am Mo., 27. Apr. 2020 um 21:49 Uhr schrieb <okd tuxland nl>:_______________________________________________
Great, anybody else who knows to install this operator? The readme is not very clear.
On 2020-04-27 00:50, James Cassell wrote:On Thu, Apr 23, 2020, at 6:16 AM, okd tuxland nl wrote:Hi All,
I like to install Red Hat OpenShift Container Storage on OKD 4.4.
The documentation of OKD points me to
https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.3/html/deploying_openshift_container_storage/deploying-openshift-container-storage documentation. This page gives instructions to install the *OpenShift Container Storage Operator* however this is not available in the operator hub in OKD. Does anybody know if this is the operator I need: https://github.com/openshift/ocs-operator and how to install?
I believe that is the one. I haven't yet looked how to install it.
users mailing list
users lists openshift redhat com
users mailing list
users lists openshift redhat com