Describe the issue: ------------------------ We have recently added a Verification step for encrypted devices(optional) Replacing Node and Replacing devices in OCS 4.6 docs We need the same content to to also added in Verification steps of Scaling Capacity book [1] Content ============ Add a new step in relevant places of >>Verification steps For reference - refer [4] Verification Steps-> Step 5 ____________________________________________________________________________________________________________ (Optional) If data encryption is enabled on the cluster, verify that the new OSD devices are encrypted. Create a debug pod and open a chroot environment for the host. $ oc debug node new-node-name $ chroot /host Verify the devices are encrypted. $ dmsetup ls | grep ocs-deviceset ocs-deviceset-0-data-0-57snx-block-dmcrypt (253:1) $ lsblk | grep ocs-deviceset `-ocs-deviceset-0-data-0-57snx-block-dmcrypt 253:1 0 512G 0 crypt _______________________________________________________________________________________________________________ Applicable sections --------------------------- Link [2] 2. Scaling up storage capacity 2.1. Creating a Storage Class 2.2. Scaling up storage by adding capacity to your OpenShift Container Storage nodes on AWS or VMware infrastructure 2.3. Scaling up storage by adding capacity to your OpenShift Container Storage nodes using local storage devices Link [3] 3. Scaling out storage capacity 3.2. Verifying the addition of a new node Document URL: ----------------- [1] - https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.6/html-single/scaling_storage/index?lb_target=preview [2] - https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.6/html-single/scaling_storage/index?lb_target=preview#scaling-up-storage-capacity_rhocs [3] - https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.6/html-single/scaling_storage/index?lb_target=preview#verifying-the-addition-of-a-new-node_rhocs [4] - https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.6/html-single/replacing_nodes/index?lb_target=stage#replacing-a-failed-vmware-node-upi_rhocs
After giving it some thought, I feel we do not need to add the suggested Note in "3.2. Verifying the addition of a new node" Reason: Add node does not mean add OSDs.. for adding OSDs after adding Nodes, we have a Note in 3.3. Scaling up storage capacity , re-directing to Section 2. Section 2 will already have the New Note/step. >> 3.2. Verifying the addition of a new node --< Do not add suggested Step for encrypted device check from Comment#0
Slight change in the Step to be added to Add capacity section . We need to replace <new-node-name> to <node-name> 2.2. Scaling up storage by adding capacity to your OpenShift Container Storage nodes on AWS or VMware infrastructure 2.3. Scaling up storage by adding capacity to your OpenShift Container Storage nodes using local storage devices _________________________________________________________________________________________________________________________________ (Optional) If data encryption is enabled on the cluster, verify that the new OSD devices are encrypted. Create a debug pod and open a chroot environment for the host. $ oc debug node <node-name> $ chroot /host Verify the devices are encrypted. $ dmsetup ls | grep ocs-deviceset ocs-deviceset-0-data-0-57snx-block-dmcrypt (253:1) $ lsblk | grep ocs-deviceset `-ocs-deviceset-0-data-0-57snx-block-dmcrypt 253:1 0 512G 0 crypt
OCS 4.6.0 GA completed on 17 December 2020