From: Chuck Lever <cel@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: kdevops@lists.linux.dev, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH v2 0/4] Add uniquifier to storage pool path
Date: Wed, 23 Apr 2025 10:01:41 -0400 [thread overview]
Message-ID: <a08619fb-1a08-4d0d-849e-d98306d95ae3@kernel.org> (raw)
In-Reply-To: <aAiHFVBzhGSkGFWi@bombadil.infradead.org>
On 4/23/25 2:22 AM, Luis Chamberlain wrote:
> On Mon, Apr 14, 2025 at 01:05:42PM -0400, cel@kernel.org wrote:
>> 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.
>>
>> v2 introduces some additional clean-ups, and attempts to address
>> review comments.
>
> I gave this a spin to see if exisitng deployments won't break but they
> would right away:
>
> Here is me running on a debian system where we had the old setup:
>
> make defconfig-seltests-radix-tree KDEVOPS_HOSTS_PREFIX=x2
> make -j128
> make bringup
>
> User mcgrof is part of the libvirt-qemu group.
> .//scripts/bringup_guestfs.sh: line 276: [: too many arguments
> cp: target '}}/guestfs/x2-maple/root.raw': No such file or directory
> Extra parameter on the command line: ‘libvirt_storage_pool_path’.
> Try ‘virt-sysprep --help’ or consult virt-sysprep(1) for more information.
> Formatting '{{ libvirt_storage_pool_path }}/{{ kdevops_storage_pool_user }}/guestfs/x2-maple/extra0.raw', fmt=raw size=107374182400
> chmod: cannot access '{{': No such file or directory
> chmod: cannot access 'libvirt_storage_pool_path': No such file or directory
> chmod: cannot access '}}/{{': No such file or directory
> chmod: cannot access 'kdevops_storage_pool_user': No such file or directory
> chmod: cannot access '}}/guestfs/x2-maple/extra0.raw': No such file or directory
> Formatting '{{ libvirt_storage_pool_path }}/{{ kdevops_storage_pool_user }}/guestfs/x2-maple/extra1.raw', fmt=raw size=107374182400
> chmod: cannot access '{{': No such file or directory
> chmod: cannot access 'libvirt_storage_pool_path': No such file or directory
> chmod: cannot access '}}/{{': No such file or directory
> chmod: cannot access 'kdevops_storage_pool_user': No such file or directory
> chmod: cannot access '}}/guestfs/x2-maple/extra1.raw': No such file or directory
> Formatting '{{ libvirt_storage_pool_path }}/{{ kdevops_storage_pool_user }}/guestfs/x2-maple/extra2.raw', fmt=raw size=107374182400
> chmod: cannot access '{{': No such file or directory
> chmod: cannot access 'libvirt_storage_pool_path': No such file or directory
> chmod: cannot access '}}/{{': No such file or directory
> chmod: cannot access 'kdevops_storage_pool_user': No such file or directory
> chmod: cannot access '}}/guestfs/x2-maple/extra2.raw': No such file or directory
> Formatting '{{ libvirt_storage_pool_path }}/{{ kdevops_storage_pool_user }}/guestfs/x2-maple/extra3.raw', fmt=raw size=107374182400
> chmod: cannot access '{{': No such file or directory
> chmod: cannot access 'libvirt_storage_pool_path': No such file or directory
> chmod: cannot access '}}/{{': No such file or directory
> chmod: cannot access 'kdevops_storage_pool_user': No such file or directory
> chmod: cannot access '}}/guestfs/x2-maple/extra3.raw': No such file or directory
> Domain 'x2-maple' defined from .//guestfs/x2-maple/x2-maple.xml
>
> error: Failed to start domain 'x2-maple'
> error: Cannot access storage file '/xfs1/libvirt/mcgrof/guestfs/x2-maple/root.raw': No such file or directory
>
> Failed to start x2-maple
> make: *** [scripts/guestfs.Makefile:80: bringup_guestfs] Error 1
>
> So, while I like the idea and approach, this would break tons of
> deployments right now.
>
> Luis
As I mentioned here [1], because KDEVOPS_STORAGE_POOL_PATH contains a
template string:
{{ libvirt_storage_pool_path }}/{{ kdevops_storage_pool_user }}
not a file pathname, 4/4 won't work.
I've committed 1/4 through 3/4 to linux-kdevops, and can post an
updated version of 4/4 that might work better for you. But if it
doesn't, then I'm open to adding a Kconfig option as you suggested.
--
Chuck Lever
[1]
https://lore.kernel.org/kdevops/44e1183d-78a7-411c-bd1f-2e7d4e6fcb32@oracle.com/
prev parent reply other threads:[~2025-04-23 14:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 17:05 [PATCH v2 0/4] Add uniquifier to storage pool path cel
2025-04-14 17:05 ` [PATCH v2 1/4] guestfs: Fix definition of guestfs_storage_dir cel
2025-04-23 6:36 ` Luis Chamberlain
2025-04-14 17:05 ` [PATCH v2 2/4] install_vagrant: Remove this role cel
2025-04-23 6:23 ` Luis Chamberlain
2025-04-14 17:05 ` [PATCH v2 3/4] Replace STORAGE_POOL_PATH with LIBVIRT_STORAGE_POOL_PATH cel
2025-04-23 6:37 ` Luis Chamberlain
2025-04-14 17:05 ` [PATCH v2 4/4] guestfs: Per-user storage pools cel
2025-04-14 21:08 ` Chuck Lever
2025-04-23 6:22 ` [PATCH v2 0/4] Add uniquifier to storage pool path Luis Chamberlain
2025-04-23 6:42 ` Luis Chamberlain
2025-04-23 14:01 ` Chuck Lever [this message]
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=a08619fb-1a08-4d0d-849e-d98306d95ae3@kernel.org \
--to=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=kdevops@lists.linux.dev \
--cc=mcgrof@kernel.org \
/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