From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Hanreich <s.hanreich@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-cluster 1/1] cfs: add 'sdn/.lock' file
Date: Fri, 4 Apr 2025 19:07:53 +0200 [thread overview]
Message-ID: <4c680cbe-75c2-40a5-844c-d5ecc800f7e1@proxmox.com> (raw)
In-Reply-To: <20250228130549.100357-2-s.hanreich@proxmox.com>
Am 28.02.25 um 14:05 schrieb Stefan Hanreich:
> This file stores a secret if the SDN configuration gets globally
> locked.
stumbled uppon this when checking for open patches for pve-cluster,
sorry for the wait but does this need to be observed by pmxcfs though?
Simple file handled by file_{get,set}_contents might shouled be enough.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-04-04 17:08 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 [this message]
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 ` [pve-devel] [PATCH pve-network 4/5] api: add lock and release endpoints for global configuration lock Stefan Hanreich
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=4c680cbe-75c2-40a5-844c-d5ecc800f7e1@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal