public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server v7 4/5] api: create: add 'import-working-storage' parameter
Date: Mon, 18 Nov 2024 18:39:18 +0100	[thread overview]
Message-ID: <c73f446c-61ca-4246-9b0f-f88c09155b4d@proxmox.com> (raw)
In-Reply-To: <683efffa-4ef1-4295-bb13-6828026e1f6c@proxmox.com>

lore.proxmox.com seems to show the diff wrong...

On  2024-11-18  18:24, Aaron Lauterer wrote:
> 
> 
> On  2024-11-18  16:29, Dominik Csapak wrote:
>> this is to override the target extraction storage for the option disk
>> extraction for 'import-from'. This way if the storage does not
>> supports the content type 'images', one can give an alternative  one.
>>
>> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
>> ---
>> changes from v6:
>> * rename 'import-extraction-storage' to 'import-working-storage'
>> * rework permission checks (single branch)
>>
>> i opted to not make the target the first default, since i did not want
>> to introduce such a change this late in the patch/review cycle and
>> AFAICS quite a few code changes would have been necessary for that
>> (we can still change that later too)
>>
>>   PVE/API2/Qemu.pm | 48 +++++++++++++++++++++++++++++++++++++++---------
>>   1 file changed, 39 insertions(+), 9 deletions(-)
>>
>> diff --git a/PVE/API2/Qemu.pm b/PVE/API2/Qemu.pm
>> index c947f09c..701558a7 100644
>> --- a/PVE/API2/Qemu.pm
>> +++ b/PVE/API2/Qemu.pm
>> @@ -132,7 +132,7 @@ my $check_drive_param = sub {
>>   };
>>   my $check_storage_access = sub {
>> -   my ($rpcenv, $authuser, $storecfg, $vmid, $settings, 
>> $default_storage) = @_;
>> +   my ($rpcenv, $authuser, $storecfg, $vmid, $settings, 
>> $default_storage, $extraction_storage) = @_;
>>      $foreach_volume_with_alloc->($settings, sub {
>>       my ($ds, $drive) = @_;
>> @@ -174,9 +174,18 @@ my $check_storage_access = sub {
>>               if $vtype ne 'images' && $vtype ne 'import';
>>           if (PVE::QemuServer::Helpers::needs_extraction($vtype, $fmt)) {
>> -            raise_param_exc({ $ds => "$src_image is not on an storage 
>> with 'images' content type."})
>> -            if !$scfg->{content}->{images};
>> -            $rpcenv->check($authuser, "/storage/$storeid", 
>> ['Datastore.AllocateSpace']);
>> +            my $extraction_scfg = defined($extraction_storage) ?
>> +            PVE::Storage::storage_config($storecfg, 
>> $extraction_storage) :
>> +            $scfg;
>> +            my $extraction_param = defined($extraction_storage) ? 
>> 'import-working-storage' : $ds;
>> +
>> +            if (!$extraction_scfg->{content}->{images} || ! 
>> $extraction_scfg->{path}) {
> 
> I think the if condition here is grouped wrong.
> 
> As it is, once if one of the items (content->images or path) is falsy, 
> we trigger it, but it should not be the case, if the other is actually 
> true.
> 
> Consider the following diff, basically grouping the content->images || 
> path condition, and only if the result is falsy, we want to raise the 
> error.
> 
> diff --git a/PVE/API2/Qemu.pm b/PVE/API2/Qemu.pm
> index 8db443d..545fe31 100644
> --- a/PVE/API2/Qemu.pm
> +++ b/PVE/API2/Qemu.pm
> @@ -179,7 +179,7 @@ my $check_storage_access = sub {
>                          $scfg;
>                      my $extraction_param = 
> defined($extraction_storage) ? 'import-working-storage' : $ds;
> 
> -                   if (!$extraction_scfg->{content}->{images} || ! 
> $extraction_scfg->{path}) {
> +                   if (!($extraction_scfg->{content}->{images} || 
> $extraction_scfg->{path})) {
>                          raise_param_exc({
>                              $extraction_param => "storage selected for 
> extraction does not support"
>                                  ." 'images' content type or is not file 
> based.",

Lets try it once more, hopefully the line endings will be as I want 
them, even on lore.proxmox.com


diff --git a/PVE/API2/Qemu.pm b/PVE/API2/Qemu.pm
index 8db443d..545fe31 100644
--- a/PVE/API2/Qemu.pm
+++ b/PVE/API2/Qemu.pm
@@ -179,7 +179,7 @@ my $check_storage_access = sub {
                         $scfg;
                     my $extraction_param = defined($extraction_storage) 
? 'import-working-storage' : $ds;

-                   if (!$extraction_scfg->{content}->{images} || 
!$extraction_scfg->{path}) {
+                   if (!($extraction_scfg->{content}->{images} || 
$extraction_scfg->{path})) {
                         raise_param_exc({
                             $extraction_param => "storage selected for 
extraction does not support"
                                 ." 'images' content type or is not file 
based.",


Also, I was able to run into this by uploading the OVA to a CephFS.

> 
> 
> 
>> +            raise_param_exc({
>> +                $extraction_param => "storage selected for extraction 
>> does not support"
>> +                ." 'images' content type or is not file based.",
>> +            });
>> +            }
>> +            $rpcenv->check($authuser, "/storage/" . 
>> ($extraction_storage // $storeid), ['Datastore.AllocateSpace']);
>>           }
>>           }
>> @@ -349,7 +358,7 @@ my sub prohibit_tpm_version_change {
> 
> 
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> 
> 



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

  reply	other threads:[~2024-11-18 17:39 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-18 15:29 [pve-devel] [PATCH storage/qemu-server/manager v7] implement ova/ovf import for file based storages Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH storage v7 01/11] plugin: dir: implement import content type Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH storage v7 02/11] plugin: dir: handle ova files for import Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH storage v7 03/11] ovf: improve and simplify path checking code Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH storage v7 04/11] ovf: implement parsing the ostype Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH storage v7 05/11] ovf: implement parsing out firmware type Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH storage v7 06/11] ovf: implement rudimentary boot order Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH storage v7 07/11] ovf: implement parsing nics Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH storage v7 08/11] api: allow ova upload/download Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH storage v7 09/11] plugin: enable import for nfs/btrfs/cifs/cephfs/glusterfs Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH storage v7 10/11] add 'import' content type to 'check_volume_access' Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH storage v7 11/11] plugin: file_size_info: warn on parent images with unusual path Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH qemu-server v7 1/5] disk import: add additional safeguards for imported image files Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH qemu-server v7 2/5] use OVF from Storage Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH qemu-server v7 3/5] api: create: implement extracting disks when needed for import-from Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH qemu-server v7 4/5] api: create: add 'import-working-storage' parameter Dominik Csapak
2024-11-18 17:24   ` Aaron Lauterer
2024-11-18 17:39     ` Aaron Lauterer [this message]
2024-11-18 17:44       ` Thomas Lamprecht
2024-11-18 20:22     ` Thomas Lamprecht
2024-11-19 11:36       ` Aaron Lauterer
2024-11-18 15:29 ` [pve-devel] [PATCH qemu-server v7 5/5] api: check untrusted image files for import content type Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH manager v7 1/9] ui: guest import: add ova-needs-extracting warning text Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH manager v7 2/9] ui: enable import content type for relevant storages Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH manager v7 3/9] ui: enable upload/download/remove buttons for 'import' type storages Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH manager v7 4/9] ui: disable 'import' button for non importable formats Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH manager v7 5/9] ui: import: improve rendering of volume names Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH manager v7 6/9] ui: guest import: add storage selector for ova extraction storage Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH manager v7 7/9] ui: guest import: change icon/text for non-esxi import storage Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH manager v7 8/9] ui: import: show size for dir-based storages Dominik Csapak
2024-11-18 15:29 ` [pve-devel] [PATCH manager v7 9/9] ui: import: adapt live import help text to ova Dominik Csapak
2024-11-18 17:14 ` [pve-devel] [PATCH storage/qemu-server/manager v7] implement ova/ovf import for file based storages Aaron Lauterer
2024-11-18 17:14 ` Filip Schauer
2024-11-18 17:35   ` Aaron Lauterer
2024-11-18 17:46     ` Thomas Lamprecht
2024-11-18 17:44   ` Filip Schauer
2024-11-18 17:49     ` Thomas Lamprecht
2024-11-18 17:53       ` Thomas Lamprecht
2024-11-18 18:03         ` Thomas Lamprecht
2024-11-18 18:03         ` Filip Schauer
2024-11-18 18:11           ` Thomas Lamprecht
2024-11-18 18:19           ` Thomas Lamprecht
2024-11-18 20:02           ` Thomas Lamprecht
2024-11-18 21:15 ` [pve-devel] applied-series: " Thomas Lamprecht
2024-11-19  7:43   ` Dominik Csapak
2024-11-19  8:43   ` Dominik Csapak

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=c73f446c-61ca-4246-9b0f-f88c09155b4d@proxmox.com \
    --to=a.lauterer@proxmox.com \
    --cc=d.csapak@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal