all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH manager] ui: ceph: osd: set default icon for other crush types
Date: Thu, 1 Dec 2022 13:23:15 +0100	[thread overview]
Message-ID: <6f4bfc84-750a-20f4-2c3e-bc133c16e8a3@proxmox.com> (raw)
In-Reply-To: <20221117092913.3711879-1-a.lauterer@proxmox.com>

I should have added this right away, but better late than never.
To test this, you need to create additional CRUSH buckets, for example for a 
bucket of the type room:

# ceph osd crush add-bucket room1 room


It should already show up in the OSD panel and if you run

# ceph osd df tree


To move another bucket, e.g. a host, into it:

# ceph osd crush move <nodename> room=room1


To move it back to the default bucket, so you can clean up the room1 bucket:

# ceph osd crush move <nodename> root=default


Remove the room1 bucket:

# ceph osd crush rm room1



On 11/17/22 10:29, Aaron Lauterer wrote:
> Some users have a more complicated CRUSH hierarchy, for example with a
> stretched cluster. The additional hierarchy steps (datacenter, rack,
> room, ...) are shown in the OSD panel. Showing a generic icon for any
> CRUSH types that have not a specific icon configured will make it easier
> to navigate the tree as it will not look somewhat broken and empty.
> 
> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
> ---
>   www/manager6/ceph/OSD.js | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/www/manager6/ceph/OSD.js b/www/manager6/ceph/OSD.js
> index 78f226ff..1255e396 100644
> --- a/www/manager6/ceph/OSD.js
> +++ b/www/manager6/ceph/OSD.js
> @@ -847,7 +847,8 @@ Ext.define('PVE.node.CephOsdTree', {
>   		osd: 'fa-hdd-o',
>   		root: 'fa-server',
>   	    };
> -	    return 'fa x-fa-tree ' + iconMap[data.type];
> +	    let icon = iconMap[data.type] ?? 'fa-folder-o';
> +	    return `fa x-fa-tree ${icon}`;
>   	},
>   },
>   	{ type: 'number', name: 'crush_weight' },




  reply	other threads:[~2022-12-01 12:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17  9:29 Aaron Lauterer
2022-12-01 12:23 ` Aaron Lauterer [this message]
2023-02-08  9:56 ` Aaron Lauterer
2023-02-15 14:08 ` [pve-devel] applied: " Dominik Csapak
2023-02-15 14:16   ` 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=6f4bfc84-750a-20f4-2c3e-bc133c16e8a3@proxmox.com \
    --to=a.lauterer@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