all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-network 4/5] api: add lock and release endpoints for global configuration lock
Date: Fri, 28 Feb 2025 14:05:48 +0100	[thread overview]
Message-ID: <20250228130549.100357-6-s.hanreich@proxmox.com> (raw)
In-Reply-To: <20250228130549.100357-1-s.hanreich@proxmox.com>

This endpoint exposes the newly introduced global lock functionality
via the API. It adds endpoints for acquiring and releasing the lock.
Acquiring the lock is as simple as:

  pvesh create /cluster/sdn/lock

The flag 'allow-pending' governs whether the lock should be acquired
if there are pending configuration changes.

The release endpoint can also be used to forcibly release the lock via
CLI without requiring the knowledge of the lock-secret:

  pvesh delete /cluster/sdn/lock --force 1

Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
 src/PVE/API2/Network/SDN.pm | 81 +++++++++++++++++++++++++++++++++++++
 src/PVE/Network/SDN.pm      | 23 +++++++++++
 2 files changed, 104 insertions(+)

diff --git a/src/PVE/API2/Network/SDN.pm b/src/PVE/API2/Network/SDN.pm
index b09a54b..3377f76 100644
--- a/src/PVE/API2/Network/SDN.pm
+++ b/src/PVE/API2/Network/SDN.pm
@@ -99,6 +99,87 @@ my $create_reload_network_worker = sub {
     return $res->{pid};
 };
 
+__PACKAGE__->register_method({
+    name => 'lock',
+    protected => 1,
+    path => 'lock',
+    method => 'POST',
+    description => "Acquire global lock for SDN configuration",
+    permissions => {
+	check => ['perm', '/sdn', ['SDN.Allocate']],
+    },
+    parameters => {
+	additionalProperties => 0,
+	properties => {
+	    'allow-pending' => {
+		type => 'boolean',
+		optional => 1,
+		default => 0,
+		description => 'if true, allow acquiring lock even though there are pending changes'
+	    }
+	},
+    },
+    returns => {
+	type => 'string',
+    },
+    code => sub {
+	my ($param) = @_;
+
+	return PVE::Network::SDN::lock_sdn_config(
+	    sub {
+		die "configuration has pending changes"
+		    if !$param->{'allow-pending'} && PVE::Network::SDN::has_pending_changes();
+
+		return PVE::Network::SDN::create_global_lock();
+	    },
+	    "could not acquire lock for SDN config"
+	);
+    }
+});
+
+__PACKAGE__->register_method({
+    name => 'release_lock',
+    protected => 1,
+    path => 'lock',
+    method => 'DELETE',
+    description => "Release global lock for SDN configuration",
+    permissions => {
+	check => ['perm', '/sdn', ['SDN.Allocate']],
+    },
+    parameters => {
+	additionalProperties => 0,
+	properties => {
+	    'lock-secret' => get_standard_option('pve-sdn-lock-secret'),
+	    'force' => {
+		type => 'boolean',
+		optional => 1,
+		default => 0,
+		description => 'if true, allow releasing lock without providing the secret'
+	    }
+	},
+    },
+    returns => {
+	type => 'null',
+    },
+    code => sub {
+	my ($param) = @_;
+
+	my $code = sub {
+	    PVE::Network::SDN::delete_global_lock();
+	};
+
+	if ($param->{force}) {
+	    $code->();
+	} else {
+	    PVE::Network::SDN::lock_sdn_config(
+		$code,
+		"could not release lock",
+		$param->{'lock-secret'}
+	    );
+	}
+    }
+});
+
 __PACKAGE__->register_method ({
     name => 'reload',
     protected => 1,
diff --git a/src/PVE/Network/SDN.pm b/src/PVE/Network/SDN.pm
index 08c8700..0f6754a 100644
--- a/src/PVE/Network/SDN.pm
+++ b/src/PVE/Network/SDN.pm
@@ -173,6 +173,29 @@ sub commit_config {
     cfs_write_file($running_cfg, $cfg);
 }
 
+sub has_pending_changes {
+    my $running_cfg = PVE::Network::SDN::running_config();
+
+    # only use configuration files which get written by commit_config here
+    my $config_files = {
+	zones => PVE::Network::SDN::Zones::config(),
+	vnets => PVE::Network::SDN::Vnets::config(),
+	subnets => PVE::Network::SDN::Subnets::config(),
+	controllers => PVE::Network::SDN::Controllers::config(),
+    };
+
+    for my $config_file (keys %$config_files) {
+	my $config = $config_files->{$config_file};
+	my $pending_config = PVE::Network::SDN::pending_config($running_cfg, $config, $config_file);
+
+	for my $id (keys %{$pending_config->{ids}}) {
+	    return 1 if $pending_config->{ids}->{$id}->{pending};
+	}
+    }
+
+    return 0;
+}
+
 sub generate_lock_secret {
     my $min = ord('!'); # first printable ascii
 
-- 
2.39.5


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  parent reply	other threads:[~2025-02-28 13:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 13:05 [pve-devel] [PATCH cluster/network 0/6] Add global locking and configuration rollback to SDN configuration Stefan Hanreich
2025-02-28 13:05 ` [pve-devel] [PATCH pve-cluster 1/1] cfs: add 'sdn/.lock' file Stefan Hanreich
2025-04-04 17:07   ` Thomas Lamprecht
2025-02-28 13:05 ` [pve-devel] [PATCH pve-network 1/5] sdn: add global lock for configuration Stefan Hanreich
2025-02-28 13:05 ` [pve-devel] [PATCH pve-network 2/5] api: add lock-secret parameter to all api calls Stefan Hanreich
2025-02-28 13:05 ` [pve-devel] [PATCH pve-network 3/5] api: add lock secret parameter to apply endpoint Stefan Hanreich
2025-02-28 13:05 ` Stefan Hanreich [this message]
2025-02-28 13:05 ` [pve-devel] [PATCH pve-network 5/5] api: add rollback endpoint 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=20250228130549.100357-6-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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal