From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH patches 1/1] fix #6142: ui: dc options: allow custom CIDRs for migration network
Date: Wed, 5 Feb 2025 16:03:09 +0100 [thread overview]
Message-ID: <20250205150309.186958-1-s.hanreich@proxmox.com> (raw)
Sometimes the desired migration network is not configured on any
network interfaces on the node. For instance, if there is a full-mesh
network the CIDR for the router IPs is not configured on any network
interface, but still a valid choice as migration network. This patch
fixes this by allowing users to additionally enter arbitrary CIDRs
into the field setting the migration network.
Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
www/manager6/dc/OptionView.js | 3 +++
1 file changed, 3 insertions(+)
diff --git a/www/manager6/dc/OptionView.js b/www/manager6/dc/OptionView.js
index b200fd12d..bd54d7618 100644
--- a/www/manager6/dc/OptionView.js
+++ b/www/manager6/dc/OptionView.js
@@ -115,6 +115,9 @@ Ext.define('PVE.dc.OptionView', {
emptyText: Proxmox.Utils.defaultText,
autoSelect: false,
skipEmptyText: true,
+ editable: true,
+ notFoundIsValid: true,
+ vtype: 'IP64CIDRAddress',
}],
});
me.add_inputpanel_row('ha', gettext('HA Settings'), {
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-02-05 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 15:03 Stefan Hanreich [this message]
2025-02-05 15:13 ` Stefan Hanreich
2025-02-06 13:50 ` [pve-devel] applied: " Fiona 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=20250205150309.186958-1-s.hanreich@proxmox.com \
--to=s.hanreich@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.