IBM / cloud-pak-deployer

Configuration-based installation of OpenShift and Cloud Pak for Data/Integration/Watson AIOps on various private and public cloud infrastructure providers. Deployment attempts to achieve the end-state defined in the configuration. If something fails along the way, you only need to restart the process to continue the deployment.
https://ibm.github.io/cloud-pak-deployer/
Apache License 2.0
139 stars 68 forks source link

Should use storageclass ocs-storagecluster-ceph-rbd instead of ocs-storagecluster-cephfs when creating Watson Query Instance #353

Closed joergre8 closed 1 year ago

joergre8 commented 1 year ago

we have deployed DV instance through deployer. Seems it has used cephfs as storageclass Our docs recommend rbd though Would you mind checking please? Or can we override the default and specify we would like to use different class? OpenShift Data Foundation On OpenShift Data Foundation, Watson Query uses block storage. Block storage: ocs-storagecluster-ceph-rbd https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=requirements-storage

fketelaars commented 1 year ago

Hi @joergre8 I checked the code and the default is indeed to use file (rwx) storage class for everything. Can you revert which storages require block storage?

{
   "addon_type":"{{ cp4d_dv_addon_type }}",
   "display_name":"{{ _dv_instance.name }}",
   "namespace":"{{ current_cp4d_cluster.project }}",
   "addon_version":"{{ _dv_version.stdout }}",
   "create_arguments":{
      "parameters":{
         "resources.dv.requests.cpu": "{{ cp4d_dv_instance_requests_cpu }}",
         "resources.dv.requests.memory": "{{ cp4d_dv_instance_requests_memory }}",
         "image.pullPolicy": "{{ cp4d_dv_instance_pull_policy }}",
         "workerCount": "{{ cp4d_dv_instance_compute_count }}",
         "enableHostIPC": "{{ cp4d_dv_instance_enable_host_ipc }}",
{% if _storage_type == 'pwx' %}
         "persistence.storageClass": "portworx-db2-rwx-sc",
         "persistence.workerpv.storageClass": "portworx-db2-rwx-sc",
         "persistence.cachingpv.storageClass": "portworx-db2-rwx-sc",
{% else %}
         "persistence.storageClass": "{{ ocp_storage_class_file }}",
         "persistence.workerpv.storageClass": "{{ ocp_storage_class_file }}",
         "persistence.cachingpv.storageClass": "{{ ocp_storage_class_file }}",
{% endif %}
         "persistence.size": "{{ cp4d_dv_instance_persistence_storage_size }}",
         "persistence.workerpv.size": "{{ cp4d_dv_instance_persistence_compute_storage_size }}",
         "persistence.cachingpv.size": "{{ cp4d_dv_instance_persistence_caching_storage_size }}"
      },
      "resources":{
         "cpu":"{{ cp4d_dv_instance_requests_cpu }}",
         "memory":"{{ cp4d_dv_instance_requests_memory }}"
      },
      "description":"Data Virtualization",
      "metaData":{

      }
   },
   "transientFields":{

   }
}
joergre8 commented 1 year ago

@fketelaars if ODF is used all storageclasses for all pvcs should point to ocs-storagecluster-ceph-rbd being it for dvcaching as well as the workers screenshot attached of pvc console after manual correct setup grafik

fketelaars commented 1 year ago

@joergre8 Understood and documented here: https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=requirements-storage

We will make the following changes:

fketelaars commented 1 year ago

Fixed