From: cel@kernel.org
To: <kdevops@lists.linux.dev>
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH v4 0/3] Add uniquifier to storage pool path
Date: Thu, 24 Apr 2025 10:17:22 -0400 [thread overview]
Message-ID: <20250424141725.827244-1-cel@kernel.org> (raw)
From: Chuck Lever <chuck.lever@oracle.com>
I'd like to be able to run more than one instance of kdevops per
physical host. Currently the kdevops guestfs set-up steers all
storage pool activity into ${STORAGE_POOL}/kdevops/guestfs, which
means there's a good change that two different logged-in users will
create virtual machines whose names, OS base images, and block
devices will interfere with each other.
So far I haven't been able to get the other storage pool-related
settings to add sufficient uniqueness to prevent this conflict.
Changes since v3:
* Define and use CONFIG_KDEVOPS_STORAGE_POOL_USER
Chuck Lever (3):
scripts: Remove unused kdevops_storage_pool_user variable
Kconfig: Define KDEVOPS_STORAGE_POOL_USER via Kconfig
guestfs: Per-user storage pools
kconfigs/Kconfig.libvirt | 52 ++++++++++++++++++++++++++++++++++----
scripts/bringup_guestfs.sh | 3 +--
scripts/destroy_guestfs.sh | 2 +-
scripts/guestfs.Makefile | 3 +--
scripts/vagrant.Makefile | 2 --
5 files changed, 50 insertions(+), 12 deletions(-)
--
2.49.0
next reply other threads:[~2025-04-24 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 14:17 cel [this message]
2025-04-24 14:17 ` [PATCH v4 1/3] scripts: Remove unused kdevops_storage_pool_user variable cel
2025-04-24 14:17 ` [PATCH v4 2/3] Kconfig: Define KDEVOPS_STORAGE_POOL_USER via Kconfig cel
2025-04-24 14:17 ` [PATCH v4 3/3] guestfs: Per-user storage pools cel
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=20250424141725.827244-1-cel@kernel.org \
--to=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=kdevops@lists.linux.dev \
/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