all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Dylan Whyte <d.whyte@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs 3/6] pvecm: fix command output formatting
Date: Wed, 15 Sep 2021 15:36:15 +0200	[thread overview]
Message-ID: <20210915133618.143859-3-d.whyte@proxmox.com> (raw)
In-Reply-To: <20210915133618.143859-1-d.whyte@proxmox.com>

- Remove host name from commands, where it provided no value
- Display new command output for pvecm status
- Shorten command output where unneccessary
- Change migration network example to use CIDR address rather than
  address + netmask

Signed-off-by: Dylan Whyte <d.whyte@proxmox.com>
---
 pvecm.adoc | 37 +++++++++++++++++--------------------
 1 file changed, 17 insertions(+), 20 deletions(-)

diff --git a/pvecm.adoc b/pvecm.adoc
index 2d1c744..2908267 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -210,7 +210,7 @@ Join Node to Cluster via Command Line
 Log in to the node you want to join into an existing cluster via `ssh`.
 
 ----
- hp2# pvecm add IP-ADDRESS-CLUSTER
+ # pvecm add IP-ADDRESS-CLUSTER
 ----
 
 For `IP-ADDRESS-CLUSTER`, use the IP or hostname of an existing cluster node.
@@ -225,14 +225,21 @@ To check the state of the cluster use:
 
 .Cluster status after adding 4 nodes
 ----
-hp2# pvecm status
+ # pvecm status
+Cluster information
+~~~~~~~~~~~~~~~~~~~
+Name:             prod-central
+Config Version:   3
+Transport:        knet
+Secure auth:      on
+
 Quorum information
 ~~~~~~~~~~~~~~~~~~
-Date:             Mon Apr 20 12:30:13 2015
+Date:             Tue Sep 14 11:06:47 2021
 Quorum provider:  corosync_votequorum
 Nodes:            4
 Node ID:          0x00000001
-Ring ID:          1/8
+Ring ID:          1.1a8
 Quorate:          Yes
 
 Votequorum information
@@ -260,7 +267,7 @@ If you only want a list of all nodes, use:
 
 .List nodes in a cluster
 ----
-hp2# pvecm nodes
+ # pvecm nodes
 
 Membership information
 ~~~~~~~~~~~~~~~~~~~~~~
@@ -303,7 +310,7 @@ Log in to a *different* cluster node (not hp4), and issue a `pvecm nodes`
 command to identify the node ID to remove:
 
 ----
-hp1# pvecm nodes
+ hp1# pvecm nodes
 
 Membership information
 ~~~~~~~~~~~~~~~~~~~~~~
@@ -337,14 +344,7 @@ look something like:
 ----
 hp1# pvecm status
 
-Quorum information
-~~~~~~~~~~~~~~~~~~
-Date:             Mon Apr 20 12:44:28 2015
-Quorum provider:  corosync_votequorum
-Nodes:            3
-Node ID:          0x00000001
-Ring ID:          1/8
-Quorate:          Yes
+...
 
 Votequorum information
 ~~~~~~~~~~~~~~~~~~~~~~
@@ -1308,8 +1308,7 @@ iface eno1 inet manual
 # public network
 auto vmbr0
 iface vmbr0 inet static
-    address 192.X.Y.57
-    netmask 255.255.250.0
+    address 192.X.Y.57/24
     gateway 192.X.Y.1
     bridge-ports eno1
     bridge-stp off
@@ -1318,14 +1317,12 @@ iface vmbr0 inet static
 # cluster network
 auto eno2
 iface eno2 inet static
-    address  10.1.1.1
-    netmask  255.255.255.0
+    address  10.1.1.1/24
 
 # fast network
 auto eno3
 iface eno3 inet static
-    address  10.1.2.1
-    netmask  255.255.255.0
+    address  10.1.2.1/24
 ----
 
 Here, we will use the network 10.1.2.0/24 as a migration network. For
-- 
2.30.2





  parent reply	other threads:[~2021-09-15 13:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15 13:36 [pve-devel] [PATCH pve-docs 1/6] pvecm: language and format fixup Dylan Whyte
2021-09-15 13:36 ` [pve-devel] [PATCH pve-docs 2/6] pvecm: replace {PVE} with {pve} Dylan Whyte
2021-09-15 13:36 ` Dylan Whyte [this message]
2021-09-15 13:36 ` [pve-devel] [PATCH pve-docs 4/6] pvecm: update instructions to add redundant links Dylan Whyte
2021-09-15 13:36 ` [pve-devel] [PATCH pve-docs 5/6] pvecm: add note about corosync killnode error Dylan Whyte
2021-09-16  8:04   ` Fabian Ebner
2021-09-15 13:36 ` [pve-devel] [PATCH pve-docs 6/6] fix 3375: warn user to remove replication jobs Dylan Whyte
2021-09-15 15:03 ` [pve-devel] applied-series: [PATCH pve-docs 1/6] pvecm: language and format fixup Thomas Lamprecht

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=20210915133618.143859-3-d.whyte@proxmox.com \
    --to=d.whyte@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal