Skip to content

Update further-considerations.md #50

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Apr 22, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 9 additions & 5 deletions docs/deployments/deployment-planning/further-considerations.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,12 +12,16 @@ Simplyblock contains two major components, the control plane and the storage pla

!!! info
A single storage plane cluster can be set up from both x86-64 and ARM64 CPUs. However, simplyblock recommends to
build a storage plane from a single CPU architecture. When operating a hybrid storage cluster with Kubernetes
a mixed CPU architecture should be limited to one CPU architecture for the disaggregated portion of the storage
cluster and one architecture for the Kubernetes worker nodes.
build a storage plane from a single CPU architecture. This is especially important to consider when running
hyper-converged or in a hybrid setup.

In terms of operating system, simplyblock supports Red Hat-based Linux distribution and recommends a Linux kernel 5.9
or later.
In terms of operating system, simplyblock requires a Red Hat-based Linux distribution version 9 (including Rocky Linux and Alma Linux)
for the control plane nodes and disaggregated storage nodes (docker-swarm) and recommends a Linux kernel 5.9 or later.

For storage nodes running in Kubernetes, any Linux distribution (RHEL-based, Debian-based, Talos) can be used. For more
information, see the supported [Linux Distributions Matrix](../../reference/supported-linux-distributions.md).

For any client host, the `nvmf-tcp` module must be loaded and support [NVMe Multipathing](https://docs.kernel.org/admin-guide/nvme-multipath.html){:target="_blank" rel="noopener"}.

## Storage Considerations

Expand Down