all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Alexandre Derumier <aderumier@odiso.com>
Subject: Re: [pve-devel] [PATCH-SERIE proxmox-widget-toolkit/pve-manager] ceph ui: add pg warning state
Date: Tue, 8 Aug 2023 13:19:50 +0200	[thread overview]
Message-ID: <35984c21-22b0-901a-3d1d-878a2b44d29d@proxmox.com> (raw)
In-Reply-To: <20230623094512.454438-1-aderumier@odiso.com>

sorry for missing this initially. Looks good and easy to distinguish now in the 
dark & light theme.


consider this:

Tested-By: Aaron Lauterer <a.lauterer@proxmox.com>
Reviewed-By: Aaron Lauterer <a.lauterer@proxmox.com>

On 6/23/23 11:45, Alexandre Derumier wrote:
> This patch serie improve ceph dashboard adding a new pg warning state.
> Currently undersized pg displayed as error state, and degraded as working state.
> 
> working is now displayed with blue color, and warning with orange color
> 
> changelog v2:
>   - fix Aaron comments
> 
> proxmox-widget-toolkit:
> 
> Alexandre Derumier (1):
>    css: add .working color #3892d4
> 
>   src/css/ext6-pmx.css | 4 ++++
>   1 file changed, 4 insertions(+)
> 
> pve-manager:
> 
> Alexandre Derumier (1):
>    ui: ceph status: add pg warning state
> 
>   www/manager6/ceph/StatusDetail.js | 31 +++++++++++++++++++------------
>   1 file changed, 19 insertions(+), 12 deletions(-)
> 




      parent reply	other threads:[~2023-08-08 11:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23  9:45 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   ` [pve-devel] applied: " Thomas Lamprecht
2023-08-08 11:19 ` Aaron Lauterer [this message]

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=35984c21-22b0-901a-3d1d-878a2b44d29d@proxmox.com \
    --to=a.lauterer@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal