Fedora Account System
Red Hat Associate
Red Hat Customer
Better to use 512 GiB, 2 TiB or 4 TiB as example. and this should be in sync with other steps in the chapter. 1) in the chapter 1.2.5, as per step 1 and 3, 3 disks are being passed but in the step 8 we have displayed 6 PV 2) In the chapter 1.2.4, in step 8 example output, PV shown is of 100GB but in step 9 we are creating device set of 2TiB storageDeviceSets . storage: 2Ti . Reported by: rhn-support-bkunal https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.3/html/deploying_openshift_container_storage/deploying-openshift-container-storage#annotations:c5000d69-af05-423c-a1e2-59e60ca0fbe9
Based on COmment #5 and below snip copied from Deployment Guide One more change needed in Section 2.5 Step 6, as example block shows size as 100Gi >> Section 2.5 - [1] [1] - https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.4/html-single/deploying_openshift_container_storage/index?lb_target=preview#creating-openshift-container-storage-cluster-on-vmware_aws-vmware >> Step 6. Create StorageCluster CR ocs-cluster-service-VMware.yaml that uses the monDataDirHostPath and localblock StorageClass. kind: StorageCluster requests: >> storage: 100Gi <--change it to 2Ti ______________________________________________________________________________ >> Step 5: Check the PVs that are created with the Available status. Confirmed that changes in Step 5 of Section 2.5 is as per the ask """"" Example output: NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE local-pv-150fdc87 2TiB RWO Delete Available localblock 2m11s local-pv-183bfc0a 2TiB RWO Delete Available localblock 2m11s local-pv-b2f5cb25 2TiB RWO Delete Available localblock 2m21s In this example, three PVs are used for OSD storage. """""""""""""
Raised BZ https://bugzilla.redhat.com/show_bug.cgi?id=1854088 for addressing Comment#7