Skip to content

Commit

Permalink
deploy: 927e335
Browse files Browse the repository at this point in the history
  • Loading branch information
@gxglls
gxglls committed Dec 5, 2023
1 parent 73c6f93 commit 4e14a40
Show file tree
Hide file tree
Showing 10 changed files with 58 additions and 58 deletions.
2 changes: 1 addition & 1 deletion next/basic-concepts/basic-concepts.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@
<p><strong>Meta</strong></p>
<p>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.</p>
<p><strong>IOMesh CSI Driver</strong></p>
<p>The self-developed CSI driver that adheres to <a href="https://github.com/container-storage-interface/spec/blob/master/spec.md">the CSI standard</a> 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.</p>
<p>The CSI driver that adheres to <a href="https://github.com/container-storage-interface/spec/blob/master/spec.md">the CSI standard</a> 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.</p>
<p><strong>IOMesh Operator</strong></p>
<p>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.</p>
<p><a href="https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/"><strong>Namespace</strong></a></p>
Expand Down
2 changes: 1 addition & 1 deletion next/basic-concepts/basic-concepts/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@
<p><strong>Meta</strong></p>
<p>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.</p>
<p><strong>IOMesh CSI Driver</strong></p>
<p>The self-developed CSI driver that adheres to <a href="https://github.com/container-storage-interface/spec/blob/master/spec.md">the CSI standard</a> 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.</p>
<p>The CSI driver that adheres to <a href="https://github.com/container-storage-interface/spec/blob/master/spec.md">the CSI standard</a> 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.</p>
<p><strong>IOMesh Operator</strong></p>
<p>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.</p>
<p><a href="https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/"><strong>Namespace</strong></a></p>
Expand Down
16 changes: 8 additions & 8 deletions next/cluster-operations/replace-failed-disk.html
View file

Large diffs are not rendered by default.

16 changes: 8 additions & 8 deletions next/cluster-operations/replace-failed-disk/index.html
View file

Large diffs are not rendered by default.

8 changes: 4 additions & 4 deletions next/cluster-operations/scale-out-cluster.html
View file

Large diffs are not rendered by default.

8 changes: 4 additions & 4 deletions next/cluster-operations/scale-out-cluster/index.html
View file

Large diffs are not rendered by default.

30 changes: 15 additions & 15 deletions next/deploy-iomesh-cluster/install-iomesh.html
View file

Large diffs are not rendered by default.

30 changes: 15 additions & 15 deletions next/deploy-iomesh-cluster/install-iomesh/index.html
View file

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion next/deploy-iomesh-cluster/setup-iomesh.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ <h2><a class="anchor" aria-hidden="true" id="configure-devicemap"></a><a href="#
</thead>
<tbody>
<tr><td><code>hybridFlash</code></td><td>Must configure <code>cacheWithJournal</code> and <code>dataStore</code>. <ur><li><code>cacheWithJournal</code> serves the performance layer of storage pool and <strong>MUST</strong> be a partitionable block device with a capacity greater than 60 GB. Two partitions will be created: one for journal and the other for cache. Either SATA or NVMe SSD is recommended.</li><li><code>dataStore</code> is used for the capacity layer of storage pool. Either SATA or SAS HDD is recommended.</li></ur></td></tr>
<tr><td><code>allflash</code></td><td><p>Only need to configure <code>dataStoreWithJournal</code>. </p> <code>dataStoreWithJournal</code> is used for the capacity layer of storage pool. It <strong>MUST</strong> be a partitionable block device with a capacity greater than 60 GB. Two partitions will be created: one for <code>journal</code> and the other for <code>dataStore</code>. Either SATA or NVMe SSD is recommended.</td></tr>
<tr><td><code>allFlash</code></td><td><p>Only need to configure <code>dataStoreWithJournal</code>. </p> <code>dataStoreWithJournal</code> is used for the capacity layer of storage pool. It <strong>MUST</strong> be a partitionable block device with a capacity greater than 60 GB. Two partitions will be created: one for <code>journal</code> and the other for <code>dataStore</code>. Either SATA or NVMe SSD is recommended.</td></tr>
</tbody>
</table>
<p><strong>Device Selector</strong></p>
Expand Down
2 changes: 1 addition & 1 deletion next/deploy-iomesh-cluster/setup-iomesh/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ <h2><a class="anchor" aria-hidden="true" id="configure-devicemap"></a><a href="#
</thead>
<tbody>
<tr><td><code>hybridFlash</code></td><td>Must configure <code>cacheWithJournal</code> and <code>dataStore</code>. <ur><li><code>cacheWithJournal</code> serves the performance layer of storage pool and <strong>MUST</strong> be a partitionable block device with a capacity greater than 60 GB. Two partitions will be created: one for journal and the other for cache. Either SATA or NVMe SSD is recommended.</li><li><code>dataStore</code> is used for the capacity layer of storage pool. Either SATA or SAS HDD is recommended.</li></ur></td></tr>
<tr><td><code>allflash</code></td><td><p>Only need to configure <code>dataStoreWithJournal</code>. </p> <code>dataStoreWithJournal</code> is used for the capacity layer of storage pool. It <strong>MUST</strong> be a partitionable block device with a capacity greater than 60 GB. Two partitions will be created: one for <code>journal</code> and the other for <code>dataStore</code>. Either SATA or NVMe SSD is recommended.</td></tr>
<tr><td><code>allFlash</code></td><td><p>Only need to configure <code>dataStoreWithJournal</code>. </p> <code>dataStoreWithJournal</code> is used for the capacity layer of storage pool. It <strong>MUST</strong> be a partitionable block device with a capacity greater than 60 GB. Two partitions will be created: one for <code>journal</code> and the other for <code>dataStore</code>. Either SATA or NVMe SSD is recommended.</td></tr>
</tbody>
</table>
<p><strong>Device Selector</strong></p>
Expand Down

0 comments on commit 4e14a40

Please sign in to comment.