From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fabian Ebner <f.ebner@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager 6/6] ui: cluster backup: use cluster-wide storage selector
Date: Wed, 8 Sep 2021 13:06:34 +0200 [thread overview]
Message-ID: <47056631-ffd7-98cf-38a0-3c81178d56b7@proxmox.com> (raw)
In-Reply-To: <20210906113231.61790-7-f.ebner@proxmox.com>
On 06.09.21 13:32, Fabian Ebner wrote:
> adapted from the existing storage selector.
>
> Previously, only the storages for the local node would be shown, which
> prevented configuring a job for remote nodes when the storage is not
> available on the local node.
>
> In contrast to the existing storage selector, no usage information is
> displayed. It's not readily available, and while it could be extracted
> from the global resource store, that's a bit messy, and in case a
> local storage is available on multiple nodes, there are multiple
> values to deal with. Instead, show the list of nodes where the storage
> is available and whether it is shared, which is relevant when seen
> from a cluster perspective.
>
> Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
> ---
> www/manager6/Makefile | 1 +
> www/manager6/dc/Backup.js | 5 +-
> www/manager6/form/ClusterStorageSelector.js | 96 +++++++++++++++++++++
> 3 files changed, 99 insertions(+), 3 deletions(-)
> create mode 100644 www/manager6/form/ClusterStorageSelector.js
>
not to happy with that one in regards to code reuse.
We either need to make this the parent of the node-specific one and hide combo-grid
columns depending on settings, or vice versa (this extends from the single one).
The former seems a bit more intuitive to me from a quick check, but no hard feelings
on that..
next prev parent reply other threads:[~2021-09-08 11:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 11:32 [pve-devel] [PATCH-SERIES manager] ui: some backup job improvements Fabian Ebner
2021-09-06 11:32 ` [pve-devel] [PATCH manager 1/6] ui: cluster backup: fix running backup with prune settings Fabian Ebner
2021-09-08 10:59 ` [pve-devel] applied: " Thomas Lamprecht
2021-09-06 11:32 ` [pve-devel] [PATCH manager 2/6] ui: factor out input panel for editing " Fabian Ebner
2021-09-08 11:01 ` [pve-devel] applied: " Thomas Lamprecht
2021-09-06 11:32 ` [pve-devel] [PATCH manager 3/6] ui: prune edit: prepare for being re-used for backup jobs Fabian Ebner
2021-09-08 11:01 ` [pve-devel] applied: " Thomas Lamprecht
2021-09-06 11:32 ` [pve-devel] [PATCH manager 4/6] fix #1803: ui: cluster backup: handle job-specific retention options Fabian Ebner
2021-09-08 11:01 ` [pve-devel] applied: " Thomas Lamprecht
2021-09-06 11:32 ` [pve-devel] [PATCH manager 5/6] ui: backup job detail: also show retention settings Fabian Ebner
2021-09-08 11:04 ` Thomas Lamprecht
2021-09-08 14:15 ` [pve-devel] applied: " Thomas Lamprecht
2021-09-06 11:32 ` [pve-devel] [PATCH manager 6/6] ui: cluster backup: use cluster-wide storage selector Fabian Ebner
2021-09-08 11:06 ` Thomas Lamprecht [this message]
2021-09-09 6:56 ` Fabian Ebner
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=47056631-ffd7-98cf-38a0-3c81178d56b7@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@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.