Skip to content

Commit 874cee2

Browse files
committed
Fixed broken links
1 parent d5b9c8f commit 874cee2

File tree

4 files changed

+45
-7
lines changed

4 files changed

+45
-7
lines changed

docs/deployments/aws-ec2/install-simplyblock.md

+4
Original file line numberDiff line numberDiff line change
@@ -20,3 +20,7 @@ weight: 30100
2020

2121
<!-- include: install storage plane (bare metal) documentation -->
2222
--8<-- "install-storage-plane-bare-metal.md"
23+
24+
Now that the cluster is ready, it is time to install the [Kubernetes CSI Driver](install-simplyblock-csi.md) or learn
25+
how to use the simplyblock storage cluster to
26+
[manually provision logical volumes](../../usage/baremetal/provisioning.md).

docs/deployments/baremetal/install-simplyblock.md

+4
Original file line numberDiff line numberDiff line change
@@ -17,3 +17,7 @@ weight: 30100
1717

1818
<!-- include: install storage plane (bare metal) documentation -->
1919
--8<-- "install-storage-plane-bare-metal.md"
20+
21+
Now that the cluster is ready, it is time to install the [Kubernetes CSI Driver](install-simplyblock-csi.md) or learn
22+
how to use the simplyblock storage cluster to
23+
[manually provision logical volumes](../../usage/baremetal/provisioning.md).

docs/deployments/kubernetes/install-simplyblock/disaggregated.md

+37-3
Original file line numberDiff line numberDiff line change
@@ -8,11 +8,45 @@ A disaggregated setup on Kubernetes is very similar to a bare metal installation
88
!!! danger
99
Simplyblock requires a fully redundant network interconnect, implemented via a solution such as LACP or Static
1010
LAG. Failing to provide that may cause data corruption or data loss in case of network issues. For more information
11-
see the [Network Considerations](../../deployments/deployment-planning/network-considerations.md)
11+
see the [Network Considerations](../../../deployments/deployment-planning/network-considerations.md)
1212
section.
1313

14-
<!-- include: install intro -->
15-
--8<-- "bare-metal-intro.md"
14+
Installing simplyblock for production, requires a few components to be installed, as well as a couple of configurations
15+
to secure the network, ensure the performance and data protection in the case of hardware or software failures.
16+
17+
Simplyblock provides a test script to automatically check your system's configuration. While it may not catch all
18+
edge cases, it can help to streamline the configuration check. This script can be run multiple times during the
19+
preparation phase to find missing configuration during the process.
20+
21+
```bash title="Automatically check your configuration"
22+
curl -L https://sblk.xyz/prerequisites | bash
23+
```
24+
25+
## Before We Start
26+
27+
A simplyblock production cluster consists of three different types of nodes:
28+
29+
1. _Management nodes_ are part of the control plane which managed the cluster(s). A production cluster requires at least **three nodes**.
30+
2. _Storage nodes_ are part of a specific storage cluster and provide capacity to the distributed storage pool. A production cluster requires at least **three nodes**.
31+
3. _Secondary nodes_ are part of a specific storage cluster and enable automatic fail over for NVMe-oF connections. A production cluster requires at least **one node**.
32+
33+
A single control plane can manage one or more clusters. If started afresh, a control plane must be set up before
34+
creating a storage cluster. If there is a preexisting control plane, an additional storage cluster can be added
35+
to it directly.
36+
37+
More information on the control plane, storage plane, as well as the different node types is available under
38+
[Simplyblock Cluster](../../../architecture/concepts/simplyblock-cluster.md) in the architecture section.
39+
40+
## Network Preparation
41+
42+
Simplyblock recommends two individual network interfaces, one for the control plane and one for the storage plane.
43+
Hence, in the following installation description, we assume two separated subnets. To install simplyblock in your
44+
environment, you may have to adopt these commands to match your configuration.
45+
46+
| Network interface | Network definition | Abbreviation | Subnet |
47+
|-------------------|--------------------|--------------|-----------------|
48+
| eth0 | Control Plane | control | 192.168.10.0/24 |
49+
| eth1 | Storage Plane | storage | 10.10.10.0/24 |
1650

1751
<!-- include: install control plane documentation -->
1852
--8<-- "install-control-plane.md"

snippets/install-storage-plane-bare-metal.md

-4
Original file line numberDiff line numberDiff line change
@@ -327,7 +327,3 @@ The command output should look like this and respond with a successful activatio
327327
2025-02-28 13:35:55,791: INFO: {"cluster_id": "7bef076c-82b7-46a5-9f30-8c938b30e655", "event": "STATUS_CHANGE", "object_name": "Cluster", "message": "Cluster status changed from in_activation to active", "caused_by": "cli"}
328328
2025-02-28 13:35:55,794: INFO: Cluster activated successfully
329329
```
330-
331-
Now that the cluster is ready, it is time to install the [Kubernetes CSI Driver](install-simplyblock-csi.md) or learn
332-
how to use the simplyblock storage cluster to
333-
[manually provision logical volumes](../../usage/baremetal/provisioning.md).

0 commit comments

Comments
 (0)