[pve-devel] [PATCH] pmxcfs: fix wrong information now covered in pvecm

Thomas Lamprecht t.lamprecht at proxmox.com
Thu Oct 20 12:01:48 CEST 2016


The "Remove Cluster configuration" section is outdated and has also
missing steps (e.g. stopping corosync before removing its config)

We have the information in the pvecm.adoc (Cluster Manager) so delete
the howto and reference the one from pvecm instead.

Signed-off-by: Thomas Lamprecht <t.lamprecht at proxmox.com>
---

Linking stuff is currently not trivial, multiple ifdef have to be defined.
Further asciidoc cannot do "elsif" or "else" which makes the process
cumbersome.
Also inter linking to other chapters is not really possible, afaik. At least
not if I open a chapter-%.html, int the all in one pve-admin-guide.html it
works naturally.

A preprocessor directive like link::/pve-docs-link/CHAPTER/ID
for example: link::/pve-docs-link/pvecm/heading-id
which generates context sensitive:
* link to the id for the all in one docs (pve-admin-guide.*)
* link to the other chapter + id for the single chapter one
* the wiki link for wiki pages
* a note for man pages to look at "man CHAPTER Section ID"

would be an idea, cannot really say how good it works with the current
preprocessor/tooling. (hadn't time to test implement it).
Any comments here?

 pmxcfs.adoc | 39 ++++++++++++++-------------------------
 1 file changed, 14 insertions(+), 25 deletions(-)

diff --git a/pmxcfs.adoc b/pmxcfs.adoc
index d35c960..a02d82e 100644
--- a/pmxcfs.adoc
+++ b/pmxcfs.adoc
@@ -174,34 +174,23 @@ The recommended way is to reinstall the node after you removed it from
 your cluster. This makes sure that all secret cluster/ssh keys and any
 shared configuration data is destroyed.
 
-In some cases, you might prefer to put a node back to local mode
-without reinstall, which is described here:
+In some cases, you might prefer to put a node back to local mode without
+reinstall, which is described in the 'Separate A Node Without Reinstalling'
+paragraph from the 'Cluster Manager' category.
 
-* stop the cluster file system in `/etc/pve/`
-
- # systemctl stop pve-cluster
-
-* start it again but forcing local mode
-
- # pmxcfs -l
-
-* remove the cluster configuration
-
- # rm /etc/pve/cluster.conf
- # rm /etc/cluster/cluster.conf
- # rm /var/lib/pve-cluster/corosync.authkey
-
-* stop the cluster file system again
-
- # systemctl stop pve-cluster
-
-* restart PVE services (or reboot)
+ifdef::manvolnum[]
+See:
+[source,bash]
+----
+man pvecm
+----
+endif::manvolnum[]
 
- # systemctl start pve-cluster
- # systemctl restart pvedaemon
- # systemctl restart pveproxy
- # systemctl restart pvestatd
+ifdef::wiki[]
+See:
 
+link:/wiki/Cluster_Manager[Cluster Manager]
+endif::wiki[]
 
 ifdef::manvolnum[]
 include::pve-copyright.adoc[]
-- 
2.1.4





More information about the pve-devel mailing list