proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-05-05 22:25:10 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

pvecm: expand on public/cluster networks

Browse Source 
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
This commit is contained in:
Aaron Lauterer 2023-11-20 16:48:30 +01:00 committed by Thomas Lamprecht
parent 4df8e368fa
commit d4ee0a1992
1 changed files with 11 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
pveceph.adoc
View File

@ -241,22 +241,26 @@ The configuration step includes the following settings:
[[pve_ceph_wizard_networks]] [[pve_ceph_wizard_networks]]
* *Public Network:* This network will be used for public storage communication * *Public Network:* This network will be used for public storage communication
(e.g., for virtual machines using a Ceph RBD backed disk, or a CephFS mount). (e.g., for virtual machines using a Ceph RBD backed disk, or a CephFS mount),
This setting is required. and communication between the different Ceph services. This setting is
required.
+ +
Separating your Ceph traffic from cluster communication, and possible the Separating your Ceph traffic from the {pve} cluster communication (corosync),
front-facing (public) networks of your virtual gusts, is highly recommended. and possible the front-facing (public) networks of your virtual guests, is
Otherwise, Ceph's high-bandwidth IO-traffic could cause interference with highly recommended. Otherwise, Ceph's high-bandwidth IO-traffic could cause
other low-latency dependent services. interference with other low-latency dependent services.
[thumbnail="screenshot/gui-node-ceph-install-wizard-step2.png"] [thumbnail="screenshot/gui-node-ceph-install-wizard-step2.png"]
* *Cluster Network:* Specify to separate the xref:pve_ceph_osds[OSD] replication * *Cluster Network:* Specify to separate the xref:pve_ceph_osds[OSD] replication
and heartbeat traffic as well. and heartbeat traffic as well. This setting is optional.
+ +
Using a physically separated network is recommended, as it will relieve the Using a physically separated network is recommended, as it will relieve the
Ceph public and the virtual guests network, while also providing a significant Ceph public and the virtual guests network, while also providing a significant
Ceph performance improvements. Ceph performance improvements.
+
The Ceph cluster network can be configured and moved to another physically
separated network at a later time.
You have two more options which are considered advanced and therefore should You have two more options which are considered advanced and therefore should
only changed if you know what you are doing. only changed if you know what you are doing.