From: Philipp Hufnagl <p.hufnagl@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH storage v4 0/4] pbs: fix #5008: Check if datastore and namespace is valid on add- and update hooks
Date: Mon, 27 Nov 2023 12:39:57 +0100 [thread overview]
Message-ID: <20231127114001.189590-1-p.hufnagl@proxmox.com> (raw)
This adds a check if the datastore and the namespace is valid when a
user attempts to add a new PBS datastore.
Since the namespace only can be checked after the datastore is
validated, the datastore will be checked as well, regardless that it
will be done later in the superclass anyway.
The functionallity to check namespaces is added with this commit. For
checking the datastore, existing code that has previously been
refactored will be reused
Since the server address has was not included on for the on_update_hook,
I had to slightly modify src/PVE/API2/Storage/Config.pm. I checked and
are pretty sure that this modification does not break anything, however
a second look would be appreciated!
Signed-off-by: Philipp Hufnagl <p.hufnagl@proxmox.com>
---
Changes since v3:
* Modify src/PVE/API2/Storage/Config.pm to add server address
Changes since v2:
* Typos
* reuse connecton on one more place previously fortotten
* simplify syntax
Changes since v1:
* do not add any overhead to activate_storage calls
* splits code from activate_storage so parts of it can be reused
* adds new methods to check namespaces
* calls checks on add/update hooks
Philipp Hufnagl (4):
pbs: Move pbs_api_connect earlyer in the code
pbs: Make it possible to reuse PBS connection for datastore API call
pbs: Extraxt check_datastore_exists from activate_storage
pbs: fix #5008: Check if datastore and namespace is valid on add- and
update hooks
src/PVE/API2/Storage/Config.pm | 4 +-
src/PVE/Storage/PBSPlugin.pm | 122 +++++++++++++++++++++++----------
2 files changed, 86 insertions(+), 40 deletions(-)
--
2.39.2
next reply other threads:[~2023-11-27 11:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 11:39 Philipp Hufnagl [this message]
2023-11-27 11:39 ` [pve-devel] [PATCH storage v4 1/4] pbs: Move pbs_api_connect earlyer in the code Philipp Hufnagl
2024-02-16 15:56 ` Fiona Ebner
2023-11-27 11:39 ` [pve-devel] [PATCH storage v4 2/4] pbs: Make it possible to reuse PBS connection for datastore API call Philipp Hufnagl
2024-02-16 15:56 ` Fiona Ebner
2023-11-27 11:40 ` [pve-devel] [PATCH storage v4 3/4] pbs: Extraxt check_datastore_exists from activate_storage Philipp Hufnagl
2024-02-16 15:56 ` Fiona Ebner
2024-02-19 8:34 ` Fiona Ebner
2023-11-27 11:40 ` [pve-devel] [PATCH storage v4 4/4] pbs: fix #5008: Check if datastore and namespace is valid on add- and update hooks Philipp Hufnagl
2024-02-16 15:56 ` 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=20231127114001.189590-1-p.hufnagl@proxmox.com \
--to=p.hufnagl@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox