diff --git a/next/basic-concepts/basic-concepts.html b/next/basic-concepts/basic-concepts.html
index d2abc045..0c166085 100644
--- a/next/basic-concepts/basic-concepts.html
+++ b/next/basic-concepts/basic-concepts.html
@@ -74,7 +74,7 @@
Meta
The meta module within each IOMesh Block Storage component for metadata management, including storage object management, data replica management, access control, and ensuring data consistency. A meta pod on a worker node provides metadata management, and each worker node can only have one meta pod.
IOMesh CSI Driver
-The self-developed CSI driver that adheres to the CSI standard and utilizes RPC (Remote Procedure Call) to manage persistent volumes, delivering reliable and consistent storage for data applications on Kubernetes. Each Kubernetes persistent volume corresponds to an iSCSI LUN in the IOMesh cluster.
+The CSI driver that adheres to the CSI standard and utilizes RPC (Remote Procedure Call) to manage persistent volumes, delivering reliable and consistent storage for data applications on Kubernetes. Each Kubernetes persistent volume corresponds to an iSCSI LUN in the IOMesh cluster.
IOMesh Operator
The IOMesh automated operations and maintenance component, allowing for roll updating IOMesh, scaling out or down nodes, and GitOps while being responsible for automatic discovery, allocation, and management of block devices.
Namespace
diff --git a/next/basic-concepts/basic-concepts/index.html b/next/basic-concepts/basic-concepts/index.html
index d2abc045..0c166085 100644
--- a/next/basic-concepts/basic-concepts/index.html
+++ b/next/basic-concepts/basic-concepts/index.html
@@ -74,7 +74,7 @@
Meta
The meta module within each IOMesh Block Storage component for metadata management, including storage object management, data replica management, access control, and ensuring data consistency. A meta pod on a worker node provides metadata management, and each worker node can only have one meta pod.
IOMesh CSI Driver
-The self-developed CSI driver that adheres to the CSI standard and utilizes RPC (Remote Procedure Call) to manage persistent volumes, delivering reliable and consistent storage for data applications on Kubernetes. Each Kubernetes persistent volume corresponds to an iSCSI LUN in the IOMesh cluster.
+The CSI driver that adheres to the CSI standard and utilizes RPC (Remote Procedure Call) to manage persistent volumes, delivering reliable and consistent storage for data applications on Kubernetes. Each Kubernetes persistent volume corresponds to an iSCSI LUN in the IOMesh cluster.
IOMesh Operator
The IOMesh automated operations and maintenance component, allowing for roll updating IOMesh, scaling out or down nodes, and GitOps while being responsible for automatic discovery, allocation, and management of block devices.
Namespace
diff --git a/next/cluster-operations/replace-failed-disk.html b/next/cluster-operations/replace-failed-disk.html
index 59ff1a3a..685727e9 100644
--- a/next/cluster-operations/replace-failed-disk.html
+++ b/next/cluster-operations/replace-failed-disk.html
@@ -1,4 +1,4 @@
-Replace Disk · Documentation VolumeSnapshot Operations Deploy Stateful Applications VolumeSnapshot Operations Deploy Stateful Applications You can see the health status of physical disks on the IOMesh Dashboard. If any disk is in Unhealthy, Failing, or S.M.A.R.T not passed state, you need to replace it with a new disk as soon as possible.
+ The IOMesh Dashboard displays the health status of physical disks for easy monitoring. If any disk is indicated as Unhealthy, Failing, or S.M.A.R.T not passed, you should replace it with a new disk as soon as possible.
Procedure
Get the meta leader pod name.
@@ -66,7 +66,7 @@
kubectl exec -it iomesh-meta-0 -n iomesh-system -c iomesh-meta bash
Run the following command multiple times to verify that there are no ongoing migration or recovery tasks in the cluster.
-Ensure that the output value is 0. If there is a field that is not 0, you need to wait for it to become 0.
+Ensure that the output value is 0. If any field has a non-zero value, you should wait for it to reach 0.
/opt/iomesh/iomeshctl summary cluster | egrep "recovers|migrates"
num_ongoing_recovers: 0
@@ -88,7 +88,7 @@
pending_migrates_bytes: 0
pending_recovers_bytes: 0
View the disk that needs to be replaced. Assume the disk blockdevice-66312cce9037ae891a099ad83f44d7c9 needs to be replaced.
+View the disk that requires replacement. In the given example, let's assume that the disk blockdevice-66312cce9037ae891a099ad83f44d7c9 needs to be replaced.
kubectl --namespace iomesh-system get bd -o wide
NAME NODENAME PATH FSTYPE SIZE CLAIMSTATE STATUS AGE
@@ -115,14 +115,14 @@
- blockdevice-66312cce9037ae891a099ad83f44d7c9
Repeat Step 2 and 3 to verify that there are no ongoing migration or recovery tasks for the cluster.
Verify that the block device is in Unclaimed state.
+Repeat Step 2 and 3 to verify that there are no ongoing migration or recovery tasks in the cluster.
Verify that the block device is in the Unclaimed state.
kubectl get bd blockdevice-66312cce9037ae891a099ad83f44d7c9 -n iomesh-system
NAME NODENAME PATH FSTYPE SIZE CLAIMSTATE STATUS AGE
blockdevice-66312 cce9037ae891a099ad83f44d7c9 qtest-k8s-1 /dev/sdc 69793218560 Unclaimed Active 44 h
Unplug the disk. Then the disk will enter Inactive state.
+Unplug the disk. Then the disk will enter the Inactive state.
Run the following commands simultaneously to remove the block device and its corresponding blockdeviceclaim.
NOTE: It is normal to see a prompt indicating that bdc cannot be found when running the following commands to clear it.
@@ -132,6 +132,6 @@
kubectl delete bdc blockdevice-66312cce9037ae891a099ad83f44d7c9 -n iomesh-system
kubectl delete bd blockdevice-66312cce9037ae891a099ad83f44d7c9 -n iomesh-system
Plug the new disk. Refer to Set Up IOMesh to mount it to the IOMesh cluster.
Plug the new disk. Refer to Set Up IOMesh for mounting steps.
\ No newline at end of file
diff --git a/next/cluster-operations/replace-failed-disk/index.html b/next/cluster-operations/replace-failed-disk/index.html
index 59ff1a3a..685727e9 100644
--- a/next/cluster-operations/replace-failed-disk/index.html
+++ b/next/cluster-operations/replace-failed-disk/index.html
@@ -1,4 +1,4 @@
-
Replace Disk · Documentation VolumeSnapshot Operations Deploy Stateful Applications VolumeSnapshot Operations Deploy Stateful Applications You can see the health status of physical disks on the IOMesh Dashboard. If any disk is in Unhealthy, Failing, or S.M.A.R.T not passed state, you need to replace it with a new disk as soon as possible.
+ The IOMesh Dashboard displays the health status of physical disks for easy monitoring. If any disk is indicated as Unhealthy, Failing, or S.M.A.R.T not passed, you should replace it with a new disk as soon as possible.
Procedure
Get the meta leader pod name.
@@ -66,7 +66,7 @@
kubectl exec -it iomesh-meta-0 -n iomesh-system -c iomesh-meta bash
Run the following command multiple times to verify that there are no ongoing migration or recovery tasks in the cluster.
-Ensure that the output value is 0. If there is a field that is not 0, you need to wait for it to become 0.
+Ensure that the output value is 0. If any field has a non-zero value, you should wait for it to reach 0.
/opt/iomesh/iomeshctl summary cluster | egrep "recovers|migrates"
num_ongoing_recovers: 0
@@ -88,7 +88,7 @@
pending_migrates_bytes: 0
pending_recovers_bytes: 0
View the disk that needs to be replaced. Assume the disk blockdevice-66312cce9037ae891a099ad83f44d7c9 needs to be replaced.
+View the disk that requires replacement. In the given example, let's assume that the disk blockdevice-66312cce9037ae891a099ad83f44d7c9 needs to be replaced.
kubectl --namespace iomesh-system get bd -o wide
NAME NODENAME PATH FSTYPE SIZE CLAIMSTATE STATUS AGE
@@ -115,14 +115,14 @@
- blockdevice-66312cce9037ae891a099ad83f44d7c9
Repeat Step 2 and 3 to verify that there are no ongoing migration or recovery tasks for the cluster.
Verify that the block device is in Unclaimed state.
+Repeat Step 2 and 3 to verify that there are no ongoing migration or recovery tasks in the cluster.
Verify that the block device is in the Unclaimed state.
kubectl get bd blockdevice-66312cce9037ae891a099ad83f44d7c9 -n iomesh-system
NAME NODENAME PATH FSTYPE SIZE CLAIMSTATE STATUS AGE
blockdevice-66312 cce9037ae891a099ad83f44d7c9 qtest-k8s-1 /dev/sdc 69793218560 Unclaimed Active 44 h
Unplug the disk. Then the disk will enter Inactive state.
+Unplug the disk. Then the disk will enter the Inactive state.
Run the following commands simultaneously to remove the block device and its corresponding blockdeviceclaim.
NOTE: It is normal to see a prompt indicating that bdc cannot be found when running the following commands to clear it.
@@ -132,6 +132,6 @@
kubectl delete bdc blockdevice-66312cce9037ae891a099ad83f44d7c9 -n iomesh-system
kubectl delete bd blockdevice-66312cce9037ae891a099ad83f44d7c9 -n iomesh-system
Plug the new disk. Refer to Set Up IOMesh to mount it to the IOMesh cluster.
Plug the new disk. Refer to Set Up IOMesh for mounting steps.
\ No newline at end of file
diff --git a/next/cluster-operations/scale-out-cluster.html b/next/cluster-operations/scale-out-cluster.html
index b7b42d43..70c161b3 100644
--- a/next/cluster-operations/scale-out-cluster.html
+++ b/next/cluster-operations/scale-out-cluster.html
@@ -1,4 +1,4 @@
-
Scale Out Cluster · Documentation VolumeSnapshot Operations Deploy Stateful Applications VolumeSnapshot Operations Deploy Stateful Applications If you have the Enterprise Edition of IOMesh software, you can scale it out online without disrupting the cluster's operation. However, scaling out is not possible with the Community Edition, which limits the number of meta or chunk pods to three. During scaling out, you can choose to add chunk pods, meta pods, or both simultaneously.
+ If you have the IOMesh Enterprise edition, you can scale out the cluster online without interrupting its operation. However, scaling out is not possible with the Community edition that only allows a maximum of three meta or chunk pods. When scaling out the cluster, you can choose to add chunk pods, meta pods, or both at the same time.
Prerequisite
Ensure an adequate number of worker nodes in the Kubernetes cluster. Each worker node can accommodate only one chunk pod and one meta pod. Therefore, if there are insufficient worker nodes, add them to the Kubernetes cluster before scaling out.
Procedure
@@ -65,7 +65,7 @@
To increase the capacity of the IOMesh cluster, you can choose to add chunk pods by following these steps:
-Find chunk in iomesh.yaml, the default configuration file exported during IOMesh installation, and then edit replicaCount. The value of replicaCount is the total number of chunk pods after scaling out.
+Locate chunk in iomesh.yaml, the default configuration file exported during IOMesh installation. Then modify the value of replicaCount, which represents the total number of chunk pods.
chunk:
replicaCount: 5
Add meta pods.
An optional step. When deploying IOMesh, three meta pods are created in the IOMesh cluster by default. If the number of IOMesh nodes in the Kubernetes cluster is equal to or greater than five, it's recommended to increase the number of meta pods from three to five. Note that the number of supported meta pods in the IOMesh cluster should be either three or five.
-Find meta in iomesh.yaml, the default configuration file exported during IOMesh installation, and then edit replicaCount.
+Locate meta in iomesh.yaml, the default configuration file exported during IOMesh installation. Then modify the value of replicaCount, which represents the number of meta pods.
meta:
replicaCount: 5
Scale Out Cluster · Documentation VolumeSnapshot Operations Deploy Stateful Applications VolumeSnapshot Operations Deploy Stateful Applications If you have the Enterprise Edition of IOMesh software, you can scale it out online without disrupting the cluster's operation. However, scaling out is not possible with the Community Edition, which limits the number of meta or chunk pods to three. During scaling out, you can choose to add chunk pods, meta pods, or both simultaneously.
+ If you have the IOMesh Enterprise edition, you can scale out the cluster online without interrupting its operation. However, scaling out is not possible with the Community edition that only allows a maximum of three meta or chunk pods. When scaling out the cluster, you can choose to add chunk pods, meta pods, or both at the same time.
Prerequisite
Ensure an adequate number of worker nodes in the Kubernetes cluster. Each worker node can accommodate only one chunk pod and one meta pod. Therefore, if there are insufficient worker nodes, add them to the Kubernetes cluster before scaling out.
Procedure
@@ -65,7 +65,7 @@
To increase the capacity of the IOMesh cluster, you can choose to add chunk pods by following these steps:
-Find chunk in iomesh.yaml, the default configuration file exported during IOMesh installation, and then edit replicaCount. The value of replicaCount is the total number of chunk pods after scaling out.
+Locate chunk in iomesh.yaml, the default configuration file exported during IOMesh installation. Then modify the value of replicaCount, which represents the total number of chunk pods.
chunk:
replicaCount: 5
Add meta pods.
An optional step. When deploying IOMesh, three meta pods are created in the IOMesh cluster by default. If the number of IOMesh nodes in the Kubernetes cluster is equal to or greater than five, it's recommended to increase the number of meta pods from three to five. Note that the number of supported meta pods in the IOMesh cluster should be either three or five.
-Find meta in iomesh.yaml, the default configuration file exported during IOMesh installation, and then edit replicaCount.
+Locate meta in iomesh.yaml, the default configuration file exported during IOMesh installation. Then modify the value of replicaCount, which represents the number of meta pods.
meta:
replicaCount: 5
Install IOMesh · Documentation VolumeSnapshot Operations Deploy Stateful Applications VolumeSnapshot Operations Deploy Stateful Applications IOMesh can be installed on all Kubernetes platforms using various methods. Choose the installation method based on your environment. If the Kubernetes cluster network cannot connect to the public network, you can opt for custom offline installation.
+ IOMesh can be installed on all Kubernetes platforms using various methods. Choose the installation method based on your environment. If the Kubernetes cluster network cannot connect to the public network, opt for custom offline installation.
-One-click online installation: Use the default settings in the file without customizing parameters.
+One-click online installation: Use the default settings in the file without custom parameters.
Custom online installation: Supports custom parameters.
Custom offline installation: Supports custom parameters.
@@ -87,10 +87,10 @@ NOTE: IOMesh resources left by running the above commands will be saved for troubleshooting if any error occurs during installation. You can run the command curl -sSL https://iomesh.run/uninstall_iomesh.sh | sh - to remove all IOMesh resources from the Kubernetes cluster.
-NOTE: After installing IOMesh, the prepare-csi Pod will automatically start on all schedulable nodes in the Kubernetes cluster to install and configure open-iscsi. If the installation of open-iscsi is successful on all nodes, the system will automatically clean up the prepare-csi Pod. However, if the installation of open-iscsi fails on any node, manual configuration of open-iscsi is required to determine the cause of the installation failure.
+NOTE: After installing IOMesh, the prepare-csi pod will automatically start on all schedulable nodes in the Kubernetes cluster to install and configure open-iscsi. If the installation of open-iscsi is successful on all nodes, the system will automatically clean up all prepare-csi pods. However, if the installation of open-iscsi fails on any node, manual configuration of open-iscsi is required to determine the cause of the installation failure.
-NOTE: If open-iscsi is manually deleted after installing IOMesh, the prepare-csi Pod will not automatically start to install open-iscsi when reinstalling IOMesh. In this case, manual configuration of open-iscsi is necessary.
+NOTE: If open-iscsi is manually deleted after installing IOMesh, the prepare-csi pod will not automatically start to install open-iscsi when reinstalling IOMesh. In this case, manual configuration of open-iscsi is necessary.
dataCIDR: ""
-
Set diskDeploymentMode according to your disk configurations . The system defaults to hybridFlash.
+Set diskDeploymentMode according to your disk configurations . The system has a default value of hybridFlash. If your disk configuration is all-flash mode, change the value to allFlash.
diskDeploymentMode: "hybridFlash"
Specify the CPU architecture. If you have a hygon_x86_64 Kubernetes cluster, enter hygon_x86_64, or else leave the field blank.
@@ -128,7 +128,7 @@
-
An optional step. The number of IOMesh chunk pods is three by default. If you install IOMesh Enterprise Edition, you can deploy more than three chunk pods。
+An optional step. The number of IOMesh chunk pods is three by default. If you install IOMesh Enterprise Edition, you can deploy more than three chunk pods.
iomesh:
chunk:
replicaCount: 3
@@ -150,7 +150,7 @@ It is recommended that you only configure values. For more configurations, refer to Pod Affinity .
An optional step. Configure the podDeletePolicy field to determine whether the system should automatically delete the Pod and rebuild it on another healthy node when the Kubernetes node that hosts the Pod fails. This configuration applies only to the Pod with an IOMesh-created PVC mounted and the access mode set to ReadWriteOnly.
-If left unspecified, this field is set to no-delete-pod by default, indicating that the system won't automatically delete and rebuild the Pod in case of node failure.
+If left unspecified, the value of this field will be set to no-delete-pod by default, indicating that the system won't automatically delete and rebuild the Pod in case of node failure.
csi-driver:
driver:
controller:
@@ -220,10 +220,10 @@
-NOTE: After installing IOMesh, the prepare-csi Pod will automatically start on all schedulable nodes in the Kubernetes cluster to install and configure open-iscsi. If the installation of open-iscsi is successful on all nodes, the system will automatically clean up the prepare-csi Pod. However, if the installation of open-iscsi fails on any node, manual configuration of open-iscsi is required to determine the cause of the installation failure.
+NOTE: After installing IOMesh, the prepare-csi pod will automatically start on all schedulable nodes in the Kubernetes cluster to install and configure open-iscsi. If the installation of open-iscsi is successful on all nodes, the system will automatically clean up all prepare-csi pods. However, if the installation of open-iscsi fails on any node, manual configuration of open-iscsi is required to determine the cause of the installation failure.
-NOTE: If open-iscsi is manually deleted after installing IOMesh, the prepare-csi Pod will not automatically start to install open-iscsi when reinstalling IOMesh. In this case, manual configuration of open-iscsi is necessary.
+NOTE: If open-iscsi is manually deleted after installing IOMesh, the prepare-csi pod will not automatically start to install open-iscsi when reinstalling IOMesh. In this case, manual configuration of open-iscsi is necessary.
@@ -254,7 +254,7 @@
\ No newline at end of file
diff --git a/next/deploy-iomesh-cluster/install-iomesh/index.html b/next/deploy-iomesh-cluster/install-iomesh/index.html
index 90e2aac7..774a3bec 100644
--- a/next/deploy-iomesh-cluster/install-iomesh/index.html
+++ b/next/deploy-iomesh-cluster/install-iomesh/index.html
@@ -1,4 +1,4 @@
-
Install IOMesh · Documentation VolumeSnapshot Operations Deploy Stateful Applications VolumeSnapshot Operations Deploy Stateful Applications IOMesh can be installed on all Kubernetes platforms using various methods. Choose the installation method based on your environment. If the Kubernetes cluster network cannot connect to the public network, you can opt for custom offline installation.
+ IOMesh can be installed on all Kubernetes platforms using various methods. Choose the installation method based on your environment. If the Kubernetes cluster network cannot connect to the public network, opt for custom offline installation.
-One-click online installation: Use the default settings in the file without customizing parameters.
+One-click online installation: Use the default settings in the file without custom parameters.
Custom online installation: Supports custom parameters.
Custom offline installation: Supports custom parameters.
@@ -87,10 +87,10 @@ NOTE: IOMesh resources left by running the above commands will be saved for troubleshooting if any error occurs during installation. You can run the command curl -sSL https://iomesh.run/uninstall_iomesh.sh | sh - to remove all IOMesh resources from the Kubernetes cluster.
-NOTE: After installing IOMesh, the prepare-csi Pod will automatically start on all schedulable nodes in the Kubernetes cluster to install and configure open-iscsi. If the installation of open-iscsi is successful on all nodes, the system will automatically clean up the prepare-csi Pod. However, if the installation of open-iscsi fails on any node, manual configuration of open-iscsi is required to determine the cause of the installation failure.
+NOTE: After installing IOMesh, the prepare-csi pod will automatically start on all schedulable nodes in the Kubernetes cluster to install and configure open-iscsi. If the installation of open-iscsi is successful on all nodes, the system will automatically clean up all prepare-csi pods. However, if the installation of open-iscsi fails on any node, manual configuration of open-iscsi is required to determine the cause of the installation failure.
-NOTE: If open-iscsi is manually deleted after installing IOMesh, the prepare-csi Pod will not automatically start to install open-iscsi when reinstalling IOMesh. In this case, manual configuration of open-iscsi is necessary.
+NOTE: If open-iscsi is manually deleted after installing IOMesh, the prepare-csi pod will not automatically start to install open-iscsi when reinstalling IOMesh. In this case, manual configuration of open-iscsi is necessary.
dataCIDR: ""
-
Set diskDeploymentMode according to your disk configurations . The system defaults to hybridFlash.
+Set diskDeploymentMode according to your disk configurations . The system has a default value of hybridFlash. If your disk configuration is all-flash mode, change the value to allFlash.
diskDeploymentMode: "hybridFlash"
Specify the CPU architecture. If you have a hygon_x86_64 Kubernetes cluster, enter hygon_x86_64, or else leave the field blank.
@@ -128,7 +128,7 @@
-
An optional step. The number of IOMesh chunk pods is three by default. If you install IOMesh Enterprise Edition, you can deploy more than three chunk pods。
+An optional step. The number of IOMesh chunk pods is three by default. If you install IOMesh Enterprise Edition, you can deploy more than three chunk pods.
iomesh:
chunk:
replicaCount: 3
@@ -150,7 +150,7 @@ It is recommended that you only configure values. For more configurations, refer to Pod Affinity .
An optional step. Configure the podDeletePolicy field to determine whether the system should automatically delete the Pod and rebuild it on another healthy node when the Kubernetes node that hosts the Pod fails. This configuration applies only to the Pod with an IOMesh-created PVC mounted and the access mode set to ReadWriteOnly.
-If left unspecified, this field is set to no-delete-pod by default, indicating that the system won't automatically delete and rebuild the Pod in case of node failure.
+If left unspecified, the value of this field will be set to no-delete-pod by default, indicating that the system won't automatically delete and rebuild the Pod in case of node failure.
csi-driver:
driver:
controller:
@@ -220,10 +220,10 @@
-NOTE: After installing IOMesh, the prepare-csi Pod will automatically start on all schedulable nodes in the Kubernetes cluster to install and configure open-iscsi. If the installation of open-iscsi is successful on all nodes, the system will automatically clean up the prepare-csi Pod. However, if the installation of open-iscsi fails on any node, manual configuration of open-iscsi is required to determine the cause of the installation failure.
+NOTE: After installing IOMesh, the prepare-csi pod will automatically start on all schedulable nodes in the Kubernetes cluster to install and configure open-iscsi. If the installation of open-iscsi is successful on all nodes, the system will automatically clean up all prepare-csi pods. However, if the installation of open-iscsi fails on any node, manual configuration of open-iscsi is required to determine the cause of the installation failure.
-NOTE: If open-iscsi is manually deleted after installing IOMesh, the prepare-csi Pod will not automatically start to install open-iscsi when reinstalling IOMesh. In this case, manual configuration of open-iscsi is necessary.
+NOTE: If open-iscsi is manually deleted after installing IOMesh, the prepare-csi pod will not automatically start to install open-iscsi when reinstalling IOMesh. In this case, manual configuration of open-iscsi is necessary.
@@ -254,7 +254,7 @@
\ No newline at end of file
diff --git a/next/deploy-iomesh-cluster/setup-iomesh.html b/next/deploy-iomesh-cluster/setup-iomesh.html
index f0ac27b6..0b1cf74f 100644
--- a/next/deploy-iomesh-cluster/setup-iomesh.html
+++ b/next/deploy-iomesh-cluster/setup-iomesh.html
@@ -126,7 +126,7 @@
