all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Max Carrara" <m.carrara@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH docs v2 1/6] ceph: add anchors for use in troubleshooting section
Date: Wed, 05 Feb 2025 15:20:42 +0100	[thread overview]
Message-ID: <D7KKU5CV8411.4P53ZCPLPRZO@proxmox.com> (raw)
In-Reply-To: <20250205100850.3-1-a.zeidler@proxmox.com>

On Wed Feb 5, 2025 at 11:08 AM CET, Alexander Zeidler wrote:
> Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
> ---
> v2:
> * add two missing anchors to be usable via xref
>

To keep things short:

- Docs now build again (tested with both `make update` and `make deb`).

- Installed the .deb packages on my development VM in order to read the
  docs where they'll be "deployed" - all works fine.

- Gave anchors and hrefs a smoke test by testing 'em out randomly;
  seems like everything's working .
  (tested on multi-page docs, single-page docs, PDF version)

- Also checked if the `id` attribute is set for the smallest headings,
  and it sure is! You can't link to those sections by default (which is
  an AsciiDoc and/or configuration thing, I'm guessing), *but* we should
  still be able to refer to them throughout the docs, if necessary
  (untested).

  For example, the `id` for "Relevant Logs on Affected Node" is
  set correctly as intended: `chapter-pveceph.html#pve_ceph_ts_logs`

- As mentioned before, I find the writing style to be quite nice; I
  especially like how things are broken down into smaller steps and
  paragraphs. No fancy idioms or figures of speech; the writing is
  strictly technical and instructive.

- The instructions themselves also seem fine; I have used similar steps
  the last time I was messing around with my Ceph cluster (was a while
  ago though). I especially like the update on the "Destroy OSDs"
  section; I personally wouldn't have thought of checking that the OSDs
  should have their Used % below the nearfull_ratio before throwing an
  OSD out.

  Full disclosure: The only thing I haven't tried out is removing a node
  that is running Ceph from a cluster. *But* because I wiped a Ceph
  installation from a node before (before re-creating it again) I can
  tell that the steps there are sensible (and *much* safer than what I
  did back then, woops). The only thing I hadn't done was removing the
  node from the CRUSH hierarchy, but I guess in my case Ceph had just
  figured that out itself :P

All in all, unless I missed something or if there are any objections, I
think this can be merged.

Consider:

Reviewed-by: Max Carrara <m.carrara@proxmox.com>
Tested-by: Max Carrara <m.carrara@proxmox.com>



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  parent reply	other threads:[~2025-02-05 14:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 10:08 Alexander Zeidler
2025-02-05 10:08 ` [pve-devel] [PATCH docs v2 2/6] ceph: correct heading capitalization Alexander Zeidler
2025-02-05 10:08 ` [pve-devel] [PATCH docs v2 3/6] ceph: troubleshooting: revise and add frequently needed information Alexander Zeidler
2025-02-05 10:08 ` [pve-devel] [PATCH docs v2 4/6] ceph: osd: revise and expand the section "Destroy OSDs" Alexander Zeidler
2025-02-05 10:08 ` [pve-devel] [PATCH docs v2 5/6] ceph: maintenance: revise and expand section "Replace OSDs" Alexander Zeidler
2025-02-05 10:08 ` [pve-devel] [PATCH docs v2 6/6] pvecm: remove node: mention Ceph and its steps for safe removal Alexander Zeidler
2025-02-05 14:20 ` Max Carrara [this message]
2025-03-24 16:42 ` [pve-devel] applied: [PATCH docs v2 1/6] ceph: add anchors for use in troubleshooting section Aaron Lauterer
2025-03-26 10:20   ` Max Carrara
2025-03-26 13:13     ` Aaron Lauterer
2025-03-26 13:36       ` Max Carrara

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=D7KKU5CV8411.4P53ZCPLPRZO@proxmox.com \
    --to=m.carrara@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