Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem (please be detailed as possible and provide log snippests): --------------------------------------------------------------- With OCS 4.5, we now have support for installing Storage Cluster Service for LSO from UI. https://issues.redhat.com/browse/KNIP-1440: Improved UI and deployment for bare metal Hence we would need to change the Deployment procedure for following section: 1. Deploying OpenShift Container Storage using local storage devices Subsection: Creating OpenShift Container Storage cluster on Amazon EC2 storage optimized - i3en.2xlarge instance type Step : Create StorageCluster CR that uses the localblock StorageClass and the PVs that are created. Current steps is from CLI. We need to change and add screenshot and process based on UI install. P.S: The local volume Creation process is still CLI based, hence we do not need changes in those steps. Version of all relevant components (if applicable): OCS 4.5 Additional info: We also need to confirm if any changes are needed in Managing guide. Need to test if Add capacity also works from UI. We shall raise separate BZs after confirmation
Proposing as a blocker as OCS 4.5 now supports UI installation of Storage Cluster in LSO.
Hi Erin, Thanks for making the changes. I could verify that installation succeeds via Bug 1859516 Few requests for change #1. Please change the e.g. box with following: 2.3. Finding available storage devices -> Step #3. Find the unique by-id device name depending on the hardware serial number for each device. sh-4.4# ls -l /dev/disk/by-id/ | grep Storage lrwxrwxrwx. 1 root root 13 Mar 17 16:24 nvme-Amazon_EC2_NVMe_Instance_Storage_AWS10382E5D7441494EC -> ../../nvme0n1 lrwxrwxrwx. 1 root root 13 Mar 17 16:24 nvme-Amazon_EC2_NVMe_Instance_Storage_AWS60382E5D7441494EC -> ../../nvme1n1 ____________________________________________________________ #2. Please remove this line from 2.3. -> Step #3. >> The lsblk command shows the last two devices, nvme0n1 and nvme1n1 with a size of 1.7 TB each. The command is not lsblk in the e.g. above this statement ____________________________________________________________________ #3 IMO, lets rephrase the entire sentence below Section 2.3-> Step 3 as following. Feel free to rephrase in a better way In this example, the local devices available are nvme0n1 and nvme1n1 with a size of 2.3 TiB Note: All the OpenShift Container Storage worker nodes are of the Amazon EC2 type i3en.2xlarge. So, all the three worker nodes have the same type of machine but the by-id identifier is unique for every local device. For each worker node that has the OpenShift Container Storage label (a minimum of three), you need to find the unique by-id device names. In this example, the by-id device names are: nvme-Amazon_EC2_NVMe_Instance_Storage_AWS10382E5D7441494EC nvme-Amazon_EC2_NVMe_Instance_Storage_AWS60382E5D7441494EC __________________________________________________________________________________ #4. 2.3. Finding available storage devices Step 6 -> please use this CR (the one in the doc needs removal of quotes from limits and re-alignment of "apiversion:xxx" first line apiVersion: ocs.openshift.io/v1 kind: StorageCluster metadata: name: ocs-storagecluster namespace: openshift-storage spec: manageNodes: false resources: mds: limits: cpu: 3 memory: 8Gi requests: cpu: 1 memory: 8Gi monDataDirHostPath: /var/lib/rook storageDeviceSets: - count: 2 dataPVCTemplate: spec: accessModes: - ReadWriteOnce resources: requests: storage: 2328Gi storageClassName: localblock volumeMode: Block name: ocs-deviceset placement: {} portable: false replica: 3 resources: limits: cpu: 2 memory: 5Gi requests: cpu: 1 memory: 5Gi Please let me know if there are any confusions.. We can discuss over gmeet or chat.
Thank you Erin for the changes. My bad, I missed some more changes regarding the Device sizes. Request you to make these as well. 2.4. Creating OpenShift Container Storage cluster on Amazon EC2 storage optimized - i3en.2xlarge instance type Step 4. Check if the PVs are created >> Please replace "size 1.7 TB" with " size of 2.3 TiB" -------------------------------- 2.3. Finding available storage devices Step 2: Please change the size of the devices from 1.7T to 2.3T in the example box nvme0n1 259:0 0 2.3T 0 disk nvme1n1 259:1 0 2.3T 0 disk --------------------------------------------- 2.3. Finding available storage devices Step 3. Find the unique by-id device name depending on the hardware serial number for each device >> Please remove the extra line after "sh-4.4# ls -l /dev/disk/by-id/ | grep Storage" in the example box
*** Bug 1859520 has been marked as a duplicate of this bug. ***