From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] applied-series: [PATCH manager 0/2] fix #5570 ceph mds: allow custom MDS IDs from the UI
Date: Tue, 23 Jul 2024 08:52:16 +0200 [thread overview]
Message-ID: <d338e493-3ade-4b23-9662-29129ea62a96@proxmox.com> (raw)
In-Reply-To: <aa1f3159-aab7-4aa2-8997-3cf7351d0956@proxmox.com>
On 2024-07-22 18:57, Thomas Lamprecht wrote:
> Am 10/07/2024 um 14:42 schrieb Aaron Lauterer:
>> The ID for the MDS cannot start with a number [0]. The first patch adds
>> a check for this.
>>
>> The second patch is the actual fix, by reworking the edit window when
>> adding new MDS'.
>>
>> By allowing the users to set the name of the MDS directly, we can catch
>> the situation where the hostname starts with a number and let the user
>> decide how it should be named. Similar to what they can already do on
>> the CLI.
>>
>>
>> Another approach would be to leave the UI as is and catch the situation
>> in the backend. If an ID that starts with a number is detected, we could
>> prepend it with a default string.
>>
>> [0] https://docs.ceph.com/en/latest/man/8/ceph-mds/
>>
>> Aaron Lauterer (2):
>> api: ceph mds: avoid creating MDS when ID starts with number
>> fix#5570 ui: ceph: make MDS ID configurable
>>
>> PVE/API2/Ceph/MDS.pm | 2 ++
>> www/manager6/ceph/ServiceList.js | 21 +++++++++++----------
>> 2 files changed, 13 insertions(+), 10 deletions(-)
>>
>
>
> applied with a small s/service_id/serviceID/ style fix squashed into the
> UI patch plus added the missing space in the subject between "fix" and the
> issue ID, thanks!
>
> Oh, I also made a follow-up [0] that makes the field required now to avoid
> an API error if the user clears the field before submitting.<
thx for the fixes!
>
> [0]: https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=d69d4ed8cb276b492a5fe7883f94db777e06d2b2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-07-23 6:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 12:42 [pve-devel] " Aaron Lauterer
2024-07-10 12:42 ` [pve-devel] [PATCH manager 1/2] api: ceph mds: avoid creating MDS when ID starts with number Aaron Lauterer
2024-07-10 12:43 ` [pve-devel] [PATCH manager 2/2] fix#5570 ui: ceph: make MDS ID configurable Aaron Lauterer
2024-07-10 13:59 ` Christoph Heiss
2024-07-10 14:18 ` Aaron Lauterer
2024-07-10 14:24 ` Christoph Heiss
2024-07-10 13:59 ` [pve-devel] [PATCH manager 0/2] fix #5570 ceph mds: allow custom MDS IDs from the UI Christoph Heiss
2024-07-22 16:57 ` [pve-devel] applied-series: " Thomas Lamprecht
2024-07-23 6:52 ` 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=d338e493-3ade-4b23-9662-29129ea62a96@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox