[pve-devel] [PATCH pve-manager v3 3/9] pvestatd: add network resource to status reporting
Thomas Lamprecht
t.lamprecht at proxmox.com
Wed Nov 12 21:39:05 CET 2025
Am 07.11.25 um 15:38 schrieb Stefan Hanreich:
> diff --git a/PVE/API2/Cluster.pm b/PVE/API2/Cluster.pm
> index 479803960..0c779bf9b 100644
> --- a/PVE/API2/Cluster.pm
> +++ b/PVE/API2/Cluster.pm
> @@ -251,7 +251,8 @@ __PACKAGE__->register_method({
> type => {
> description => "Resource type.",
> type => 'string',
> - enum => ['node', 'storage', 'pool', 'qemu', 'lxc', 'openvz', 'sdn'],
> + enum =>
> + ['node', 'storage', 'pool', 'qemu', 'lxc', 'openvz', 'sdn', 'network'],
> },
> status => {
> description => "Resource type dependent status.",
> @@ -431,6 +432,23 @@ __PACKAGE__->register_method({
> optional => 1,
> default => 0,
> },
> + network => {
> + description => "The name of a Network entity (for type 'network').",
> + type => "string",
> + optional => 1,
> + },
> + network_type => {
why not kebab-case like we strongly prefer in general for all new properties in
the API?
> + description => "The type of network resource (for type 'network').",
> + type => "string",
> + enum => ["fabric", "zone"],
> + optional => 1,
> + },
> + protocol => {
> + description =>
> + "The protocol of a fabric (for type 'network', network_type 'fabric').",
> + type => "string",
> + optional => 1,
> + },
> },
> },
> },
More information about the pve-devel
mailing list