From: "Shannon Sterz" <s.sterz@proxmox.com>
To: "Proxmox Datacenter Manager development discussion"
<pdm-devel@lists.proxmox.com>,
"Stefan Hanreich" <s.hanreich@proxmox.com>
Subject: Re: [pdm-devel] [PATCH pve-network v3 6/6] api: zones: update schema of endpoints
Date: Wed, 03 Sep 2025 11:37:02 +0200 [thread overview]
Message-ID: <DCJ2BCMYU438.3NGQUQWK0B6YX@proxmox.com> (raw)
In-Reply-To: <20250902140956.228031-10-s.hanreich@proxmox.com>
small comments in-line
On Tue Sep 2, 2025 at 4:09 PM CEST, Stefan Hanreich wrote:
> The possible properties returned by the zone endpoints were only
> partly documented. Add all missing properties and improve descriptions
> for existing properties.
>
> Extract all duplicate properties into a separate variable, so we
> don't have to rewrite the whole API definition for every endpoint.
>
> Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
> ---
> src/PVE/API2/Network/SDN/Zones.pm | 203 +++++++++++++++++++++--
> src/PVE/Network/SDN/Zones/EvpnPlugin.pm | 22 ++-
> src/PVE/Network/SDN/Zones/QinQPlugin.pm | 6 +-
> src/PVE/Network/SDN/Zones/VlanPlugin.pm | 1 +
> src/PVE/Network/SDN/Zones/VxlanPlugin.pm | 15 +-
> 5 files changed, 218 insertions(+), 29 deletions(-)
>
-->8 snip 8<--
> + 'vxlan-port' => {
> + description =>
> + "UDP port that should be used for the VXLAN tunnel (default 4789). VXLAN zone only.",
wouldn't it make sense to define a `default` property here then? so:
default => 4789,
-->8 snip 8<--
> 'rt-import' => {
> type => 'string',
> - description => "Route-Target import",
> + description =>
> + 'List of Route Targets that should be imported into the VRF of the zone',
nit: you added a period to all other descriptions here, so end this
sentence with one too?
> optional => 1,
> format => 'pve-sdn-bgp-rt-list',
> },
> diff --git a/src/PVE/Network/SDN/Zones/QinQPlugin.pm b/src/PVE/Network/SDN/Zones/QinQPlugin.pm
> index 5806e69..3c72d35 100644
> --- a/src/PVE/Network/SDN/Zones/QinQPlugin.pm
> +++ b/src/PVE/Network/SDN/Zones/QinQPlugin.pm
> @@ -18,11 +18,11 @@ sub properties {
> tag => {
> type => 'integer',
> minimum => 0,
> - description => "Service-VLAN Tag",
> + description => "Service-VLAN Tag (outer VLAN)",
> },
since this is so short, i think it's probably fine to leave that without
a period here.
> mtu => {
> type => 'integer',
> - description => "MTU",
> + description => "MTU of the zone, will be used for the created VNet bridges.",
> optional => 1,
> },
> 'vlan-protocol' => {
> @@ -30,6 +30,8 @@ sub properties {
> enum => ['802.1q', '802.1ad'],
> default => '802.1q',
> optional => 1,
> + description =>
> + "Which VLAN protocol should be used for the creation of the QinQ zone",
nit: add a period here too?
> },
> };
> }
> diff --git a/src/PVE/Network/SDN/Zones/VlanPlugin.pm b/src/PVE/Network/SDN/Zones/VlanPlugin.pm
> index 90f16bf..9d6932f 100644
> --- a/src/PVE/Network/SDN/Zones/VlanPlugin.pm
> +++ b/src/PVE/Network/SDN/Zones/VlanPlugin.pm
> @@ -27,6 +27,7 @@ sub properties {
> return {
> 'bridge' => {
> type => 'string',
> + description => 'the bridge for which VLANs should be managed',
nit: capitalize beginning of sentence and end it in a period?
> },
> 'bridge-disable-mac-learning' => {
> type => 'boolean',
> diff --git a/src/PVE/Network/SDN/Zones/VxlanPlugin.pm b/src/PVE/Network/SDN/Zones/VxlanPlugin.pm
> index 8f6fba0..7ab89da 100644
> --- a/src/PVE/Network/SDN/Zones/VxlanPlugin.pm
> +++ b/src/PVE/Network/SDN/Zones/VxlanPlugin.pm
> @@ -27,21 +27,22 @@ sub type {
> sub properties {
> return {
> 'peers' => {
> - description => "peers address list.",
> + description =>
> + "Comma-separated list of peers, that are part of the VXLAN zone. Usually the IPs of the nodes.",
> type => 'string',
> format => 'ip-list',
> },
> - fabric => {
> - description => "SDN fabric to use as underlay for this VXLAN zone.",
> - type => 'string',
> - format => 'pve-sdn-fabric-id',
> - },
> 'vxlan-port' => {
> - description => "Vxlan tunnel udp port (default 4789).",
> + description => "UDP port that should be used for the VXLAN tunnel (default 4789).",
> minimum => 1,
> maximum => 65536,
could also define the default here too?
> type => 'integer',
> },
> + fabric => {
> + description => "SDN fabric to use as underlay for this VXLAN zone.",
> + type => 'string',
> + format => 'pve-sdn-fabric-id',
> + },
> };
> }
>
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
next prev parent reply other threads:[~2025-09-03 9:36 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 14:09 [pdm-devel] [PATCH network/proxmox{, -backup, -api-types, -datacenter-manager} v3 00/30] Add initial SDN / EVPN integration Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox v3 1/2] schema: use i64 for minimum / maximum / default integer values Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox v3 2/2] pbs-api-types: fix values for integer schemas Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-backup v3 1/1] api: change integer schema parameters to i64 Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH pve-network v3 1/6] sdn: api: return null for rollback / lock endpoints Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH pve-network v3 2/6] controllers: fix maximum value for ASN Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH pve-network v3 3/6] api: add state standard option Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH pve-network v3 4/6] api: controllers: update schema of endpoints Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH pve-network v3 5/6] api: vnets: " Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH pve-network v3 6/6] api: zones: " Stefan Hanreich
2025-09-03 9:37 ` Shannon Sterz [this message]
2025-09-03 13:04 ` Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-api-types v3 1/6] sdn: add list/create zone endpoints Stefan Hanreich
2025-09-03 9:36 ` Shannon Sterz
2025-09-03 13:15 ` Wolfgang Bumiller
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-api-types v3 2/6] sdn: add list/create vnet endpoints Stefan Hanreich
2025-09-03 9:36 ` Shannon Sterz
2025-09-03 12:07 ` Stefan Hanreich
2025-09-03 13:16 ` Wolfgang Bumiller
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-api-types v3 3/6] sdn: add list/create controller endpoints Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-api-types v3 4/6] sdn: add sdn configuration locking endpoints Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-api-types v3 5/6] tasks: add helper for querying successfully finished tasks Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-api-types v3 6/6] sdn: add helpers for pending values Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-datacenter-manager v3 01/15] server: add locked sdn client helpers Stefan Hanreich
2025-09-03 9:37 ` Shannon Sterz
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-datacenter-manager v3 02/15] ui: pve: sdn: add descriptions for sdn tasks Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-datacenter-manager v3 03/15] api: sdn: add list_zones endpoint Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-datacenter-manager v3 04/15] api: sdn: add create_zone endpoint Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-datacenter-manager v3 05/15] api: sdn: add list_vnets endpoint Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-datacenter-manager v3 06/15] api: sdn: add create_vnet endpoint Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-datacenter-manager v3 07/15] api: sdn: add list_controllers endpoint Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-datacenter-manager v3 08/15] ui: sdn: add EvpnRouteTarget type Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-datacenter-manager v3 09/15] ui: sdn: add vnet icon Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-datacenter-manager v3 10/15] ui: sdn: add view for showing evpn zones Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-datacenter-manager v3 11/15] ui: sdn: add view for showing ip vrfs Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-datacenter-manager v3 12/15] ui: sdn: add component for creating evpn vnets Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-datacenter-manager v3 13/15] ui: sdn: add component for creatin evpn zones Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-datacenter-manager v3 14/15] ui: sdn: add evpn overview panel Stefan Hanreich
2025-09-02 14:09 ` [pdm-devel] [PATCH proxmox-datacenter-manager v3 15/15] ui: sdn: add evpn panel to main menu Stefan Hanreich
2025-09-02 14:13 ` [pdm-devel] [PATCH network/proxmox{, -backup, -api-types, -datacenter-manager} v3 00/30] Add initial SDN / EVPN integration Stefan Hanreich
2025-09-03 16:38 ` [pdm-devel] superseded: " Stefan Hanreich
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=DCJ2BCMYU438.3NGQUQWK0B6YX@proxmox.com \
--to=s.sterz@proxmox.com \
--cc=pdm-devel@lists.proxmox.com \
--cc=s.hanreich@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