public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] applied: [PATCH docs] pvecm: improve SSH section
Date: Wed, 25 Nov 2020 12:42:22 +0100	[thread overview]
Message-ID: <20201125114222.1873087-1-f.gruenbichler@proxmox.com> (raw)

reword some parts, fix wrong information about port forwarding

Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
---
 pvecm.adoc | 18 ++++++++++--------
 1 file changed, 10 insertions(+), 8 deletions(-)

diff --git a/pvecm.adoc b/pvecm.adoc
index cbbcf60..0fad203 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -872,17 +872,19 @@ If you see a healthy cluster state, it means that your new link is being used.
 Role of SSH in {PVE} Clusters
 -----------------------------
 
-{PVE} utilizes SSH tunnels for various operations.
+{PVE} utilizes SSH tunnels for various features.
 
-* Proxying terminal sessions of node and containers between nodes
+* Proxying console/shell sessions (node and guests)
 +
-When you connect another nodes shell through the web interface, for example, a
-non-interactive SSH tunnel is started in order to forward the necessary ports
-for the VNC connection.
+When using the shell for node B while being connected to node A, connects to a
+terminal proxy on node A, which is in turn connected to the login shell on node
+B via a non-interactive SSH tunnel.
 
-* VM and CT memory and local-storage migration, if the cluster wide migration
-  settings are not configured 'insecure' mode. During a VM migration an SSH
-  tunnel is established between the target and source nodes.
+* VM and CT memory and local-storage migration in 'secure' mode.
++
+During the migration one or more SSH tunnel(s) are established between the
+source and target nodes, in order to exchange migration information and
+transfer memory and disk contents.
 
 * Storage replication
 
-- 
2.20.1





                 reply	other threads:[~2020-11-25 11:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201125114222.1873087-1-f.gruenbichler@proxmox.com \
    --to=f.gruenbichler@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal