mirror of
https://git.proxmox.com/git/pve-docs
synced 2025-06-27 10:29:40 +00:00
pvecm: replace {PVE} with {pve}
although they both act the same, {pve} is more common throughout the docs, so this helps to keep things more consistent Signed-off-by: Dylan Whyte <d.whyte@proxmox.com>
This commit is contained in:
parent
a37d539fe4
commit
65a0aa490b
@ -24,7 +24,7 @@ Cluster Manager
|
|||||||
:pve-toplevel:
|
:pve-toplevel:
|
||||||
endif::manvolnum[]
|
endif::manvolnum[]
|
||||||
|
|
||||||
The {PVE} cluster manager `pvecm` is a tool to create a group of
|
The {pve} cluster manager `pvecm` is a tool to create a group of
|
||||||
physical servers. Such a group is called a *cluster*. We use the
|
physical servers. Such a group is called a *cluster*. We use the
|
||||||
http://www.corosync.org[Corosync Cluster Engine] for reliable group
|
http://www.corosync.org[Corosync Cluster Engine] for reliable group
|
||||||
communication. There's no explicit limit for the number of nodes in a cluster.
|
communication. There's no explicit limit for the number of nodes in a cluster.
|
||||||
@ -90,7 +90,7 @@ upgrade procedure to {pve} 6.0.
|
|||||||
Preparing Nodes
|
Preparing Nodes
|
||||||
---------------
|
---------------
|
||||||
|
|
||||||
First, install {PVE} on all nodes. Make sure that each node is
|
First, install {pve} on all nodes. Make sure that each node is
|
||||||
installed with the final hostname and IP configuration. Changing the
|
installed with the final hostname and IP configuration. Changing the
|
||||||
hostname and IP is not possible after cluster creation.
|
hostname and IP is not possible after cluster creation.
|
||||||
|
|
||||||
@ -871,10 +871,10 @@ pvecm status
|
|||||||
If you see a healthy cluster state, it means that your new link is being used.
|
If you see a healthy cluster state, it means that your new link is being used.
|
||||||
|
|
||||||
|
|
||||||
Role of SSH in {PVE} Clusters
|
Role of SSH in {pve} Clusters
|
||||||
-----------------------------
|
-----------------------------
|
||||||
|
|
||||||
{PVE} utilizes SSH tunnels for various features.
|
{pve} utilizes SSH tunnels for various features.
|
||||||
|
|
||||||
* Proxying console/shell sessions (node and guests)
|
* Proxying console/shell sessions (node and guests)
|
||||||
+
|
+
|
||||||
|
Loading…
Reference in New Issue
Block a user