From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexandre Derumier <aderumier@odiso.com>
Subject: [pve-devel] applied: [PATCH v2 pve-manager 1/1] ui: ceph status: add pg warning state
Date: Mon, 13 Nov 2023 16:26:35 +0100 [thread overview]
Message-ID: <8421a91e-8b8c-4451-b801-3e0caa2cc699@proxmox.com> (raw)
In-Reply-To: <20230623094512.454438-3-aderumier@odiso.com>
Am 23/06/2023 um 11:45 schrieb Alexandre Derumier:
> Like ceph mgr dashboard, we need a warning state.
>
> - set degraded as warning instead working
> - set undersized as warning instead error
> - rename error as critical
> - add "working" (info-blue) color for working state
> - use warning (orange) color for warning state
>
> Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
> ---
> www/manager6/ceph/StatusDetail.js | 31 +++++++++++++++++++------------
> 1 file changed, 19 insertions(+), 12 deletions(-)
>
>
applied, thanks!
I folded in the CSS class into this patch to be added to pve-manager's
CSS file for now and renamed "Working" into "Busy", which is IMO slightly
better conveying what we mean here.
next prev parent reply other threads:[~2023-11-13 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 9:45 [pve-devel] [PATCH-SERIE proxmox-widget-toolkit/pve-manager] ceph ui: " Alexandre Derumier
2023-06-23 9:45 ` [pve-devel] [PATCH proxmox-widget-toolkit 1/1] css: add .working color #3892d4 Alexandre Derumier
2023-06-23 9:45 ` [pve-devel] [PATCH v2 pve-manager 1/1] ui: ceph status: add pg warning state Alexandre Derumier
2023-11-13 15:26 ` Thomas Lamprecht [this message]
2023-08-08 11:19 ` [pve-devel] [PATCH-SERIE proxmox-widget-toolkit/pve-manager] ceph ui: " Aaron Lauterer
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=8421a91e-8b8c-4451-b801-3e0caa2cc699@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=aderumier@odiso.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.