public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Dominic Jäger" <d.jaeger@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 4/4] qdevice: Clarify required packages
Date: Tue, 28 Jul 2020 11:32:15 +0200	[thread overview]
Message-ID: <20200728093215.44860-4-d.jaeger@proxmox.com> (raw)
In-Reply-To: <20200728093215.44860-1-d.jaeger@proxmox.com>

I overlooked the different package names myself. Writing out the two commands
makes this more difficult to overlook.

Signed-off-by: Dominic Jäger <d.jaeger@proxmox.com>
---
 pvecm.adoc | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/pvecm.adoc b/pvecm.adoc
index 47916fa..cf5f052 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -957,8 +957,17 @@ configured to do so.
 The traffic between the daemon and the cluster must be encrypted to ensure a
 safe and secure QDevice integration in {pve}.
 
-First, install the 'corosync-qnetd' package on your external server and
-the 'corosync-qdevice' package on all cluster nodes.
+First, install the 'corosync-qnetd' package on your external server
+
+----
+external# apt install corosync-qnetd
+----
+
+and the 'corosync-qdevice' package on all cluster nodes
+
+----
+pve# apt install corosync-qdevice
+----
 
 After that, ensure that all your nodes on the cluster are online.
 
-- 
2.20.1




  parent reply	other threads:[~2020-07-28  9:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28  9:32 [pve-devel] [PATCH docs 1/4] qdevice: Remove a wrong 's' Dominic Jäger
2020-07-28  9:32 ` [pve-devel] [PATCH docs 2/4] pvecm: Add comma after 'First' Dominic Jäger
2020-07-28  9:32 ` [pve-devel] [PATCH docs 3/4] qdevice: Add note about root login requirements Dominic Jäger
2020-07-28  9:32 ` Dominic Jäger [this message]
2020-08-11 13:34 ` [pve-devel] applied-series: [PATCH docs 1/4] qdevice: Remove a wrong 's' Fabian Grünbichler

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=20200728093215.44860-4-d.jaeger@proxmox.com \
    --to=d.jaeger@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